Hokay, so, first the “native app” option is still in beta, so it’s not officially supported. It does seem to be unofficially supported, but undocumented.
From a high-level app organization perspective then, there seem to be 3 options:
- web app (how Bubble normally works)
- mobile (this is a page that your web page can redirect to when the user is mobile)
- native app (this is a single page that does everything and is sort of exported to the app store)
Question: can you have a “native app” page for ios and a different “native app” page for android, or can you detect that the app is on ios/android to show different navigation and so on?
Question: is there any advantage to using the “mobile” option vs the responsive layout settings?
Question: if you have a “native app” page that gets sent to one or more app stores, you can still have a web app, right? Are there any side effects to a single “native app” page that make that page inappropriate as a web app? Maybe it takes a long time to load or something like that?
Question: when you build a “native app” page, and submit it to the app store, and it gets accepted, and users download the app, do you have to update it through the app store instead of just pushing a new version from development to live in Bubble?
Question: once a “native app” is on a user’s phone, does it have to communicate with the database through API workflows, or is it still transparently connected like the web app?