We’re bound by NDAs for specifics but here’s my thoughts:

  1. Mobile native is a lot better than I was expecting
  2. Mobile native is being developed quickly (looks to be quicker than web!) I said to Bubble I wasn’t sure how they could outpace the competition e.g Flutterflow, but they seem confident that they can due to the technical differences between the platforms.
  3. Backend workflows are shared between the mobile and web apps. Reuseable elements, UI, and front-end workflows are not. That favours our apps that are BE workflow heavy (we tend to build like that for maintainability).
  4. Mobile native is truly mobile native (because it is). It feels like a mobile app, not a progressive web app (again, because it is React Native).

I don’t know what they’re announcing at BubbleCon, but probably lots more details, maybe showcases of real apps.

Right now, with mobile native in its beta stage, I feel comfortable encouraging clients to launch mobile companion apps (e.g if they have an AI app, creating a companion app that allows them to use the most popular features of the app).

However, if a client came to me looking to build a mobile-first social network, I’d still turn them away, because mobile native isn’t there yet (and why would it be - it’s in beta) and I’m not sure Bubble native would be the right tool for the job. In 6 months, that could well change.

Before being added to the beta, I was really indifferent to mobile native as I just never used Bubble for mobile first apps, and my client’s apps never really needed them. I’d never have recommended a PWA for my clients (whether you agree or disagree, that’s another story).

Now, I think it’s something that Bubble can genuinely support. If you’re considering developing a mobile app, I’d build the web mobile + desktop version as normal. Don’t bother with a PWA, then wait for mobile native, and build the native app when that’s released.

6 Likes