What goes in your app and what lives in Engage?
If your app uses React, a developer can add Frigade Engage’s built-in guide or checklist components. An Engage flow supplies the content and tracks its state, such as whether a step is complete. Decide which real action should complete the step.
After a developer integrates the needed provider and publishing channel in your app, your team can publish supported flows to that channel without changing code each time. If you use the headless JavaScript SDK, it supplies the logic and your app provides the interface. Decide which visitor or activity information the guide actually needs before connecting it.
Which Frigade price applies to your onboarding flows?
Ask for the current terms for Engage and confirm how your account counts usage. The public Frigade pricing page labels its figures as Assistant pricing.
What should you test and keep outside the dashboard?
Check how a keyboard user enters the guide, reads the current step, leaves it and returns to the app. Keep the flow copy, labels, completion rules and the source for your own components separately.
The documentation shows progress in the dashboard. Check what your Engage account can export before relying on transfer of flow definitions or user progress to another service.
How do you show the difference between dismissing and finishing?
Draw a checklist for a fictional workspace. Use no account, app connection or data.
- Close the reminderLeave Create a workspace incomplete when the user dismisses it.
- Draw an actual workspaceMark the step complete only when the fictional workspace exists.