I’ve always seen Bubble Go as a kind of transition between the mobile preview and TestFlight or the internal test version of Android. If you really want to test stability and behavior, you necessarily have to go through here. This will also allow you to test other elements, such as push notifications, and other plugins (if you have used them) that require a native mobile phone.
I suggest you switch to these two tools as soon as possible. So you get a big picture of what’s really happening to your app on real mobile devices. I would use the web preview for the very first steps, that is the construction more than anything graphic. Bubble Go as confirmation to the mobile preview (but I would only check the UI, nothing more.
Everything that is logical, workflows and API calls in my opinion must be verified on TestFlight and Android internal test Version.
If it’s ever acting up you need to quit it and relaunch ( Happens very often). Also it makes my iphone 15 very hot and eats up about 1% of battery every 2 minutes when in use. Does it do the same for you?
I am not done “converting” my webApp to native yet -50% through. There’s more to do than expected. Repeating groups, drop downs, using shor lists and sheets, etc… I am forcing myself to use plugins to a minimum for now and it is possible. It also helps in reviewing and revamping design UI. Happy about it so far.
When I am more advanced, in about one month, I will register for Apple store and Google Play and test.