TapGuide / Blog / 2 November 2026
How to create training guides for a mobile app (one task per guide)

The training guides that work for frontline staff are small. Make one guide per task, named the way staff would say it ("Clock in at the start of a shift"), with numbered steps, one action per step and a screenshot of the screen at that moment. Capture them on the same phone or scanner staff use, keep each one short enough to follow in a couple of minutes, and put them where people can open them during a shift. Skip the full manual that tours every feature of the app. Nobody reads it at the till.
Here's how to build a set of guides like that, step by step, on Android.
Why one task per guide?
Frontline staff learn an app in the middle of real work, often with a customer waiting. They don't need to know everything the app can do. They need the next thing they're about to do.
A guide per task gives them that:
- It's quick to find. The title matches the job in front of them, so they open the right page at once.
- It's quick to follow. Five to ten steps, not forty.
- It's quick to fix. When one screen changes, you redo one guide, not a whole manual.
- It fits the role. A cashier, a shift lead and a stock clerk each get only the guides they need.
If a task branches ("if the customer has no receipt, do this instead"), make the branch its own guide and link to it from the step where it splits.
Step 1: List the tasks, not the features
Start with what people do in the app on a normal shift, not with the app's menu. Ask a team lead or watch a shift and write down every task, in the words staff use:
- Clock in and out
- Swap a shift
- Receive a delivery
- Process a return
- Report a broken item
Then sort the list. Put the daily tasks first, then the ones that cause the most questions, then the rare ones that are easy to get wrong. A new starter needs the first group in week one. The rest can wait.
Step 2: Capture the task on the device staff use
Do the task once, the right way, on the same kind of phone your team uses, and take a screenshot before each tap.
On most Android phones, including Samsung Galaxy phones:
- Open the screen you want to capture.
- Press Power and Volume down at the same time.
- If that doesn't work, Google's Android help says to press and hold Power for a few seconds, then tap Screenshot.
Use a test account or training data if the app has one, so real customer names and orders don't end up in the guide. Some apps block screenshots and screen recording; Samsung's help page notes that not all screens or apps allow them. If yours does, check with the app's vendor or your IT team before you plan the guides around screenshots.
Step 3: Write one action per step
Each step tells the reader to do one thing, using the words they will see on the screen.
- Start with a verb. "Tap Returns." "Scan the receipt." "Enter the reason."
- Use the button's real label, in bold. "The icon at the bottom right" stops being true after the next update.
- Split any step with "and". "Scan the item and tap Refund" is two steps.
- Say what they should see when it matters. "A green tick appears" tells them it worked.
- Put warnings before the step. "Check the amount first: refunds can't be undone."
Keep the language plain. Many frontline teams include people who are new to the job, new to the country or new to smartphones. Short sentences and the on-screen labels help all of them.
Step 4: Mark up and blur the screenshots
A full phone screen has a lot on it. Make the button for each step obvious: draw a box or circle around it and nothing else. Crop out what adds nothing, but keep enough of the screen that people can tell where they are.
Blur anything private before the image goes anywhere: customer details, staff names, phone numbers, notifications. Training guides get printed, forwarded and pinned in group chats.
You can do basic markup in your phone's photo app: in Google Photos, open the screenshot and tap Edit. The tools differ between phone makers and Android versions, so check what yours offers. For a full structure around the steps (purpose, owner, last updated), see how to write an SOP with screenshots.
Screenshots or a screen recording?
A short video can help with a task that depends on timing or a gesture, like a long press or a swipe. Android has a built-in recorder:
- Stock Android (Pixel): swipe down twice from the top of the screen and tap Screen record. Before you tap Start, you can choose to show touches on the screen.
- Samsung Galaxy: open Quick settings and tap Screen recorder. Touch and hold that icon to open its settings, where Show taps and touches puts a dot wherever you touch the screen.
Menu names and where the tile sits vary between phone makers and Android versions. If you can't find the tile, edit your Quick settings panel to add it.
For most tasks, though, numbered steps with screenshots are the better training guide. Staff can follow them at their own pace, find step 6 without scrubbing through a video, print them, and you can update one step without recording everything again. A video works well as an extra, next to the written guide.
The faster way: record the steps instead
Taking, cropping and captioning screenshots for twenty guides is a lot of work, and it's why training material often falls behind the app.
TapGuide is an Android app that does the capture and the first draft for you. Press Record, do the task once, and press Stop. Each tap becomes a step with its own screenshot, and the step text is written from the button's label, such as "Tap Returns". Then you edit the wording, reorder or delete steps, highlight the button and blur private data.
Export the guide as PDF to print or share in the team chat, or as Markdown or HTML for your wiki or help center. It runs on Android 8.0 and later, with no account and no internet permission, so screenshots of internal apps stay on the phone until you share them. It records on Android only, but staff can read the exported guide on any device. More on this use in SOPs and work instructions, made on the phone.
Get the guides to staff where they work
A guide nobody can find doesn't train anyone. Put it where people already look:
- On the phone. Pin the PDFs or a link in the team chat or the app staff already use for messages.
- On the wall. Print the guides for tasks done at a fixed spot, like the receiving bay or the back office, and pin them next to the device.
- In onboarding. Give new starters the week-one guides on day one, and have them follow each guide once while someone watches.
- In one place. Keep a single current copy and link to it, instead of sending files that turn into old versions.
Test with a new starter, then keep it current
Before you share a guide, give it to someone who has never done the task. Ask them to follow it alone while you watch. Every pause or question is a step to fix.
After that, guides go out of date when the app does. Give each guide an owner and a "last updated" date. When the app updates or a process changes, redo the guides it touches, all the screenshots at once, so old and new screens never mix.
For the general method behind step-by-step guides on a phone, see how to make a step-by-step guide on Android.
Make your next guide in one take
Press Record, do the task once, and TapGuide turns every tap into a step with a screenshot. Free on Android 8.0 and later. No account, no internet access.
Get it on Google Play