26

I recall Bubble employees mentioning this in the past and assume for every single element type that exists for native mobile and the existing web apps, we can do this simple operation.

I’d also imagine that the ‘convert to another type’ function will exist within the mobile editor as well, so if an existing web app type of element, such as popup, doesn’t exist for mobile native, we can simply click onto the popup and use the convert to another type button to select the appropriate native mobile container type that is the popup equivalent/replacement.

They likely will retain this for workflow triggers as well, which works even better than convert to another type compared to elements, since the workflow trigger conversion is not restricted to the ‘type’ as the element conversion is. I doubt they will have built this out as a new function for workflow actions though, so likely a need to tweak the workflow action series to include new action types only available in mobile native.

I wouldn’t expect Bubble to be completely changing the way workflows work in regards to data and all elements that are available for the web apps and native apps, but instead may find new actions or triggers available in native apps that are not available in mobile apps like sending push notifications or vibrating a device. I don’t think Bubble would be building it out in such a way that it is a completely different system that requires building a new UI and front end workflow for every single mobile view.

Maybe @georgecollier could speak more to what workflows need to be built new without spilling too much about the native editor than Bubble wants the alpha testers to publicize.