I seriously doubt Apple will casually abandon HealthKit. They are not Google, and I'm sure the contracts underpinning MFi and similar marks for major partners have savagely punitive terms that would enable those partners to recover in any such case.

Not what I was referring to, hope this clarifies but apple seems willing to change the API which would require dev time to implement, ie this isn’t a project you can stick on the app store and ignore, it will require continuous effort and cash to keep there and compatible.

As an individual developer is the owner of the app and code I just want to know if the app will still exist in a year and be functional, otherwise I am not interested regardless of me liking the app idea.

If OP would like to charge money or accept donations or whatever they would like to do that is fine, but right now those questions are unanswered.

Okay, all granted, but now that we agree you keep all your data which is safe, we only need discuss how no other than totally trivial project I think can really be "[stuck] on the app store and [ignored]," not for more than a couple years. Anything with meaningful platform integration would impose the same requirement, not to mention the $100 pa vig and time investment required just to show up at the party. In 2025, for something whose basic concept is obvious and the differentiator is polish, I don't see this as a tremendously reasonable showstopper the way you're treating it, even for a first time dev.

"Assume good faith" and that. Fair to ask, but show the courtesy due an equal at least until it is evident that is unwarranted. This engineer has done work demonstrating they are at least my equal and I am not prepared to treat them otherwise only because I have not seen them do so before. The 32/64 bit and Intel/Arm transitions should be enough warning for anyone and lie well within living memory.

Someone may cavil over "polish," I suppose. I have a 5-quart 'Artisan' Kitchen-Aid stand mixer in lavender, because that nicely sets off my kitchen decor and because I impose light enough duty on that machine to make aesthetics a reasonable figure of merit. This app is not that kind of machine. Who cares what color the cover plates are, when the target audience will never run the machine with them installed anyway?

(And unless there exists a design patent, why worry about a case where, at worst, you already know what market you need your product to fit?)

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.'

Where is the lack of showing courtesy?

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.

No need to be excused, you did nothing wrong, we misunderstood each other is all.