3 ms·
> Apple breaks existing apps. They have a pretty long beta program (source: Apple dev., since 1986). If your app doesn't work with the upcoming release, it's n
by ChrisMarshallNY 4y ago
> Apple breaks existing apps.
They have a pretty long beta program (source: Apple dev., since 1986). If your app doesn't work with the upcoming release, it's not Apple's fault.
Some companies will refuse to start testing, until the OS is officially released. That's a corporate process problem, and not Apple's.
I'm not an Apple apologist, though I am often accused of being so (because I develop Apple apps, that is enough to categorize me as a "fanboi"). It's just that Apple (and many, many other companies) goes well out of their way to accommodate prerelease testing of apps on their operating systems, and many many companies don't bother to avail themselves of the opportunity. I do have a problem with people that consider themselves to be "professionals," having these issues, and blaming the operating system, when the fault is PEBCAK.
I tend not to do very much testing of prerelease, beyond a simple "make sure it doesn't crash" test. I will turn up an issue, from time to time, but it's rare. When I do get an issue, it is often that I rely on a certain order of calls, in delegate protocols, and they can change, with OS releases (the fact I rely on the order is a bug, and this just exposes my bug, so I need to fix it).
This is because I take a very conservative approach to writing apps, use native Swift, but not "bleeding edge," and support one version back. I have deprecation warnings turned on, and all warnings as errors, so I can't compile, if I have stuff that Apple sees will break (usually, the deprecation warnings start a couple of major releases in advance).
I also don't use dependencies, or write, using hybrid systems. That helps a lot.
- nindalf 4y agoYou’re saying it’s their fault for not testing their app on a pre-release OS that breaks the app. The people you’re replying to say that an OS shouldn’t break an app unless it’s absolutely unavoidable.
- CharlesW 4y ago> You’re saying it’s their fault for not testing their app on a pre-release OS that breaks the app. The notice doesn’t say that iOS 16 breaks the app. It’s extremely unlikely that it does, unless they’re using private APIs (bad), or they’ve hardcoded an “iOS 15 or lower” version check (bad). What the notice does say is “we couldn’t be bothered to test the app with iOS 16, even though it’s been available to developers for months”.
- dahfizz 4y agoThat's exactly the issue. Writing an app once shouldn't mean a lifetime of maintenance. You shouldn't have to test and rewrite once a year (!!). If I gave you a three month warning before punching you in the face, it doesn't make it reasonable for me to punch you in the face.
- noirbot 4y agoThe issue is the other end of this is Microsoft having essentially eternal backwards compatibility for everything in Office and Windows and the major security risks and code baggage that come with that.
- ChrisMarshallNY 4y agoIf you need to rewrite your app, every year, then the problem is not the operating system vendor. If you don't want to write apps for a platform, then the solution is simple; don't support it. Most folks like to support Apple, because it's a really lucrative user base. People make a lot of money from users of Apple devices. People use Apple devices, because they like the assurance they get, of certain things. Most of the folks that complain about Apple are not exactly representative of the huge majority of folks that use Apple devices; who don't have much interest in going out on social media, and making noise about their devices. If someone gives me a three-month punch warning; I have no one to blame, but myself, if my face is still there, when the punch comes. Whether or not the punch should be thrown, is another matter, and not really relevant (or appropriate) to the discussion.
- droopyEyelids 4y agoI work at a big 2nd-tier tech company and corporate security policies prohibit beta versions of OSes. Our ios and android apps are a huge part of our business yet the only way for devs to work on updates is to subvert corp security like figure out how to proxy client certs or bridge the corp network from their laptop to their personal equipment. Its a huge fight every year that never gets resolved
- jen20 4y agoThat sounds like a problem with your corporate policies.