How to build instant 9-language "Polyglot Search" with Deep Linking & Partial Matching

[boston85719]

@dhasanovic88

To the user, it just looks like a quick flicker or a fast reload, but under the hood, we are forcing the app to re-fetch the correct language strings. Sometimes you have to think like a magician—hide the technical constraint behind a snappy interaction

You can get magician like quick change with no flicker or page reload without using app text or url parameters and instead use url path lists (better for SEO)

Why I no longer will use App Text

No, I actually meant I will no longer use App Text No. While true, there is more to the expression than simply referencing app text, it is not like you explained. [Screen Shot 2023-09-29 at 8.30.52 PM] [Screen Shot 2023-09-29 at 8.30.47 PM] As mentioned, I don’t use the ‘users language’ and I instead use the URL path item #2 (akin to a sub-folder for language - but within Bubble constraints). I don’t need to load all option sets (they are pre-loaded anyway as that is part of their built in…

By not using app text and url parameters, you can get faster language changes on web when switching from default english to user preference…you can also get more SEO benefits from URL path lists instead of the URL parameters.