Dashboard
Generate with AI
Show PlayStep your app, get tours written for it step by step, then record a clip for each step.
Generate with AI looks at your app and suggests guides: which element each step points at, its title and text, how it completes, and a note on what to record for its clip. It does not make videos. You record those, and each step tells you exactly what to show.
Start from Guides › New guide › Generate with AI.
1. Show PlayStep your app
Pick one way. Each analysis keeps its screens for 30 days.
| Way | How | Works behind a login |
|---|---|---|
| Web app | Create a capture link, open it, and click through the pages your users need help with. Needs the PlayStep script or npm package installed. | Yes |
| Flutter app | Run your app with the capture token: flutter run --dart-define=PLAYSTEP_CAPTURE=cap_…, or pass captureToken: to PlayStep.init. On Flutter web, the capture link works too. | Yes |
| Public website | Paste an address. PlayStep reads up to 10 public pages on the same site. | No |
A capture link opens a small panel in your app. Nothing is captured until you press Start capturing. Then every page or screen you open is added, and the dashboard lists them as they arrive. Press Finish when you are done. Links stop working after two hours or at Finish, and work only in the app they were made for (an SDK running with one of its keys).
What is captured
For each screen: its path or route name, its title and headings, and the elements people use (buttons, links, tabs, menu items, checkboxes, and fields' labels and placeholders). For each element, PlayStep also records a way to find it again: its data-guide / GuideAnchor id if it has one, otherwise a CSS selector (web) or its text, key, semantics label or tooltip (Flutter).
Never captured: what anyone typed or picked in a field, anything inside an element marked data-private, and screenshots on the web. Flutter apps can opt in to small screenshots with captureScreenshots: true. Emails, phone numbers, long numbers and tokens in labels are masked on the device and again on our servers.
2. Say what users should learn
Optional: what to focus on, who the tours are for, and how many to suggest. Then press Generate tours. It takes up to a minute.
3. Review the suggestions
You get tours in different shapes:
| Kind | Starts |
|---|---|
| Onboarding | On a new user's first visit |
| Task walkthrough | From the launcher, for one key workflow from start to finish |
| Feature spotlight | When someone opens the page it is on |
| Empty state help | When someone opens a page that starts empty |
Each step shows the element it points at, how it completes (a tap on the element, or Next) and what to record. The AI can only pick elements PlayStep captured, so every step points at something real. Choose Create draft, Create all, Try another version for a different take on one tour, or Dismiss.
4. Record the clips
Open a draft. Steps without a clip are marked, and each step says What to record, for example "On Invoices, click New invoice and wait for the form to open." Choose Record or upload to add the clip right there. You can publish without clips; those steps show text only.
Then preview and publish as usual. The guide plays on the web and in Flutter without code changes: steps find their elements by selector (see Anchors).
Limits
| Plan | Generations per month |
|---|---|
| Free | 3 |
| Pro | 50 |
A generation counts once it finishes; one that fails does not count. Each app runs one capture crawl or generation at a time.
Privacy
Captured screens are sent to Google's Gemini API to write the suggestions. PlayStep uses a paid API plan, under which Google does not use the data to train its models. Screens, screenshots and suggestions are deleted after 30 days, or when you delete the app. See the privacy policy.