Native Mobile App is bugging!

Mobile Beta
1

I would like to first say that the native mobile editor is a game-changer!!! Amazing work by the bubble team.

However, it’s not quite there yet. (especially for the upcoming price changes). There’s still a lot of work to be done.

  1. Password reset!! - Some of my users have been logged out of their accounts for days now because the password reset is bugging!
  2. Signup/loging with OAuth (social) doesnt work properly. Especially on android! It could’ve been a great way to go around the “forgot password” issues for now, but that’s bugging as well.
  3. I keep getting warning messages from Google Console about (a) updating the target API levels, (b) the app supporting 16 KB memory page sizes, and (c) a whole lot of app crashes and risk of the app being removed entirely if the violations are not fixed!

Among other issues, like the app taking forever to start up!

I’ve had users delete the app entirely from their phones cause of this.

I know you are working tirelessly to resolve most of these issues, but to be honest, you are rushing to start charging for a service that still needs a ton of work done!

I currently have 1300 users on my app, and I can barely keep up with the complaints and bugs.

Strongly considering other options!

4 Likes
2

I’m having similar issues. Contant errors on Testflight. App works perfectly on BubbleGo but so many problems on Testflight. These bugs need to get resolved otherwise I will also look at other options.

3

@nick.carroll can we make this a focus? Above anything else, the sign-in process is what makes or breaks user acquisition. It’s hurt my business tremendously having users confused by password reset not working and outdated apps not refreshing properly. When a user comes back onto an outdated app they aren’t being told it needs to be refreshed, only after performing a data action the update app screen is shown. And even then, when they refresh their app (if it is an ota), it often takes 1-2 refreshes for the newest version to be pulled.

1 Like
4

The refresh issue is really bugging us. On our app, we have some actions that run on index page load. When an OTA is pushed and old versions deprecated, user who load their app on that moment have to close and reload like 1-2 times before the new loaded app takes effect. This sometimes creat the impression that the app is broken😩

@nick.carroll what is the best practice for this?

5

Yea my users are complaining about the exact same thing. I hope the team can find a way to push OTA’s without restarting the app.

6

we are going to be investigating this behavior holistically so we can get something performant and consistent in place

1 Like
7

I agree. Native mobile is an amazing start - but I’m not ready to move my PWA users over to native.

Here’s whats holding up my decision:

  • Image upload is extremely slow - uploading more than 1 image feels broken (that slow).
  • Search with Algolia needs to be done via REST api which is so much slower than Algolia’s SDK. There’s no way to implement fast/powerful search over 100k + rows. PWA users are used to amazing search experience.
  • There’s no way to display initial content in a selectable list if list allows more than 1 selection (known bug).

My users would feel like we downgraded features - while forcing the painful switch to native.

I’m a huge fan and need native. There’s so many benefits on native, like: app store distribution, GPS, and native swipe feel.

3 Likes
8

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