Icon color isn’t changed correctly by condition (works sometimes, doesn’t work other times).
“Toggle element” action doesn’t show the element
Condition on element “When element X is visible, this element isn’t visible” condition doesn’t correctly show/hide the element.
Workflows incorrectly say they have 0 triggers.
Notification “Workflows could not run because too many events triggered at the same time.”, even though no workflows should have been running at all.
Can’t modify values of inputs on Web Preview, making testing impossible where fields are required.
Horizontal Lists can’t have dynamic height (fit height to content) because their ListItems are always set to “this elements height is filling it’s container”, which always makes its container (the Horizontal List) 's height 0 unless you set a fixed height.
Horizontal List doesn’t have “Fit width to content” option, which breaks ability to center it when you have a dynamic (content-driven) width. You have to pick either fixed width or ability to center, but can’t have both.
Page heights in web preview aren’t accurate to how it works on mobile.
No indication on web preview when editor has changed.
No debugging tools of any kind available.
Actions that should be lightning fast (frontend UI changes, minor data-based updates) take a long time.
Have I submitted tickets for these?
I know that to be a good citizen I should submit a bug report for each of these. But that means taking time to articulate how to reproduce the errors, making demo videos, isolating the problem, keeping a copy of the problem area accessible for Support to see the behavior (either by avoiding making a workaround, thus completely halting development, or by preserving it on a separate branch that I’m paying for), and responding to Support’s empty answers to keep the ticket alive. FOR EACH THING. And for any of these which can’t reliably be reproduced, Support will eventually close the ticket anyway.
Despite all of this, I do try to create tickets when I have time… however, the paradox is that all of these things slow me down, which means I don’t have time to submit support tickets.
This is why I’ve stopped working on my app for now. Not having a way to test in the mobile view is ridiculous and hearing crickets from the support team is even more ridiculous.
Impossible to have floating groups on sheets. (note: it’s possible with a RE sheet ONLY if vertical list…not scrollable).
Google maps auto-complete search for addresss (like in web). I need to API to google maps and it’s so slow.
No way to hide keyboard in multi-line input or in singple line input when decimal or integer.
Going to a view AND resetting stack is slow.
Copy link (there is a share sheet plugin for iOS)
OTA updates break app and send users in update loop. Nick said this in in the works today tho
I’m in the same boat with bug reports. Bubble support replies and there’s no reference to what bug report they’re talking about in my email thread (when they reply). So I can’t simply respond with email…I have to open the browser messenger in bubble.
In short - it’s not easy having muliple bug reports going on at once. Your email will be confusing.
Thank you to all the Developers out there banging on Native Mobile. I personally was not up for such a huge task of being an unpaid Bubble employee, so I’ve opted to sit out Native Mobile until it’s usable.
Big applaud and gratitude to all those who are doing the tough task of using their personal resources to help push the platform forward. The reward you will receive of improvements and hopefully a working app are not sufficient for the amount of work and effort you will put into helping Bubble.
Bubble should consider free subscription plans for anybody building in mobile native and taking their own time to report or post about issues. They should also implement in editor bug reports and screen captures to make the whole process less involved for the developers taking the time to bang on the system.
From what I recall, both mobile native and AI are currently free, but I think Bubble has been stating publicly that they are unsure of the payment structures they may or may not introduce for both. I’m not sure, Bubble has caused me to always question my own memory. But I’m pretty sure there is not clarity from Bubble on these points yet, and they have left it publicly ambiguous.
