Respectfully, I am on a salary so it is very difficult to know whether this could translate to more than $65 in wage improvement over a year, even in theory. If I get a raise it will be due to a combination of reasons. However, if this is indeed a productivity enhancer, you should market to companies, not workers.
You mention that I should pay an ongoing fee for features to be added over time. However, there is no guarantee of future feature development even if I do pay every month. And there is definitely no guarantee I will care about or like the new features either. If this transcription works well, that’s the only feature I need.
Being charged monthly also doesn’t seem right when you’re not providing an ongoing service. If you develop a new feature that is better than the current version, I would pay for that as well.
> However, if this is indeed a productivity enhancer, you should market to companies, not workers.
That's the plan. Gotta start somewhere.
> You mention that I should pay an ongoing fee for features to be added over time. However, there is no guarantee of future feature development even if I do pay every month. And there is definitely no guarantee I will care about or like the new features either. If this transcription works well, that’s the only feature I need.
For a monthly subscription or annual subscription, the developer is incentivized to develop new features to retain the ongoing payments coming from the existing customer base.
A one-time payment model actually incentivizes the developer to focus instead on marketing efforts every month and capturing new users rather than increasing/maintaining the satisfaction of the current user base.
> Being charged monthly also doesn’t seem right when you’re not providing an ongoing service. If you develop a new feature that is better than the current version, I would pay for that as well.
I definitely am providing an ongoing service. You get constant improvements to the application, bug fixes, and support. Would you prefer in-app purchases for each additional feature?
Thanks for sharing your perspective on the pricing though. It's very helpful to see how people view the value of what I'm building versus their hard earned dollars. Fundamentally, this is the only pricing scheme that would make sense for me to continue development on this application and devote as much time to it as I am. I'm giving up a significant portion of my time to continue pushing development forward and I need to make sure that it makes sense for me personally if I want it to be something that isn't short-term.
You mention that I should pay an ongoing fee for features to be added over time. However, there is no guarantee of future feature development even if I do pay every month. And there is definitely no guarantee I will care about or like the new features either. If this transcription works well, that’s the only feature I need.
Being charged monthly also doesn’t seem right when you’re not providing an ongoing service. If you develop a new feature that is better than the current version, I would pay for that as well.