Test the first 60 seconds of your app
· 7 min read
You know what your app does. You know which button to press first. You know why it asks for the camera. A stranger knows none of that. In the first minute they decide, often without saying so, whether to carry on. You cannot see this minute with your own eyes any more, because you have seen it too many times. This post is a short way to test it with fresh eyes before you launch.
Why the first minute matters
I won't quote a retention number at you, because I don't have a trustworthy one. Here is what I can point to. I read the Nielsen Norman Group's article on mobile app onboarding on 10 November 2026. Its main advice is to keep instruction small. Instructional onboarding should be "brief, optional, and should only highlight the minimum" that people need. The idea is simple: every screen you put between a new person and the first useful thing is a chance for them to leave.
The first minute has five parts: the first screen, sign-up, permission prompts, any tour, and the empty screen after all that. Test each one.
The first screen
The first screen has two jobs. It should say what the app does, and it should make the first step obvious. Both are easy to get wrong when you built the thing.
Try a five-second test. Take a screenshot of your first screen. Show it to someone for about five seconds, then hide it. Ask two questions: "What is this app for?" and "What would you do first?" If the answers are vague or wrong, the screen is not doing its job. Write down their exact words. They are better copy than anything you will write alone.
Look for these problems: a logo and nothing else, a slogan that sounds good but says nothing, a screen full of options with no clear first one, and words that only you use.
Sign-up friction
A sign-up screen is a toll gate. Some apps need one, such as a banking app. Many don't need it on the first screen. The Nielsen Norman Group article "Login Walls Stop Users in Their Tracks", which I read on 10 November 2026, says "Users are utterly vexed to have to enter information before they get a taste of what is in store for them." It advises letting people see real content first. It also suggests asking for an account after the task is done, when the person has already seen value.
Questions to ask about your own sign-up:
- Can someone see the value first? A sample, a demo or a read-only view is often enough.
- Is every field needed today? A name, a birthday and a phone number can wait for later.
- Are the sign-in choices clear? If you offer social sign-in and email, do the buttons say what will happen?
- What happens if the sign-in fails? Try a wrong password and a cancelled social login.
- Is there an email confirmation? Sign up with a fresh address and time how long the email takes. Check that the link brings you back to the right place in the app.
Permission prompts
Camera, location, notifications, contacts. Each is a question to a stranger who does not know you yet. Both big platforms say the same thing: ask at the right moment and explain why.
I read Apple's privacy guidelines on 10 November 2026. Apple says: "Ideally, wait to request permission until people actually use an app feature that requires access." It also says: "Avoid requesting permission at launch unless the data or resource is required for your app to function." On the wording of the system alert, Apple asks for "a brief, complete sentence that's straightforward, specific, and easy to understand."
I read Android's guide to requesting runtime permissions on the same day. Its first principle is: "Ask for a permission in context, when the user starts to interact with the feature that requires it." It also says: "Don't block the user." If someone says no, the guide says to "gracefully degrade" the app, so the person can keep using it without that feature.
To test this, install the app fresh and answer the prompts three ways:
- Allow everything. Does it feel natural, and did you know why it asked?
- Deny everything. Can you still use the app? Does it tell you which feature is off, and why?
- Ignore the explanation and tap quickly. Does the prompt still make sense?
One Android detail to know before you test: the same guide says that if a person taps Deny for a permission more than once, they "will no longer see the system permissions dialog" when the app asks again. A prompt shown too early can cost you that permission for good. To see the prompt again while testing, reinstall the app or clear its data.
A prompt for notifications on the very first screen, before the person has done anything, is the classic problem. Move it to the moment it helps.
Tours versus learning by doing
A swipeable tour feels like good manners. In practice most people tap through it without reading. The same Nielsen Norman Group article says "we don’t recommend deck-of-cards onboarding", and calls instructional overlays "often nice-to-have and not need-to-have". It does say a tour can make sense when you need information from the user to get started, for example when an account must be set up first.
The plain advice: put the person in front of the real thing as soon as you can, with one clear next step. If you keep a tour, make it short and make it skippable. Then watch whether a new person reads it or just taps past it.
Empty states
After sign-up, a new person often lands on a screen with no data in it. No projects, no messages, no history. This is the screen you will never see in your own testing, because your account is full.
I read the Nielsen Norman Group article on empty states on 10 November 2026. It says: "Do not default to totally empty states." It also says empty states should explain what the area will hold and how to fill it, and it advises you to "Provide direct pathways (i.e., links) to getting started with key tasks."
Make a brand new account and look at every screen. For each empty one, ask:
- Does it say what will appear here?
- Is there a button for the first step, such as "Add your first item"?
- Would sample content help someone see what the screen is like when it is full?
How to run the test with strangers
You need people who have never seen the app. Give each one a single task:
"Open the app and tell me in one sentence what it does, then do the first thing it asks."
Then ask for three things back:
- The one-sentence answer. This is your five-second test, done for real.
- The moment they hesitated. Ask them to think aloud as they go, or to write down the point where they paused, got confused or nearly quit.
- Their device. Phone model and OS version. A prompt or a layout can look different on another phone.
Keep the task small, because one task gives you one clear answer. For more on wording it, see how to write a test task. For why the device matters, see testing on phones you don't own. When the notes come back, sort them with turning beta feedback into a fix list. Anything that made two people hesitate at the same spot goes to the top.
Don't explain anything before they start. If you have to say "oh, you tap there", that is your finding.
The first-minute checklist
- Show the first screen for five seconds. Can they say what the app is for?
- Is the first step obvious on that screen?
- Can someone see value before creating an account? If not, is the account really needed now?
- Is every sign-up field needed today? Do the sign-in buttons say what they do?
- Does the confirmation email arrive quickly and return the person to the right place?
- Does every permission prompt come right when the feature needs it, with a clear reason?
- If you deny a permission, does the app still work?
- Is any tour short, skippable and really needed?
- Does every empty screen explain itself and offer a next step?
- Did at least three strangers do the task, and did you record their device and where they hesitated?
Where TestSwap fits
TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. You can post web, iOS and Android apps, and link to wherever testers can open or install it. That makes it a handy source of strangers for this exact test, because the people reviewing your app have not seen it before.
Put the one-sentence task in your test task. Each review needs a real first impression and a concrete suggestion, and a first impression is what you are after here. A review also has an optional private bug notes box that only you can see, so ask testers to put the moment they hesitated and their phone there.
Try it
Install your own app fresh, deny every permission, and look at every empty screen. Fix what you find. Then post your app on TestSwap with the one-sentence task, and review someone else's app first to see how it works. Tell me what's missing or broken (@dizid on X).