Open Jeehut opened 1 year ago
fwiw - I think the disconnect here is that the limits don't seem (to me at least) to align with the package descriptors.
Currently, you have
This makes sense to me as targeting. Bigger companies will probably be willing to pay more.
However, I don't see the logic in tying this to #languages.
Why would a small indie not support lots of languages? If you have a diverse userbase (or are willing to use machine translation), then that's an easy edge for a small app.
Moreover - it's kinda the pitch for using Remafox at all. It should be the pitch from Remafox that 'now you're set up - you can easily add all the languages!'
The #text blocks limitation makes a lot more sense to me. 500 is a pretty decently sized app, so if you need unlimited, then you're probably developing something pretty large.
But neither of these are great discriminators for larger company. Normally, services do that by detecting multiple users, offering sso support or similar. These don't really apply in your case.
It's tricky - you need to make a living, and you want to take more money where you can. Equally, £99 isn't a trivial ticket price...
@ConfusedVorlon Thank you for your input, I will take it into consideration for potential future pricing changes.
Having that said, I really don't want to discuss pricing of my apps. It's a topic where I can't possibly ever make everyone happy. I researched the translation management market before setting my pricing, and my app is still very cheap compared to the competition, even though it's deeply integrated with Xcode, unlike any other competition. And helping with translations is only the beginning feature set of RemafoX, there's much more to come within the next year and who knows where the road is headed in the years after.
My goal is to rather add more features and keep the pricing than to add features and require users to pay more for them. Maybe I should make this more clear on my paywall. The features listed on the roadmap and the ones I created myself in the Issues here are by far not the only ideas I have planned for RemafoX, but I don't want to spoil everything. So, especially everyone who purchases a Lifetime membership now will profit a lot over the years for really cheap. But of course, it's a question of trust: Do you think I will be able to keep up with my plans or will the app only get small updates? In any case, investing in me by making a purchase (and maybe even spreading the word) is the best way to help me succeed and motivate me to add more features long term.
It's a choice, and adding more flexibility to the pricing is going to make this choice a little bit fairer, I think. Even if it doesn't suit your needs at the moment. I hope that you will think differently once you see how RemafoX evolves over time.
Problem Statement
If a project has requirements that just go above the Pro tier limits a little bit (25 languages / 500 text blocks per project), like say 30 languages in a project but the text block limit actually is fine, it's a big jump to the Max tier to just add those missing 5 languages to the plan.
Suggested Solution
Have more flexibility in the pricing by providing options to add languages and text blocks to an existing tier. For example, to support 30 languages, it should be possible to buy the Pro tier and a pack of 5 languages added on top. This way, the paid amount would reflect the needs of the user much better without having to jump to the Max plan.
Additional Considerations
To keep things simple, the additional languages or text blocks could be Lifetime-only.