Install Product Fruits into Your Application

After signing up, choosing your plan, and getting familiar with the Product Fruits interface, the next step is to connect Product Fruits to your own application.

This step is called installation. It allows Product Fruits to appear inside your product, so your users can see the tours, hints, checklists, announcements, surveys, and other in-app experiences you create.

You can click around Product Fruits before installing it, but you will understand its real value only when you see it working inside your own product, with your own pages, users, and onboarding goals.

Why Installation Matters

Product Fruits works on top of your application. To do that, it needs to load inside your product and recognize the user who is currently signed in.

Installation makes it possible to:

Show Product Fruits content inside your app
Display the right content to the right users
Test your onboarding on real pages
Understand which users have already seen or completed content
Build experiences that match your actual product flow

The installation snippet is a small technical step, but it helps you answer the important question early: will Product Fruits work cleanly in your app, with your users and your UI?

Is Installation Difficult?

In most cases, installation is quick and straightforward.

A developer may need to add the Product Fruits code to your application, but this is usually a small task, similar to adding an analytics, chat, or support tool.

Your developer will need your workspace code. You can find it in Product Fruits administration in the Installation section. Each workspace has its own workspace code.

Why Each Workspace Has Its Own Installation

A workspace is like a separate container for your Product Fruits content and settings.

For example, you may have:

One workspace for testing
One workspace for your live production app
Separate workspaces for different products or environments

Each workspace has its own code because Product Fruits needs to know which content and settings to load. If your developer installs the testing workspace code, your app will load content from the testing workspace. If they install the production workspace code, your app will load content from the production workspace.

This helps you test safely before showing content to real users.

What To Prepare Before Asking Your Developer

You do not need to understand the technical setup in detail. Your developer will choose the right installation method for your app.

Before sending them the developer docs, it helps to prepare a few simple details:

Which workspace should be installed first
Whether Product Fruits should be installed in a test environment or the live app
Whether you want to target content by simple user details, such as role, plan, language, or sign-up date

Product Fruits also needs a reliable way to tell users apart, so it knows who has already seen a tour, checklist, or hint. You do not need to decide the technical details yourself. Your developer can usually use the same user ID or email address your app already uses.

You can start with the basic required information and add more details later if you need more advanced targeting.

What Happens After Installation

After Product Fruits is installed, you can test your content where it will actually appear: inside your own product.

This means you can check whether:

Your tour opens on the correct page
A hint appears next to the right button or field
A checklist is visible to the right users
Your content looks good inside your real interface
Everything is ready before you publish it to users

The browser extension helps you build and preview content, but installation is what makes Product Fruits part of your real product experience.