How to localize onboarding for multiple languages and support

Are you faced with the challenge of localizing onboarding to meet your user’s language and location?

Well, we’ve got good news. We’ve got a tool that helps you identify, modify, and create content for your users.

And, when you know that localization can boost international client usage by 17%, and reduce costs by 34%, it’s worth investing in content localization from the start.

In this article, we’ll show you how you can localize your onboarding and content to your users.

How to localize onboarding content?

To localize content, you’ll need two things: An onboarding flow, ‌and the ability to create content in different languages.

Option one: There are ways to build and develop all the onboarding features and language codes (not to mention RTL formats). But that takes time, resources, and continuous development.

Option two: Another option is to choose a user onboarding tool that equips you with all the features you need like localization, customization, and user segmentation power tools.

In this article, we’ll focus on how Product Fruits helps our clients with localization — because it’s quick, easy, and cost-effective, AND we see success with our customers on a daily (of course we’ve got to brag…)

What is Product Fruits and how can it help localize content?

Product Fruits is a Digital Adoption Platform. That means we give you the tools, analytics, and customization options you need to create onboarding flows that convert.

A few key points: It’s no-code, it acts as an invisible layer on top of your product, and installation is a breeze.

Here’s how we help you localize onboarding.

Product Fruits offers an automatic set up of supported languages

Product Fruits a broad selection of supported languages in the app.

To localize content, you start by selecting the languages you want for onboarding.

(Source: Product Fruits)

By selecting your chosen language(s), every Product Fruits tool will display a dropdown with those options.

To help you see how easy it is, this is what the language choice looks like:

(Source: Product Fruits)

This dropdown option will allow you to edit content for each onboarding feature, for example: tours, hints, or checklists.

Does Product Fruits automatically detect the language of the user?

Although Product Fruits doesn’t necessarily automatically detect the language of the user, this is what actually happens upon integration:

First things first, because Product Fruits is a no-code tool, we pride ourselves in easy implementation and ease of use.

That means, when you first set up Product Fruits, you’ll need to introduce an installation code snippet — Don’t worry, it’s very fast and easy to do. Think of it as something similar to adding a Google Tag Manager.

This code snippet allows for certain information to be passed between our applications.

The Product Fruits code snippet contains a language parameter that determines the current language of the user. This will help us determine which language to use for displaying products.

Curious to see what the installation process looks like? You can read our installation guide.

Fruity Tip: You might consider showing distinct tours or tips based on the language, or limiting the tours/tips to specific languages. To do this, use the “Display for” settings in the tour/tip section. Then, select Rules -> add condition -> Language and select the preferred language.

How to introduce Right-to-left (RTL) onboarding support

Product Fruits supports RTL natively. As a default, we will inherit RTL settings from your own application.

For example, if your application has the “RTL” attribute in your code, Product Fruits can read this and display all Product Fruits content in RTL format.

Fruity Tip: Connect your onboarding features and flow to a knowledge base. His allows users to find support resources instantly and without relying on your support team. And bonus: Product Fruits supports RTL in our Knowledge base, which allows you to edit, and switch formats easily.

You can read our full support document here