Sorry, I don’t understand you. Are you talking about the payment for getting the App? Or are you talking about something else? What do you mean by: it didn’t work like how I said?
Yes if there are any paid features then no arguments they’ll definitely have to use a paid subscription model, added on top of the one-time access fee they’ll charge (it said $30). However, what I’m saying can just be applied on top of that.
So from what I understand, you said you don’t want to have to continue paying for Ratio after the first upfront fee (one-time access fee). I’m trying to say that, I suggest they use this model: a one-time access fee, with a small yearly subscription fee to get access to updates.
Most payment models out there right now are mainly either: one-time access fees or monthly/yearly subscriptions. The one-time access fee model that was widely used back then is very unsustainable, because it is dependent on the regular influx of users purchasing the product. However, the subscription model is Firstly, very costly for Users, and Secondly, still slightly unreliable for the Developers, as it isn’t guaranteed that Users will continue using, and thus, paying for the product after the first month or year.
So, what I’m suggesting is that they combine both of these widely used models, and ensure that they’ll have a reliable source of revenue, and lower subscription fees for the Users, a win-win situation for both parties.
Alternatively, they (developers) may choose to adopt a model where: there is a fixed initial free-trial period and afterwards use the subscription model
There are many different business models out there. I’m just suggesting the one that I feel, will be good for both the developers + users, as the one-time access fee model is unsustainable, while the subscription model is very costly for users.