>
your comment is completely divorced from the situation on the ground when it comes to app developmentPerhaps it is.
> The UI has changed overtime, sometime substantially,
How so? I see an app in the store. I install it. An icon shows up on my screen. I tap it to open it. A window is shown where I can type text in. If I receive a phone call or text message, something is displayed on the screen to alert me to that fact. I can tap on that to be brought to the event source. Or I can ignore it. When I close the app, there's usually some way for changes to be saved (sometimes automatically).
This workflow, as the user sees it, hasn't changed.
> there is now an entirely new language (Swift) you can write your apps in as well as a new design language based on that new language (SwiftUI).
Did that deprecate compatibility with apps written in the older language?
> APIs change version to version of iOS and customers expect things that are now possible on newer iOS versions even if your app was written on an older version
Like what? The context was a text editor app and todo apps. What has changed here?
> Also, a lot of app developers work directly with their app’s communities to focus on what their users want.
That's pretty cool. What about basic features without needing a subscription?
> Have you not dealt with the annoyance of an app that hasn’t been updated for a newer OS? Or one that isn’t even providing “table stakes” to other apps in it’s category?
Yup. It's almost always an app that's written in some trendy language, using some cloud feature, or some paid-for app. I use lots of free software on my laptop without that problem.
Notably, text editors from 30 years ago still work fantastically. Email clients from 30 years ago still mostly work great (unless using certain popular anti-consumer cloud email providers). Games from 20 years ago are a hit or a miss. A lot of times they work just fine with an emulator.
And I've already paid for all of those. Once.
Why should the iPhone be any different?