Probably won’t be until early next year till we get access to it. Latest update I read was that there will be a demo of this feature (not a launch) at Bubblecon and a select few users from the waitlist will receive beta access early Q4.
Given the complexities of launching a mobile native feature and Bubble’s recent struggles to keep the web version running smoothly, I’d temper my expectations a bit.
I’m excited nonetheless and have to applaud the efforts of the Bubble team so far!
Early 2025 is the current official line (ref.)
@tylerboodman which wrapper supports background geolocation?
As @senecadatabase mentions, Progressier is great for PWAs
But unfortunately Progressier cannot fix Apple’s (deliberate? anti-competitive!) bugs that make PWAs inferior to native iPhone apps.
For example, Apple broke the PWA Screen Wake Lock functionality in iOS 16.4:
Here we are 18 months later still waiting for Apple to fix the bug so PWAs can once again keep the screen awake, like native – will Apple ever fix it? Seems doubtful at this point.
Unfortunately I feel compelled to build a native app rather than continue using PWA. Apple is monopolistic!
Curious if this will be bundled into agency plans, my brain says yes, but since I haven’t heard anything about it, I’m a little worried it won’t.
Also, it will be really nice to convert all of these wrapper apps I’ve built over the years into a truly native app. I’m TOO excited for this.
That’s the 3rd delay so far, my money is on a couple more
@nick.carroll Hi, do you know when native transitions might be supported? Currently, hiding and showing pages doesn’t quite provide that ‘native’ feel.
It would also be great if we could build components and plugins for the React environment.
Are you previewing on web preview or BubbleGo?
We are previewing on web preview!
@nick.carroll what is the timeline for rolling out the Beta to all users on the waiting list? I signed up last year when the waiting list was first opened after Bubblecon 2023 finished…I think I’ve signed up 3-4 times since then when announcements via emails were sent etc.
Is there an internal strategy in terms of allowing X number of users to access every X number of days, or is there a strain on the system and so the rollout will be quite slow to get users from waitlist to access?
We have started pulling users off in small batches to get a sense for the amount of load on the build pipeline & bug ticket process and will start pulling larger batches as we near the end of the year
Any further updates on this. New batch of beta users?
There are some of us who really needs this and do not just want to play around - is there a option for prior releases? i have a mobile first app client - i would pay to get in beta - i am registered 20 times now in the page and since day 1 plsss
Same here. I have 3 clients ready to sign but only if I can provide native mobile.
Just saw this in the monthly update
Just because you can do mobile native right now doesn’t mean you should.
I’m telling clients that it’ll be worth waiting until mid-2025. Until then, as great as it is, there’s not enough elements / too many hacky workarounds that make it very very difficult to build an app that is maintainable (for example, reuseable elements were only added like last week, so I don’t know how people were building maintainable apps until then…)
I’ve been fortunate enough to have access to the mobile beta for a few weeks. It is going to be so awesome for us Bubblers.
But keep in mind that it is very much in beta now. Native features that your clients will require are simply not available to us yet—whether they’re built and hidden or just not built yet.
Looking closely at the Bubble Docs, you can see a whole section on Native mobile apps. Read even closer, and you can understand what is available so far. Also, look at the November Community Update and see what Josh is highlighting as a priority on this front…
My take is that the team is prioritizing the foundation stabilization before pumping out native features and elements, which makes complete sense. I also agree with the slow rollout of the beta list because they would get slapped with support tickets if they did larger batches.
TL;DR =
Timeline update for non-beta?
@graham3, check out this thread from @fede.bubble:
