I build for the web so I'm obviously biased, but have you considered building a web application? If your app doesn't use device features that are not exposed t

I build for the web so I'm obviously biased, but have you considered building a web application? If your app doesn't use device features that are not exposed to the browser, building a progressive web app (https://developers.google.com/web/progressive-web-apps/ https://developers.google.com/web/progressive-web-apps/) will save you a lot of effort, help you get to market faster, and spend far less money on user acquisition than a native app. On iOS, PWAs look and feel no different from regular websites. On Android, you get access to native-like features, including support for loading the app offline, push notifications, the ability to install the app to the homescreen, a separate entry in the task switcher, etc. I wouldn't build something like Snapchat or Instagram as a webapp, simply because building those experiences in the browser and getting them just right is still kinda hard. However, most applications aren't Snapchat or Instagram, and a prototype certainly doesn't need that level of spit and polish. You might still choose to build a native app somewhere down the line, but starting with a webapp gives you a chance to evaluate your idea and get something working in the hands of your users very quickly.