3 ms·
It’s not hard to do a recompile with a slightly newer SDK, check things still work, update the version and copyright and re-upload. That’s how I keep all my ap
by w0mbat 4y ago
It’s not hard to do a recompile with a slightly newer SDK, check things still work, update the version and copyright and re-upload. That’s how I keep all my apps in the store.
Often you find a cheap update you ought to make, like add dark mode support which wasn’t a thing when the app was written. Sometimes you take the app across a tech boundary, like adding ARM code to a Mac app. I can see Apple’s motivation to keep fresh goods on their shelves that work with current OS versions and hardware.
- TedDoesntTalk 4y agoSome apps are feature-complete.
- w0mbat 4y agoNo app is feature complete on a changing platform. The OS changes and the new hardware is different. Assumptions made years ago no longer hold. One of my apps has been in the store for 10 years (Mac & iOS) and I have had to make many updates to keep it fresh. (Adding Retina support to the 3d rendering code and the picture assets, going 64 bit on iOS, dark mode, adding ARM to Mac, replacing deprecated API use, etc, etc.). These changes are in addition to updates that fixed bugs or added actual new app features and are part of the cost of doing business.
- newbalance 4y agoIt's hours of work - recompile, test, publish, test again once new versions hits the App Store. Upgrades and maintenance are a bigger time sink than most consider. And this assumes there aren't any new issues that need fixing during the maintenance.
- capableweb 4y agoGames are immensely more complex than your average run-of-the-mill smartphone application. As the author of the submission tweet themselves say: > Now I need to dig up my project file, update the Unity version to make sure it meets the App Store requirements, rebuild, retest, resubmit all to get the exact same game in the exact same place it was before. From my own experience, updating the Unity version tends to not be hassle-free, especially if it's a major version. Updating xcode tends to be a hassle as well, if not outright impossible unless you keep buying new Apple hardware too. And why is the onus on the developers to update apps just for the sake of updating them? Can things not just be "done" anymore? There doesn't seem to be any specific reasons except "we like fresh updates" provided for why the updates should be done. If it works, why remove it? Are they running out of space? Are people being fooled by the application somehow?
- Gollapalli 4y agoUpdates should be required only when specific apis or features are deprecated and the app in question uses those. But there probably isn't an easy way to test whether an app uses them. Aside from literally going through the binary, looking for those calls or something.
- w0mbat 4y ago>> Updates should be required only when specific apis or >> features are deprecated and the app in question uses those. >> But there probably isn't an easy way to test whether an app >> uses them. Xcode tells you what deprecated calls you are using every time you do a fresh build. The list varies by which minimum iOS version you state. Xcode also tells you if your project settings need an update, and will do it for you. You should always be able to do a fresh build, or your app is effectively abandoned.
- rockbruno 4y agoOnly if you're doing it constantly for every SDK update. But if your game is complete then you have no reason to do it, and if you haven't updated your SDKs in 2 years, chances are that you will not be able to do it without re-writing a huge part of the software.