This is only Translation plugin you need!
This plugin combines functionality, flexibility, and seamless integration, making it an essential tool for every Bubble developer.
Unlimited Translation : Translate as much content as needed without any additional costs. One-Time Payment : Pay once and use it forever—no recurring fees. Top-Notch UI : An intuitive and easy-to-use interface. Customizable Design : Tailor the translation elements to fit your app’s unique style. Workflow Integration : Trigger translations within workflows seamlessly. Language Selector Widget : Includes a built-in UI for users to select their preferred language.
This plugin includes two powerful elements: Translator Widget: A ready-made UI for easy language selection and translation. Native Translate Element: Designed for users who prefer to build their own custom UI while leveraging translation functionality.
Is This Plugin for You?
Bubble Language Translator is perfect if you’re looking to:
Expand your Bubble app’s reach to a global audience.
Offer a multilingual experience without complex coding.
Provide users with a personalized, native-language interface.
Streamline translation workflows within your application.
Hi, your plugin looks great. However befire purchasing, I need to understand if the plugging supports custom translation of single elements. Sometimes Google Translate results aren’t 100% accourate and I would like to be able to change few translated items.
I understand that you’re looking for a way to manually adjust translations for specific elements, as Google Translate may not always be 100% accurate.
Currently, the plugin is built on the Google Translate widget, which does not support manual customization of individual translations ( i.e. to modify specific words or phrases ). Unfortunately, this is a limitation of the widget itself.
We rely on the Google Translate widget for all translations. Since it’s provided directly by Google, there aren’t any user-imposed rate limits on its usage through our plugin. Translation failures would typically be due to issues on Google’s side rather than any limits built into the plugin.
I am looking for a way of translating my app too and till now doing the translation on my own seems to be the best (but very time consuming) solution. However, I have a doubt about using the DB. Isn’t this option WU consuming? I mean the way I see this happening is adding on my data type a new field for the language and then using a conditional when dropdown Language value is French…display the value in the French field of my data.
You’re absolutely right…storing multiple language versions in the database and using conditionals to display them can become WU-intensive, especially if you have a lot of dynamic data being loaded.
This plugin works by automatically translating your static and dynamic content on the page using Google Translate, without needing to store all translations in your database. It detects and translates visible content in real-time (including content rendered dynamically), which keeps your DB clean and avoids unnecessary WU usage.
just bought ur plugin and can’t say I am satisfied neither that is ur fault for this. We all know Google Translate is poor. Are you thinking adding a tool to let us edit the translation? Maybe something where we can use custom states rather than db storage? I am sure there will be plenty of Bubblers willing to pay more for this option.
Actually using your native translate element I managed to achieve what I want and basically I can display the correct translation. On the text itself…I use a conditional “when dropdown Language value code is XX” the text should be XXXXXXX. And it seems it is working fine as my conditional seems to go over the google translation and displays my text.
However, there is a problem with your plugin and you need to adress it: it does not translate a reusable element used in a repeating group. In my case the reusable element triggers a popup also and although the popup is partially translated, I cannot do the trick with the conditional cause I need a native translate element on the reusable element in order to call it.
Thanks for the feedback! I’m glad to hear it’s working for you in most cases
About the issue with reusable elements inside repeating groups…could you please share a quick Loom video showing the problem on a test page? That’ll help me understand it better and work on a fix.