1. LLMs/AI lower the barrier to native development
“LLMs changed one of the core assumptions behind our 2020 decision, so we reevaluated our mobile stack from first principles. What we found led us back to native.” – fnthawar2
2. Unpredictable App Store review times favor OTA/web updates
“I cannot plan around random which is why I’ve opted for web‑tech‑based apps (Capacitor) with OTA updates so I can get fixes out just as quick as I could get webapp updates out.” – joshstrange
3. Trade‑offs between cross‑platform and native (performance, UX, maintenance)
“- App Store Review time… - In the same vein, you can do updates without waiting on native when using web technologies… - Cross‑platform, yes LLMs mean you can create a native iOS and Android app but you have to keep those in sync… - Like the point above: Web, if you want to support web, why not get the other platform for cheaper (shared logic)” – joshstrange
4. Team size and resources dictate feasibility
“The vastly undersold topic to all of these is how many developers do you have? We have the option of using flutter, or not launching an app at all. The concept of going full native is a non‑starter.” – SV_BubbleTime
5. Calls for evidence and long‑term cost data
“For a post about reevaluating costs from first principles, there's remarkably little cost data. Engineer hours? Review time? Defect rates? Parity failures? Agent spend? Ongoing maintenance? Anything?” – hermitwriter