November 17, 2026 · Use case
How do you test the first session of an app or a product?
How to see what people understand, miss, and need in the first session, before you ship.
- Use this when what people understand, miss, and need in the first session.
- Show the work the way people would actually meet it.
- A simulated audience can give you a first read while the work can still change.
- Confirm a high-stakes decision with a live study when you need official evidence.
Neon Blue builds simulations of human behavior. A first-session test is a close look at the opening minutes: what people think the product is, what they try, and where they reach for help.
It overlaps with onboarding, but it also covers the first real task, not only the welcome screens.
When to use it
Use this when the first session of an app or a product is still changeable, and you need to see what people try, miss, and need before you ship.
It is less useful when the audience is still undefined, or when the decision already needs a representative live sample as the official result.
Questions and configuration
Start with who should answer, what they will see, and what you need to decide. If any of those is fuzzy, fix that first.
- After a few minutes, what can this product do?
- What did you try first?
- What did you look for and not find?
- Where did you want help?
- Would you come back, and why or why not?
How Neon Blue fits the workflow
Neon Blue sits before you lock the work. You put the stimulus in front of a simulated audience, read what they do and why, and change the work while it is still cheap.
If the decision has to stand as official evidence, follow with a live study. Keep the simulated read labeled as simulated.
Limits and validation
A simulated read is for design, rehearsal, and a fast first pass. It is not a representative live sample, and it should not be presented as one.
The main risk is false precision. Use the result to choose or rewrite, then validate anything that has to be official.
Starter template
Target group: First-time users of the app or product.
Research decision: what people understand, miss, and need in the first session.
Core stimulus: The first-session screens or a working draft of the opening experience.
Main task: a clear read, with reasons, that can still change the work.
Validation note: follow with a live study when the decision needs official evidence.
Next step
Bring the work as people would see it, and a plain description of the audience. Book a demo and we will set up a first study.
Frequently asked questions
When is this the right study?
Use this when the first session of an app or a product is still changeable, and you need to see what people try, miss, and need before you ship.
If you need a representative live sample as the official result, use this as a first pass, then field the live work.
Can a simulated audience replace the final study?
No. It is best used to draft, rehearse, and get a first read.
When the decision needs official live evidence, you still run that study.
What do we need to start?
The audience in the language you already use, the work people would actually see, and the decision you need to make.
How does Neon Blue run this?
We put your work in front of a simulated audience and return a read you can use to change it.