5 ms·
Hate away, but in this case I'm on Apple's side here. The author may be the exception where no updates are actually needed, but that does seem to be the excepti
by crazygringo 4y ago
Hate away, but in this case I'm on Apple's side here. The author may be the exception where no updates are actually needed, but that does seem to be the exception. In my experience, most iOS apps I've tried downloading that were last updated 2-3 years ago simply don't work.
Apple requires an update in the past 3 years or else a minimum threshold of downloads. Presumably the latter is required so there are simply enough newer reviews to indicate whether it's broken (lots of 1-star) or not. These seem like pretty reasonable indicators that it's still working.
> My old code simply did not work anymore with the latest versions of Xcode. So I had to spend four hours on Saturday upgrading all my platform libraries simply so that I could compile the damn app.
Honestly that's just good hygiene. Because if they waited another 2 years, it might have taken 4 days to get the thing working. New versions of libraries come with all sorts of improvements, whether it's for accessibility or security or a hundred other things.
It doesn't seem unreasonable to me that if you're maintaining software in a public app store, you should be able to compile it semi-regularly with new versions of packages.
- masklinn 4y ago> In my experience, most iOS apps I've tried downloading that were last updated 2-3 years ago simply don't work. Not sure what category of software that was but e.g. for games it’s usually not an issue. I used to have a bunch of games and game-adjacent software from the first AppStore year, we’re talking the time when you’d pay a buck for a virtual rain stick which’s use the accelerometer. They kept working until the 64b switch killed them. Rebuilding them would undoubtedly have been difficult for the author even if they’d not moved away from them, but because those’d use only minimal is features (raw-ish inputs, and setting up opengl) there’s basically nothing to break which would not be flagrant.
- musicale 4y agoI also had many games killed off by the 64-bit switch (on both iOS and macOS), but even after that a number of games that still worked were removed from the app store.
- TedDoesntTalk 4y agoGames are definitely “complete” after a while., sometimes on first release. If they continue to work on the OS, the only reason Apple is dropping them is because they want the developer to give them another $99. The busywork this creates is a headache for everyone except Apple.
- arcticbull 4y ago$99 from a few developers is meaningless to both Apple and the developer of a game. It's like 40 minutes of wages for an average engineer. Apple doesn't want to have to support old bugs and poor API choices in perpetuity.
- TedDoesntTalk 4y agoWhat makes you think it's only a few and not large scale? And why would forcing a developer to update their feature-complete game result in stopping support of "old bugs and poor API choices"? There is no requirement to update the API level. Read the article.
- arcticbull 4y agoSimply rebuilding and resubmitting the app with a new version of Xcode will yield a significantly different binary artifact today than a few years ago. It isn't necessarily about API level, it could be (from time to time) about going from arm32 to arm64, to adding better-optimized builds for new microarchitectures, getting bitcode that's recompiled by Apple to support app thinning. Apple may deprecate or remove APIs from time to time that should also be addressed. That there wasn't necessarily, specifically, a change this time doesn't mean that this program isn't about supporting that over time. It's much easier to make such changes if developers are in the habit of periodically making updates vs. being told to make a breaking update out of the blue.
- scarface74 4y agoYou really think the $99 a year from developers would incentivize anything? And before you quote the number of “registered developers”, all of those aren’t paying developers.
- nemothekid 4y ago>Apple tells me I could have avoided all this pain if my app was being downloaded above a “minimum download threshold”. The policy is completely silent on what this download number needs to be to avoid getting flagged as outdated–is it hundreds or thousands or hundreds of thousands of downloads a month? I think this is a fair policy as well. From Apple's POV how can they ensure many apps in the app store still work on the latest phones? If the developer has been updating the app, they can be relatively sure. If the developer hasn't, but the app continues to be downloaded with success they can also be sure the app works. But for an app the developer has (seemingly) abandoned and and nobody downloads? It's most likely broken. You could argue that that Apple should test the app before sending such a message but I think it's probably likely that (1) the majority of apps that are abandoned are broken and (2) the developers don't actually respond. It's easier to tell all the devs to get up to speed and those that actually care will submit the app for review (even if all you have to do is change a version number). What actually sucks is if you have to rewrite parts of your app because even though the iPhone 22 Pro Max Plus w/ Turbo & Knuckles supports the same SDKs as the iPhone 4, Apple won't let you resubmit your app as is.
- yamtaddle 4y agoIt also makes sense because it might not be a good idea to apply the same criteria everywhere. In an app category with 10,000,000 downloads per month, an app pulling 500 downloads a month might be a drop-worthy also-ran that's mostly just directing a few people away from better options & cluttering results. In a category with 1,000 downloads a month, the app with 500 dl/m is likely the best and most-popular app in that category and dropping it would be tantamount to dropping the whole category.
- matchagaucho 4y agoAgreed. Apple is not asking for more features, but a recompile of the app against the latest iOS and SDKs. That's generally a good practice as buffer overflows and all kinds of entropy accumulates on an OS.
- SilasX 4y agoApple was adding buffer overflows to their OS in 2014?
- bambax 4y agoBackward compatibility is Apple's job, not developers. (This debate is as old as computers, but I'm strongly in Raymond Chen's camp.)
- naniwaduni 4y agoWorse, developers need forward compatibility. Predicting the future is widely considered harder than inspecting the past.
- musicale 4y agoIn theory if you follow Apple's guidelines then you should maximize your app longevity; in practice Apple is going to break you eventually, and quite possibly in the next OS release.
- tonmoy 4y agoUnreasonable backward compatibility is how we end up with windows vista
- musicale 4y agoWindows Vista was painful, but consider that: 1) Compatibility wise it wasn't worse than macOS Catalina or iOS 11, which both killed off 32-bit apps; actually a typical iOS release is probably worse than Vista in terms of backward compatibility 2) Vista's security improvements (such as sandboxing device drivers, requiring app permissions, etc.) were beneficial and persist to today – and were arguably the predecessor to modern app permissions systems in macOS and iOS (and Windows 10/11) 2a) Microsoft eventually largely addressed compatibility by providing an XP compatibility mode (really an XP VM); they could have/should have managed this better 3) Vista got the UI for app permissions wrong, and users hated it; I think Apple did it better but Apple is generally better at UI and also had the chance to learn from Microsoft's mistakes. At the end of the day, Vista's woes were largely from not paying enough attention to backward compatibility, combined with poor UI design. It was a rough transition, but Microsoft seems to have learned somewhat from the experience (although Windows 8 also had some UI issues.)
- kkfx 4y agoMh, changing the "ecosystem" so much means the ecosystem is not stable, witch means is a crappy mass of bugs/a working prototype not a commercial product. Oh, I like of course innovation but if we talk about mobile stuff, so something tied by choice to hw, their real update rates behind security related patches, should be very calm. Anything must evolve to be alive, but also anything must NOT be stressed to change just some crap to prove that something have changed. That's not evolution. Beside that, I fail to see any tangible improvement in ALL modern software to a point that I almost quit using mobile crapware of any vendor and kind, for real. I can't avoid it completely, unfortunately, but that's is.
- newtritious 4y agoQuite a few changes over the past few years have been reducing access to data that can be used for fingerprinting, and requiring apps to ask permission for access to user data. This is squarely the fault of developers abusing the users trust.
- fny 4y agoYou know what doesn't have this problem? Web apps. I have a site up from 2001 that still functions perfectly.
- stonemetal12 4y agoI doubt it. Web browsers of today can't pass the old acid tests because the spec changed.
- nerdix 4y agoUnless you did one of the gazillion things that was permissible in 2001 but is now considered insecure and was patched out of all the major browsers. Not saying that making browsers more secure is a bad thing but it's definitely not true that every 20 year old web app will work flawlessly on a modern web browser in 2022.
- alpaca128 4y ago> In my experience, most iOS apps I've tried downloading that were last updated 2-3 years ago simply don't work. The linked article already answered this: For instance, the App Store could factor in: - App Store ratings and reviews - Active developer membership - Historical behavior of the developer (ie. updating other apps) - Number of crashes - Number of active sessions, especially for the latest devices and platform versions These are all metrics that the Apple already automatically tracks
- scarface74 4y agoApple just like most sane platforms have a deprecation policy. First they deprecate APIs and then remove support entirely. She said herself that she had to make changes to update her code to the latest SDK.
- lapcat 4y ago> Presumably the latter is required so there are simply enough newer reviews to indicate whether it's broken (lots of 1-star) or not. These seem like pretty reasonable indicators that it's still working. You think App Store ratings and reviews are accurate? They're incredibly easy to fake and buy. Scam artists are doing it all the time.