Decrease time-to-value for Pro Trial users

[gstout52]

Epic

#3839

Description

As a new FFC Team trial user

I want to get started using FlowFuse quickly

So that I can validate that FlowFuse is the right tool for me.

Built into our GTM strategy is the assumption that new FlowFuse users are already familiar with Node-RED. So, it is sensible to begin the onboarding experience of new FlowFuse users with that in mind.

This story calls for a revised onboarding flow that begins by asking the new user if they have existing Node-REDs running elsewhere that they would like to import to FlowFuse.

Since returning to the Team trial (and away from letting users choose any tier upon signup), the percentage of users opening the editor within one hour of signing up is around 60%.

This work is expected to improve that even further.

The new flow should proceed as follows.

1. The user signs up and lands in the app.
2. The user is welcomed and asked if they would like to (A) connect existing Node-REDs or (B) start from scratch. If the user chooses to start from scratch, the current onboarding tour begins immediately.
3. If (A), the user is asked where the existing Node-RED is running: locally, in the cloud, or on an edge device. Options are provided for each possibility.

Which customers would this be available to

None

Acceptance Criteria

• [ ] criteria 1
• [ ] criteria 2
• [ ] criteria 3
• ...

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[joepavitt]

If (A), the user is asked where the existing Node-RED is running: locally, in the cloud, or on an edge device. Options are provided for each possibility.

Offering them the chance to paste in flow.json would be a nice opener, we also (currently) only provide a blank Node-RED instance by default. We could offer an alternative "default" flow, including Dashboard, etc?

I have concern about offering them the change to connect edge Instance as the first thing, we've seen from the free trial, currently, it's cumbersome to do this.

[hardillb]

We could offer an alternative "default" flow, including Dashboard, etc?

Isn't that just a Blueprint?

[joepavitt]

@hardillb Yes, absolutely, but currently the default-created Hosted Instance on Team Trial doesn't use a Blueprint

[gstout52]

I think the first approach should be to let them connect existing instances, wherever they are. Work in progress for the device agent installer will help, but if we don't agree that the process is now officially easy, then the backup can be: help the user connect existing Node-RED running elsewhere than on the edge devices, then offer blueprints, then offer to connect edge devices.

I believe the work in https://github.com/FlowFuse/device-agent/issues/364 and https://github.com/FlowFuse/device-agent/issues/401 should make the process of connecting edge devices much easier and faster. But if we're not there yet, then we don't want to slow the new user down immediately upon signup.

[hardillb]

but currently the default-created Hosted Instance on Team Trial doesn't use a Blueprint

Ahh, OK, that distinction was what I had missed.

Only counter point is that installing the Dashboard will slow down provisioning of the Instance as it will need to install at startup.

[joepavitt]

should make the process of connecting edge devices much easier and faster

The only real step that the Install Scripts bypasses is the need to install NodeJS ahead of the Device Agent. Other than that, the onboarding experience will be very similar.

[gstout52]

Let's move forward with this by inviting the user to choose whether to start from scratch or import existing Node-REDs upon account creation.

[joepavitt]

import existing Node-REDs upon account creation.

How do you expect this to go down from a user experience perspective? Drop in a flow.json enough, because they can just do that in 2 clicks once the Editor is available anyway.

[gstout52]

Let's do this (splitting out each step 3 in the issue description):

• Remote instance: walk through remote instance setup workflow that currently exists
• Hosted instance: Ask the user if they have an existing flow.json they would like to begin with, and create a new instance from it. The important step here is that we do it before the user has to enter the automatically-created instance and find the Import menu for themselves.

[joepavitt]

This flow doesn't work though, we have to spin up the Hosted Instance as early as possible in order to prevent the user from having to sit and wait for it to spin up. Having something is better than nothing, and having to wait 5 mins for the instance to spin up, in my opinion.

This onboarding will also then differ depending on tier, as with Starter, there is no "Remote Instance" concept available. I need much more detail here, mockups of the questions/onboarding flow would be most helpful, even just post note details the path you're expecting a user to follow.

[gstout52]

Pushing this back due to size of 2.20 release, and other work on a new product tour to accommodate the changed home page.

[gstout52]

Pushing back again. With Tables offering and additions to the Performance feature, it's sensible to see how users engage over the next few weeks and design an onboarding path that optimizes their paths.

[gstout52]

It is on me to sketch a flow, but with the FlowFuse Expert Assistant, and @cstns with the work you're doing on creating , we're now in a position to have a much quicker time-to-value for new trial users.

[gstout52]

@cstns Here is a mockup of an improved new signup flow: https://www.figma.com/board/B5O9ZCPNufeyXnDqPxKDZQ/Onboarding?node-id=8-11&p=f&t=SDZIN0FtgaYs3ViV-0