RailsConf 2024 - Progressive Web Apps with Ruby on Rails by Avi Flombaum 

If you imagine 3 stages of complexity for offering a mobile experience for your users: 1) PWA: minimal dev effort, no interaction at all with app stores and mobile ecosystems 2) Turbo/Strada hybrid app: modest dev effort, some knowledge of mobile development required + interaction with app stores, etc and 3) full mobile app, immense effort, most likely requiring dedicated developers. Enabling PWA is the fastest and cheapest option if you're operating on limited resources, boostrapping, a solo, or crunched for time. It also helps if you want or must keep a single codebase in Ruby and not mess with Swift/Java/Kotlin, or avoid app store fees and red tape. Conversely, of all possible ways, it's the least "native"-like, but considering the minimal effort, it's a very acceptable tradeoff imo.

@@kevinvzb Thanks for your reply! :) Let me reverse the question, when do you think it's absolutely necessary (from requirements POV) to go native?

@@alessandromacagno4127 if the product absolutely depends on access to native mobile APIs (like advanced camera features) you can't get through browsers.