3 ms·

> Apple requires you to update your app every year to support their new tooling. ????. I barely do this each 2 or 3 years. Also, I keep away to high dependenci

by mamcx 7y ago

> Apple requires you to update your app every year to support their new tooling. ????. I barely do this each 2 or 3 years. Also, I keep away to high dependencies, so maybe I get lucky. I do small stuff like - re-generated and update your push notification certificates. - update your marketing images - Recompile once per year? That is so close to zero maintenance as is possible to get.

wlesieutre 7y ago
The current language Apple is using is: >Starting April, 2020, all iPhone and iPad apps submitted to the App Store will need to be built with the iOS 13 SDK or later. They must also support the all-screen design of iPhone XS Max or the 12.9-inch iPad Pro (3rd generation), or later. If you want to properly support iOS 13, that also means implementing dark mode support and breaking your application delegate apart to a scene delegate for multiple instances. In addition to the notched screen "safe area" changes that most developers have probably caught up on by now but are becoming mandatory. Previous years it's meant supporting flexible sizes for new devices, sizes for split screen multitasking, drag and drop, siri intents, adding @3x retina assets, changing out UIWebView to the (not directly compatible) WKWebView, and a million other things. For a simple app with minimal support for iOS's growing featureset, maybe some years you can get away with loading it into this year's XCode, clicking the automatic code update button, and compiling. But polished iOS apps put a lot more work into keeping up. I don't have any knowledge of how Android compares, but iOS is definitely a moving target and Apple isn't afraid of deprecating things or mandating support for newer features.
itake 7y ago
> once per year? That is so close to zero maintenance as is possible to get. Compare that to a static site with Netlify or AWS S3, which never requires an annual package update and rebuild. You also didn't address how Apple requires you to update the marketing screen captures. You will need to brush off the dust of your faked out app data and spend a few hours tweaking them in an image editor.

by mamcx 7y ago

wlesieutre 7y ago

The current language Apple is using is: >Starting April, 2020, all iPhone and iPad apps submitted to the App Store will need to be built with the iOS 13 SDK or later. They must also support the all-screen design of iPhone XS Max or the 12.9-inch iPad Pro (3rd generation), or later. If you want to properly support iOS 13, that also means implementing dark mode support and breaking your application delegate apart to a scene delegate for multiple instances. In addition to the notched screen "safe area" changes that most developers have probably caught up on by now but are becoming mandatory. Previous years it's meant supporting flexible sizes for new devices, sizes for split screen multitasking, drag and drop, siri intents, adding @3x retina assets, changing out UIWebView to the (not directly compatible) WKWebView, and a million other things. For a simple app with minimal support for iOS's growing featureset, maybe some years you can get away with loading it into this year's XCode, clicking the automatic code update button, and compiling. But polished iOS apps put a lot more work into keeping up. I don't have any knowledge of how Android compares, but iOS is definitely a moving target and Apple isn't afraid of deprecating things or mandating support for newer features.

itake 7y ago

> once per year? That is so close to zero maintenance as is possible to get. Compare that to a static site with Netlify or AWS S3, which never requires an annual package update and rebuild. You also didn't address how Apple requires you to update the marketing screen captures. You will need to brush off the dust of your faked out app data and spend a few hours tweaking them in an image editor.