Just like I did a few times previously on the forum, listing improvements that could be implemented in the web application editor to improve the “quality of life” of those who use Bubble. I’m going to start here a list of feedback that I will give over time as I test the mobile editor, based on things that have already been implemented (elements, actions, etc.).
To begin, I will compare the existing elements (one by one) with the current web editor. Obviously some elements do not apply in this comparison, so I will not include these.
Starting with the inputs, in the images below we have examples of common Inputs, on which I tested all types. Both examples were tested under the same conditions (same styles, same types, content, etc.).
Here are the results:
COMMON INPUTS
- Input (text):
OK - Input (email): OK
- Input (password): OK, but…
I have some suggestions here. As we currently cannot use plugins so we cannot natively show/hide the password (which is always a good practice from a user perspective).
Although we can currently use this in WEB EDITOR and probably in the future in MOBILE, why not make this a native action?
In fact, other options would be extremely important to specifically control some password input, such as checking whether the input meets the most common and main password policy. Currently we can measure the strength of a password, but what about exposing data such as the presence of special characters, capital letters, numbers, length, etc.
This is currently only possible with plugins or the use of regex, I even built some private plugin to this use case and much more manipulations that I think is important (maybe I am going to release it soon to community). But considering that the basis of Bubble is to democratize knowledge and application development for non-technical people, why not have these options in the password type input, natively?
Additional things for text inputs like allowing to remove multiple spaces in the middle of strings and not just at the extremities (like when using the :trimmed operator), or even the option to switch between the “on change” and “on input” methods that would make it much easier to handle instant type/search in many cases with no need to, again, resort to plugins or custom code.
- Input (integer): does not show the the thousand separator in MOBILE
- Input (decimal): does not show the last two zeros in MOBILE (but this does not affect the real value)
- Input (address): when we use the browser’s autofill the corners do not respect the border radius on MOBILE (this occurs to any input filled in this way).
- Input (US phone): does not apply the style to the input and also does not apply the phone mask.
- Input (percentage): does not apply the percentage symbol and keeps the value as decimal (only visual issue as it does not affect the real value)
- Input (currency): does not apply the currency symbol and also the thousand separator.
- Input (date): applies the full data/time format by default in MOBILE (this does not change the date/time in fact, but prevents to display any custom/most common formats.
- Input (euro date): same as above.
- Input (text - numbers only): does not apply the style to the input.
MULTILINE INPUT
- OK
CHECKBOX
- OK, but…
The checkbox showed an improvement in the MOBILE version. Although both share the same style in the example, it has additional options such as choosing the icon (including its size and color), which we do not have in the WEB version. In addition, the WEB version always had the label a little misaligned in relation to the icon and limited the choice of icon, which made us always resort to building our own customized checkboxes. But I believe (and hope) that many of these improvements will also be reflected in the WEB version.
DATE/TIME PICKER
It looks like it will have some small changes compared to the WEB version (Date or Time instead just Date or Date & Time). According to what I’ve seen elsewhere it would be something completely new, but at the moment it’s not even rendered in preview mode.