I am committing as a user of the app, something I plan to integrate into my life.
It’s not unfair to want to know whether the author plans to make it viable long term or if it is a project that is scratching their personal itch.
If it’s a project that’s only meant to scratch a personal itch and they only plan to support it for as long as they deem it useful and have no intention of open sourcing it in the future that is fine, I personally, and I’m sure other , don’t want to bother with it, that doesn’t mean nobody does but it answers a question and prevents disappointment down the line.
If the author has intentions of supporting it long term then asking about funding or long term development effort assists the author to think about something they might bot have thought about, or at the very least has the author clarify.
I’m fine with paying for polish, many users are.
Here the product is already made and in distribution, asking these questions isn’t preventing the project for getting going, they are the next logical step in the life of a project, arguably some of them should have been asked before “going live” like if you would like to monitise the project.
Sure, again, all granted. To reiterate the thesis of my prior comment, 'Fair to ask, but show the courtesy due an equal at least until it is evident that is unwarranted.'
I asked a question in response to them asking me to download and use their app. Have we reached a point in this world where simply asking a question is offensive? They had every right to choose not to respond just like I can choose not to use their app if they don’t. How you respond is your choice, if you chose to take offence to a question about the long term sustainability of a project that’s on you, for me I don’t want to use software that has no intention of existing long term. If we have different values that’s fine, I don’t care.
A cultural difference, perhaps. I read your tone and line of questioning as brusque if not just shy of insulting, but if you are familiar with the 'ask vs. guess' distinction, I hail from an exceptionally "guess"-oriented culture which I, ironically belatedly, gather may be uncommon in this discussion. Pray excuse me.
Thanks for this. As the developer of the app, I must confess that to get to the current state was mainly motivated by having fun coding and a general willingness to release it. There was no plan, in that sense, where I want to be in a year or so. For now, I want to focus on building a great product, and the confirmation of a great product for me would be to see usage. To me, to maintain the app for now seems to be not a lot of effort.
It’s not unfair to want to know whether the author plans to make it viable long term or if it is a project that is scratching their personal itch.
If it’s a project that’s only meant to scratch a personal itch and they only plan to support it for as long as they deem it useful and have no intention of open sourcing it in the future that is fine, I personally, and I’m sure other , don’t want to bother with it, that doesn’t mean nobody does but it answers a question and prevents disappointment down the line.
If the author has intentions of supporting it long term then asking about funding or long term development effort assists the author to think about something they might bot have thought about, or at the very least has the author clarify.
I’m fine with paying for polish, many users are.
Here the product is already made and in distribution, asking these questions isn’t preventing the project for getting going, they are the next logical step in the life of a project, arguably some of them should have been asked before “going live” like if you would like to monitise the project.