Deploy the version people will actually use
Replit supports different ways to publish depending on the project. Before inviting users, confirm the deployment type fits the app, the public URL is stable enough to share, and the live version matches what you tested.
Replit launch checks
- Open the deployed URL while logged out of Replit.
- Confirm environment variables are configured in the deployment, not only the workspace.
- Test cold starts, loading states, and any server actions.
- Check whether the app needs a static, autoscale, reserved, or native/mobile path.
- Run the core flow from a phone if mobile users are expected.
If the app is mobile or Expo-based
A Replit mobile project may need a different public testing path than a simple web app. Make sure participants know whether they should open a web URL, use a mobile preview, join a TestFlight-style flow, or install from a store listing.
The participant should never have to guess where the actual product experience starts.Use JustMadeIt for the proof loop
- 01Add the deployed destination
Use the Replit public URL or approved app destination as the product access point.
- 02Define the meaningful task
Tell participants what product action matters for the first proof objective.
- 03Send people through JustMadeIt
The session starts in JustMadeIt, moves to the product, and returns for evidence.
- 04Upgrade verification when ready
A server-side integration can later report approved product events automatically.
What to show participants
If your Replit app has multiple possible destinations, do not make participants choose blindly. Send them to the exact deployed URL, mobile test path, or app listing that matches the experience you want them to complete.
Then ask for evidence tied to that specific flow. A participant saying the deployment loaded is useful, but it is different from completing the meaningful product task.