Comment by eps
2 years ago
Your choice obviously, but paying a recurrent fee for an existing function as opposed to new content comes across as unjustified and inherently unfair.
2 years ago
Your choice obviously, but paying a recurrent fee for an existing function as opposed to new content comes across as unjustified and inherently unfair.
You prefer schemes then where you have to pay for new functions, and pay once again for new features added later on, and so on?
I am also producing content and will have more. It sounds like you’d want that content to be paid for instead of just free to make sense of the subscription options. That’s a good idea.
Yes, I much prefer that and I'm probably not in the minority.
This arrangement lands itself especially well on educational apps - you would buy a "module", master it, progress, buy next one, rinse and repeat. If you stall, that's your problem, the $ waste is limited and you can always backtrack and re-learn without paying again. Just like with textbooks.
I realized that maybe the best is to have some schedule of premium features becoming free for all later on as I develop more. Which is my plan - expand my differentiating moats at the edge so that I can give everything the competition charges for for free.
Perhaps adopt a hybrid model where you keep the features added before and up until the end of your subscription term? Then if you want features added after that, you have to renew your subscription.
"apps these days" aren't like older software, where basically all the code and functionality was written and baked into each new release by the author/team releasing it
almost every piece of new software you use (certainly everything with a subscription) is actually calling another third-party paid API (sometimes multitudes) and using your subscription money to pay for the cost of the app leveraging that API
this approach made it much easier to release a product, but now the product depends on a third-party being paid for every request
I have near zero marginal operating cost thanks to offline-first architecture
But now I see this "offline first" upgrade is seen as a downgrade in terms of value for the premium offering, so I have to figure that out
For what it's worth "offline first" is a big win in my opinion and would sway me to switch to Manabi. I tried it previously, and the changes you mentioned are something I'm interested in.
1 reply →