Bubble.io Web View Performance & Stability for Native Mobile App (Shared Reusable Elements)

Mobile Beta
1

Hey everyone,

We’re currently developing a native mobile app using a web view for our Bubble.io application. Our goal is to maximize efficiency by sharing reusable elements between our web and native app.

We’re running into some concerns regarding the performance and stability of the Bubble.io web view within a native wrapper. Specifically, we’re noticing:

  • Loading times that feel sluggish compared to a truly native experience.
  • Occasional glitches or unresponsiveness, especially with more interactive reusable elements.

We’re trying to keep development streamlined, but not at the expense of user experience.

Has anyone successfully optimized their Bubble.io app for a native web view, particularly when using shared reusable elements? What are your best practices for:

  • Improving overall performance and responsiveness?
  • Ensuring stability and minimizing glitches?
  • Designing reusable elements that perform well in both web and native web view contexts?

Any tips, workarounds, or alternative strategies would be hugely appreciated!

Thanks!

2

I’ve also noticed webviews loading pages extremely slow - and in some cases failing.

To handle the slow loading - I have a floating group with a spinning loading spinner that shows and then hides after 4 seconds. Janky - but at least it tells the user it’s loading rather than a white screen in the webview.

Many times 4 seconds is not enough. Which proves how slow the webview loads.

1 Like
3

Appreciate the input! Is it slow for something data search intensive or typical across all types of screens?

4

all - even without data

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.