Jun 20, 2026, 8:28 AM@BenRiceM From what I know (which is admittedly limited), it’s also not really feasible to have a pay per major upgrade model on mobile operating systems because the underlying APIs could change at any time, breaking non-updated apps—so yeah, I get the conundrum. 😅
@amxmln That’s mostly true, but Apple could support publishing updates to older versions of the app.
It can be a huge pain trying to support multiple operating systems, but imagine if you could have a “legacy” version of your app for iOS 18 and the current version on iOS 26/27 but still be able to publish bug fixes to the 18 version.
And if that were possible you could tie your paid updates to operating system versions.
(Does that make sense?)
Jun 20, 2026, 9:31 AM@BenRiceM Yeah, I get it. 😊
I guess a workaround could be to have an Indigo Classic and then Indigo 1/2/3/4 for releases? Although I don’t know how that would work with maintenance, overhead, user-data, etc. My current Mastodon app, Mona, did something similar with the Liquid Glass update. 🤔