While trying to launch a mobile application I wonder how I should handle adding a payment solution later on. I would like to have all features available for free in the beginning to get as much feedback as possible. Once I have decided on which features to keep I would like to lock most of them behind a subscription solution. How do you handle this? Does existing users feel betrayed if they suddenly has to subscribe in order to keep using the app?
Describe it as paid, with a free year, and extend everyone's account periodically until you've figured out what to charge for (and how).<p>When you do figure out what to charge for, consider charging long time users less, or extending them out one last time.
Instead charge money from the beginning.<p>It will provide useful feedback regarding whether people will pay and if some people will pay, what they will pay for.<p>You want people who are willing to pay. You don't want people who are unwilling. Requiring payment is basic market segmentation.<p>Good luck.
If an app I was using did that, I would immediately delete it from my device and look for an alternative. It wouldn't even matter to me if the alternative offered less features.
My approach for a business solution was to limit volume on a fee account and let their growth tip into paid options. It was clear up front. Never modified it. YMMV