|
This has not been my experience (Source: Apple native developer, since 1986). It is a pain to deal with their App Store, but it isn't intolerable. I don't charge for my apps, but I understand that the Apple ecosystem is very lucrative for devs that do. > causing codebases to become complicated and littered with if/then evaluations for various SDKs I have found that I almost never have to do this, and when I do, it's usually a bad code smell. Part of the reason, is that I develop native, for one platform at a time. It might be another story, entirely, if I have to develop for multiple ones. I just got contacted by a friend, wrt an ObjC app that has been deprecated for over a decade. He reports that it still works fine, on iOS18. Many years ago, I spent a few months, learning Android. The thing that really put me off, was the Android Pizza of Death. That's the pie chart that describes the percentage of users, running various Android versions. It was sobering. Apple basically allows me to write support for the current OS, and support just one back. The app I'm in the process of releasing now, works in iOS 15, but I am declaring support starting at 16, and it works fine in 18. |
Android, on the other hand, is a dumpster fire. The worst SDK I've worked in my life, building UIs there is incredibly frustrating.