Ask HN: How to build a Minimum Viable Product that is a smartphone app

I am hoping that someone with more experience building Minimum Viable Featuresets for products can tell me. I can understand the value in building a MVP around a SaaS(Browser based), because its quite easy to add features, and deploy with out much disruption. But, how does one do it in the smartphone app arena? I have quite a number of apps on my android phone that have never been updated since install, and if I release the bare minimum featureset as part of Version 1.0, wont I stand the risk of my initial launch base possibly never being able to experience my Version 1.x feature release?

Or should I be releasing Version 1.0 to a closed (invite only) user base and iterate like crazy based on feedback received from them before doing a public launch?

Any advice is very much appreciated.