Article6 min readUpdated
Design for first time internet users: a practical guide
How to design for first time internet users: simple screens, clear icons, voice and local language, and care for elderly people using a new smartphone.
Imagine a vegetable seller in a small town in Bardhaman district who has just bought her first smartphone. Her son set up WhatsApp. Now a customer asks her to pay by UPI. She opens an app, sees a row of small icons, a text she does not understand, and a button that says "Authenticate". She closes the app. The app was not broken. It was designed for someone who had used apps before.
Design for first time internet users means building apps and websites for people who are new to smartphones, so that every step can be understood without prior experience. These users are not slow. They are simply meeting every pattern for the first time.
This article is about the choices that help most: simple structure, icons with words, voice, local language and patience. It builds on my notes in designing apps for Indian users and regional language app design.
Who is a first time internet user, and what is different about them?
A first time internet user is a person who has just started using a smartphone or the internet, often with help from family. They do not know common patterns, such as swipe, long press or hamburger menu, and may read slowly or prefer a regional language.
Important differences to design for:
- No habit memory. Experienced users guess what an icon does. Beginners do not.
- Fear of mistakes. They worry about losing money or deleting something. They tap less and ask others more.
- Reading effort. Long text in English is a barrier. A regional language helps, though some people still read slowly.
- Shared devices. A phone may be used by a whole family, with different needs.
- Small budgets. A cheap phone and limited data mean slow screens and a careful use of storage.
Do not assume age. A young shop worker and a retired teacher may both be beginners. Do not assume simple means childish either. Respect is part of the design. Write as you would speak to a respected neighbour.
How do you keep an app simple enough for a beginner?
Give each screen one main job, one main button, and few choices. Remove everything that does not help the next step. If a beginner must read a paragraph to proceed, the screen is too complex.
Concrete rules I follow:
- One task per screen. "Enter your phone number" is one screen. "Enter the OTP" is the next screen.
- One main button. Make it large and the same colour on every screen.
- A visible way back. A clear back button on every screen, with the word "Back" or its local word.
- Short forms. Ask only what you need now. Collect the rest later. See form design best practices.
- Visible steps. Show "Step 2 of 4" so the person knows how much remains.
- No hidden actions. Do not place important actions behind swipes, long presses or a three-dot menu.
- Confirm before big actions. Show a clear summary before payment and say what happens next.
For the first screens a new person sees, see my notes on app onboarding UX and mobile app navigation patterns. A bottom bar with three to five labelled items is easier than a hidden side menu.
Should you use icons, text or voice?
Use icons together with a short word, never alone, and offer voice or audio help for key steps. An icon with a label is understood by more people than either one alone.
Icons mean different things to different people. A heart, a bell, a funnel or a share symbol may mean nothing to a beginner. A rupee note, a phone, a house or a camera is usually clearer, because they match objects in daily life.
How to handle each:
- Icons. Use familiar objects. Draw them with a simple, bold outline. Avoid abstract symbols. For ideas on drawing a consistent set, see custom icons vs icon libraries.
- Text. Use the word people use in daily life. Say "Send money", not "Initiate transfer". For tone and wording, see UX writing and microcopy for apps.
- Voice. A speaker button that reads the instruction aloud in the user's language helps people who read slowly. Voice input helps people who find typing hard. Check that voice works in the languages you support, and test with real accents.
- Pictures and short clips. A 10 second animation of "tap here, then here" can replace a paragraph.
Voice has limits. It needs quiet surroundings and data. Always keep the written text too, and never make audio the only way to learn a step.
What should a language and text setup look like?
Ask for language on the first screen, show each language in its own script, and write in simple words. Keep sentences short, avoid technical terms, and test the text on someone who is not part of your team.
A few practical points:
- Offer the local language first when you know the user's region. For West Bengal, that may be Bengali, with English as a choice.
- Write numbers and money in the form people see on bills and UPI apps.
- Replace words like "authenticate", "credentials" and "session expired" with "Confirm it is you", "Your login details" and "Please log in again".
- Use plain error messages that say what to do: "The number has 10 digits. Please check and try again."
- Allow large text. Many users have weak eyesight, and cheap phones have small screens.
See my posts on Bengali typography and on Hindi app design for script details.
How do you design for elderly users and digital literacy?
Design for elderly users with large text, strong contrast, big buttons and few steps. Digital literacy means the ability to use digital tools with confidence, and it grows with safe practice, so build screens that make practice safe.
Key points:
- Large touch targets. Buttons should be big, with space between them, so a shaky tap lands correctly.
- Strong contrast. Dark text on a light background. Avoid light grey text.
- Undo and recovery. Let people cancel and go back. Fear of a mistake stops many beginners.
- Patience. Do not time out quickly, especially for OTP and payment steps.
- Trusted helpers. Many beginners learn through a child or neighbour. Add a "Share with family" or "Call us" option so a helper can step in.
- Fraud awareness. Say clearly that the company will never ask for a PIN. Short warnings protect people.
My guide on accessibility in app and web design covers contrast and text size in more detail. For slow phones and weak signals, see designing for low-end phones and slow networks.
On a seller app I designed for a marketplace in Tanzania, the same lesson applied: sellers who were new to apps needed a very short onboarding, clear labels and a verification step that told them exactly what was needed. Small texts decided whether a person finished or quit.
How do you test with real beginners?
Test with five or six real beginners, give each one a task, and watch without helping. What they do tells you more than what they say, because beginners often blame themselves and say "it is fine".
A simple routine:
- Find people who match your users, such as a shop owner, a retired person or a first phone owner.
- Give a task: "Send Rs 100 to this number" or "Book an appointment".
- Stay silent for the first minute. Note where they hesitate.
- Ask after the task: "What did you expect to happen when you tapped that?"
- Fix the top three problems and test again.
Be kind and clear that you are testing the app, not the person. Run these tests in their language and on their phone. My guide to usability testing on a small budget explains how to do this with little money. If your product serves people who are new online, I can help plan and design it through my mobile app design service.
Frequently asked questions
What is the most important rule when designing for beginners?
+
Give each screen one job and one main button. Beginners cope well with a clear single step, and they struggle when many choices appear at once.
Should I use only icons to save space?
+
No. Icons alone confuse beginners, so always add a short word beside each icon. Use familiar objects instead of abstract symbols.
Does voice help first time smartphone users?
+
Yes, when it works well in their language and accent. Voice instructions and voice input help people who read or type slowly, but keep written text as well.
How do I design for elderly users?
+
Use large text, strong contrast, big buttons and few steps. Allow undo, avoid short timeouts and show clear messages after every action.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.