We’re pleased to unveil the WebSync Plugin for Bubble Mobile, a straightforward yet powerful solution that enhances your mobile app by smoothly connecting native and web environments through a React Native WebView, allowing seamless two-way communication!
Key Features:
Seamless React Native WebView Integration: Effortlessly integrate native and web environments for smooth two-way communication.
Supports All Bubble Data Types: Send and receive text, numbers, dates, images, files, and custom app types.
Real-Time Data Exchange: Enjoy dynamic content updates and real-time data synchronization without any coding.
This plugin is ideal for adding interactive web content, integrating external data sources, and enabling real-time communication with no coding needed. Whether you want to embed dynamic web pages or enhance your app with seamless native-web interactions, the WebSync Plugin is your go-to tool!
Thank you very much for your suggestion This is definitely a useful idea and showing a loading bar while the page is loading can improve the user experience We have shared your feedback with our development team for review Once we have any updates on this we will let you know
Feel free to share any other ideas or suggestions we are always happy to hear them
im using the plugin, send/recieve on basic types like text is working great, but not custom types. i simply selected the custom type i wanted to use, is there another step i am missing? Appreciate the plugin!
i notice it says something about api call type, making me think theres another step im unaware of to use costum types.
Thanks for the kind words about the plugin — appreciate it!
You’re on the right track, and your intuition about the API call type is correct.
With WebSync for Bubble Mobile, there is an extra step when working with custom types, compared to basic types like text or number.
Here’s the key point:
Why basic types work, but custom types don’t (yet)
Basic types (text, number, yes/no, etc.) are sent and received directly without any additional configuration.
Custom types require Bubble to know the exact structure of the data being sent/received (fields, data types, nesting, etc.).
Because of that, simply selecting a custom type in the action isn’t enough.
What’s missing for custom types
To use custom types correctly, you need to:
Define the custom type via an API call
The plugin relies on an API call type to describe the schema of your custom object.
This is how Bubble knows how to serialize and deserialize the data.
Ensure the API call returns that custom type
The API response must match the structure of your custom type exactly.
Field names and data types must align with what you defined in Bubble.
Use that API-defined type in WebSync
Once the API call type exists, WebSync can correctly send/receive objects of that type.
Without this step, Bubble doesn’t have enough information to handle the custom object, which is why it silently fails or doesn’t behave as expected.
Next steps
Please double-check that you’ve set up an API call type that defines your custom object.
If possible, let us know:
What the custom type looks like (fields + types)
Whether it’s coming from an API response or built locally
Which WebSync action you’re using (send or receive)
We’ll be happy to look at your setup and point out exactly what needs adjusting.
Just checking in to see if you had a chance to try the steps we shared regarding API call types for custom types and whether that helped clarify or resolve the issue on your end.
If it’s still not working as expected, feel free to share a bit more about your custom type or the exact WebSync action you’re using - we’ll be glad to take another look and help you move forward.
That’s great to hear — thanks so much for confirming!
We’re really happy everything is working as expected now.
If you’re enjoying our plugin, we’d be so grateful if you could take a moment to rate it! You can head to the Plugins tab in the Bubble editor, search for the plugin by name, and leave the stars you think it deserves. Your feedback truly motivates us to keep improving.
Additionally, if you’re satisfied with your experience working with Zeroqode, we’d love to hear more! You can share your thoughts on the following platforms:
Key Features:
