[skydhash]

Mobile development is very fast-paced. Even with the native Android SDK, dependency issue can bite you. If I start working on an old codebase and I can't get it to launch in a few hours. I just generate a new starter project and migrate the codebase, adding the newer version of each dependency (while taking care of breaking changes and so). It can be easier and take care of security issue at the same time.

Desktop, CLI and Web Backend programs can be easier because they are in a much stable environment. But mobile development is very much a high-speed train.

My own tips for React Native is just use the IDE (XCode, Android Studio) for each platform whenever I have to build and use a text editor for the JS part. Always worked flawlessly.

[wccrawford]

On top of that, Google is now requiring that you keep within 2 versions of the latest API, meaning that you have to reupload your app every 2 years (or less) to keep it on the store. Even if it's completely fine.

I think there's something similar for Apple, but I can't actually remember the details right now.

[kitsunesoba]

Apple doesn’t generally enforce lower bounds on the supported OS or SDK built against unless there’s recently been a major transition (e.g. 32-bit support being dropped), which don’t happen too often. They will remove listings that have sat idle for too long though (4-5+ years I think, but don’t quote me on that). I’ve never dealt with it personally since the projects I’ve been responsible for have always been getting updates.