I’m currently working on a Bubble mobile app, and I need to run JavaScript and display dynamic HTML, but it seems this isn’t possible yet in the new mobile environment.
Has anyone found a way to make this work?
I’m trying to display text from my database and make each word clickable.
When a user clicks on a word, I want to retrieve that word and its context to trigger a Bubble workflow.
On the web version, everything works perfectly using the Toolbox plugin and custom JavaScript.
However, on the mobile version, Toolbox doesn’t work, and there’s no HTML element to insert rich content.
So I’m wondering if anyone has managed to:
Run JavaScript inside a Bubble mobile app (without Toolbox)?
Display dynamic HTML (e.g. clickable <a> words or custom CSS classes) in a mobile page?
Or ideally, trigger a Bubble workflow when a specific word is clicked in the text?
I believe this issue affects many projects aiming to make their Bubble mobile apps more interactive.
Thanks a lot in advance for any tips or workarounds
If you’re unsure whether these plugins meet your specific needs, I recommend reaching out to @ZeroqodeSupport directly or reading the documentation. There are other similar plugins available in the marketplace that offer comparable functionality, but these are the ones I’ve personally used and can vouch for, you can find them by filtering by “mobile” and search for toolbox, webview or websync
Thanks for reaching out!
On Bubble Native, inline <script> in HTML/MRTE won’t execute inside the WebView, so the reliable path is using Toolbox for Bubble Mobile to run JavaScript and pass values back to Bubble.
The flow we recommend is: render your text as HTML (wrap each word: <span data-word="X">X</span>), run one delegated click/touch listener via Toolbox → Run JavaScript, emit the clicked word (and any context) with the plugin, then continue your Bubble workflow from the plugin’s “value received” event. This avoids per-word listeners and works consistently on iOS/Android.
Docs: Toolbox for Bubble Mobile
Could you confirm a few details so we can tailor exact steps (listener snippet + emit key names)?
Which element renders the text: Text (interpret as HTML), MRTE, or WebView?
Is your text already wrapped with tags/attributes (e.g., <span data-word>), or is it plain text?
What data should we return: just the word, or also index/sentence/record ID?
Target devices/OS versions where this will run (iOS/Android)?
Thank you.
Once we have these, we’ll share the precise action setup and event configuration for your case.
