What I've learned from shipping 25+ mobile apps

20-Feb-2026 306
Most teams overestimate how much “native” they need This is the pattern I see more than any other. A team comes to me convinced they need custom native screens for half their app. They want native forms, native lists, native everything. They’ve been burned by web views that look janky and they don’t want that experience. Then we look at what their users actually do. And 80-90% of it is standard CRUD. Creating records, viewing lists, editing profiles, managing settings. All of that works beautifully as server-rendered HTML inside a native navigation wrapper. No custom Swift or Kotlin needed. The native parts that matter are the ones that can’t be web. Push notifications, camera access, biometrics, haptic feedback, in-app purchases. Those need to be native. And most of them are doable with bridge components in a few lines of HTML!.
Use coupon code:

RUBYONRAILS

to get 30% discount on our bundle!
Prepare for your next tech interview with our comprehensive collection of programming interview guides. Covering JavaScript, Ruby on Rails, React, and Python, these highly-rated books offer thousands of essential questions and answers to boost your interview success. Buy our 'Ultimate Job Interview Preparation eBook Bundle' featuring 2200+ questions across multiple languages. Ultimate Job Interview Preparation eBook Bundle