All posts

You vibe-coded an app. Here is how to show people how it works

Your AI coder got the app built in a weekend. Explaining it to the first people who open it is the part nobody prompts for. It takes an afternoon, not another sprint.

5 min read
Isometric illustration of an app window with a small tooltip pointing at a button and a play button card beside it

You described an app, your AI coder built it, and after a few evenings of prompting it actually works. You post the link. The first visitors land on a dashboard full of buttons you know by heart, and they leave within a minute.

It is not that the app is bad. Nobody showed them where to start. You know the path through your app because you prompted every screen of it. A first-time visitor sees the whole interface at once and has to guess.

The fix is small: a welcome message, a short guided tour of the one thing your app is for, and a video you can post wherever you launch. This post shows how to do all three in an afternoon, without adding code you then have to maintain.

Why AI-built apps need a tour more than most

Hand-built apps tend to grow one screen at a time, and their makers notice where users get lost along the way. Vibe-coded apps are often different:

  • Everything arrives at once. A prompt like “add a settings page with team management and billing” produces ten features in one go. The interface is complete before anyone has tried it fresh.
  • Labels come from the model. Buttons get names like “Workspace hub” or “Generate insights” that sounded right in the prompt but tell a new user little.
  • The happy path is in your head. You know that step one is “connect your data” because you wrote that prompt first. Nothing on the screen says so.

A tour does not fix any of that, but it bridges it. It walks a visitor along the path you had in mind, until they get the result your app exists for.

What you actually need

Not a full onboarding system. For a first launch, three things cover most of it:

WhatWhere it livesWhat it does
A welcome popupIn your app, on first visitSays in one line what the app does and offers the tour.
A tour of three to five stepsIn your appWalks the visitor to the first useful result.
A 30-second demo videoYour landing page, X, Product Hunt, READMEShows people who have not signed up yet what they will get.

The tour and the video show the same flow. So it makes sense to make them from the same clicks.

The obvious route: prompt a tour library

Your first instinct may be to ask your AI coder: “add a product tour with react-joyride” or a similar library. That works, and for some apps it is the right call. Know what comes with it:

  • The tour lives in your code: every step is a selector and a text string in a component.
  • Changing a word means a prompt, a review of the diff and a deploy.
  • Steps point at elements by selector. When your next prompt rewrites a component, the selectors may silently stop matching.
  • A video is a separate job with a separate screen recorder.

If you like having everything in code, go ahead. If you would rather not re-prompt your app every time you want to change a tooltip, there is another way.

The other route: click through your app once

Stepsome is a Chrome extension that builds the tour on top of your running app. You open the app, press Alt Shift T, and click through the flow the way a new user should. Every click becomes a step, with a spotlight on the element and a tooltip you type straight into. Your app keeps working while you do this, so you can follow a real flow across pages.

Then you publish one file. Your AI coder puts it in your project, which is the only code change, and you do it once. After that, changing the copy or adding a step happens in the editor, not in your codebase. See How to add a product tour with your AI coder for the install, prompt included.

The same steps become the video. Click Make video and Autopilot replays your tour while recording it, then opens the Studio with zooms already placed on every click.

An afternoon, step by step

  1. Decide the one result (10 minutes). What should a new user have done when the tour ends? Created a first project, generated a first report, sent a first invoice. One result, not a feature list. User onboarding for SaaS explains how to pick it.
  2. Seed a clean demo account (15 minutes). Ask your AI coder for a seed script, or set one up by hand: realistic names, no lorem ipsum, no test data with your own email in it. You will use it for the tour and the video.
  3. Click the tour (15 minutes). Open your app, press Alt Shift T, choose Add steps by clicking and walk to the result. Click Popup to add a welcome step in front. Hold Alt while clicking anything you want to point at without triggering it, like a Delete button.
  4. Rewrite the step texts (20 minutes). Stepsome writes a first title for every step, like “Click “Save””. Replace each with what the user gets. How to write product tour copy has the rules; the AI copywriter can do a first pass with your own Anthropic or OpenAI key.
  5. Install (10 minutes). Publish the tour, download the site file and paste the ready-made prompt into Cursor, Claude Code or Lovable.
  6. Record the video (20 minutes). Click Make video, let Autopilot run, then trim and export. Make a launch video of your side project covers the details.

What it costs

For a first launch, nothing. The Free plan covers one website, three published tours or widgets, every pattern from tours to checklists, and video export in 1080p, with a small “Made with Stepsome” badge. There is no account to create and no card to enter.

When the app starts to earn, Pro removes the badge and adds audiences, schedules, language rules, analytics per step and 4K export. See pricing.

One more thing: nothing leaves your machine

If your app handles anything sensitive, this matters. Stepsome has no servers. The tours stay in your browser while you build them, and your users load one static file from your own domain. No third-party script on your pages and no vendor that sees your users.Onboarding without third-party scripts goes into the trade-offs.