The 6 screens almost every small-business app really needs (and the ones you can skip)

A developer once sent a business owner I know a quote for her first app. Thirty-one screens. A splash screen, an animated intro, a "discover" feed, a blog, a rewards wallet, a referral tree, an in-app chat, a wishlist, a compare tool. She runs a home bakery. She sells about forty cakes a month on WhatsApp. She did not need thirty-one screens. She needed six.

I've built apps for 15 years, and the single most expensive mistake I see small businesses make isn't choosing the wrong developer or the wrong tool. It's building screens nobody uses. Every extra screen costs money to design, money to build, money to test, and — the part people forget — attention. A customer who has to hunt through your app is a customer who leaves. And roughly one in four people abandon an app after using it just once (Business of Apps). You do not have room to waste their first minute on screens that don't earn their place.

So here's the honest map I give every owner before we build anything: the six screens almost every small-business app actually needs, what each one is really for, and the "invisible" screens that matter even though you don't design them as pages. Then a fully worked example — a real home-bakery app, screen by screen — so you can see how few pieces it really takes. No jargon. Just the shape of a good, small app.

Count screens by their job, not their looks

Before the list, one idea that will save you lakhs: name every screen by the job it does, not the industry you're in.

A boutique's "product page" and a salon's "service page" look different, but they do the exact same job — show one thing in detail so someone can decide. A cake shop's "checkout" and a physiotherapy clinic's "book appointment" screen also do the same job — take the commitment and the money. When you count by job, you discover that a shop, a clinic and a coaching centre all need roughly the same six screens. The words on them change; the structure doesn't.

This matters for your wallet. When a developer quotes "screens," they're really quoting jobs — design work, build work, testing. If you can describe your app as six jobs, you can sanity-check any quote and cut the padding. If your app truly needs a seventh job, you'll know exactly why. That clarity is worth more than any feature.

Here are the six jobs, in the order a customer meets them.

Screen 1 — Home: the front door with one obvious job

The Home screen is not your brochure. It's not the place to tell your founding story or show five banners. It's a front door, and a good front door does one thing: it points the visitor to the single most useful next action, fast.

For a shop, that action is "browse what's new" or "reorder your usual." For a clinic, it's "book an appointment." For a coach, it's "start today's lesson." Pick the one thing 80% of your customers open the app to do, and make it the biggest, most obvious thing on the screen.

Why so strict? Because you lose people in the first minute, not the first week. Industry data puts healthy Day-1 retention at only around 25% on Android and 28% on iOS (Amra & Elma, 2025) — meaning most people who install never really come back. A Home screen that makes someone think "what am I supposed to do here?" burns the tiny bit of goodwill you had. A Home screen that says, in effect, "here's the thing you came for, tap here," keeps them moving.

What belongs on a good small-business Home screen:

• One clear primary action (a big button or a prominent list of what's new).
• A short row of shortcuts to the two or three things people do most.
• Something that proves you're open and real — today's specials, current stock, next available slot.
• A visible way to get help (more on that in Screen 6).

What does not belong: an animated splash screen that wastes two seconds, a carousel of five promos nobody swipes, or a wall of text. Cut all of it. The Home screen's success is measured by how quickly people leave it — for the screen they actually wanted.

Screen 2 — Browse: the shelf where people look around

The Browse screen is your shelf. It's the list of what you sell or offer: products, menu items, services, class packs, doctors, stylists. This is where curiosity happens, so it needs to be scannable, not clever.

For most Indian small businesses, a simple, image-led list beats a fancy grid with a dozen filters. People shop on their phones, often on patchy data, often one-handed while doing something else. Big, clear photos, honest names, and the price right there. If you sell more than a handful of things, add categories (Cakes, Cookies, Hampers) rather than a search-everything box — categories help people who don't yet know what they want.

A few honest rules I've learned the hard way:

• Show the price on the list. Hiding it until the detail page feels clever and quietly frustrates people. Indian buyers price-check first; respect that.
• Photos sell, so budget for them. The cheapest upgrade to any catalogue app is better product photos, not more features. A ₹3,000 afternoon with a photographer often does more than ₹30,000 of extra code.
• Keep filters minimal at launch. One or two ways to narrow the list is plenty. Elaborate filter panels are the classic screen that gets built, gets demoed, and never gets used.
• Show what's sold out or unavailable rather than hiding it. "Back on Friday" builds more trust than a mysteriously missing item.

If you sell only three or four things, you may not even need a separate Browse screen — the list can live on Home. That's not a shortcut; that's good design. Fewer screens, remember, is the goal.

Screen 3 — Detail: the one-item screen that answers "should I?"

Tap an item on the shelf and you land on its Detail screen. This is the quiet salesperson. Its whole job is to answer the customer's real question — "is this right for me?" — and remove the last bit of doubt before they commit.

A good Detail screen for a small business has just a few things, done well:

• A great photo (or a few). This is the single biggest lever on whether someone buys.
• A plain, honest description. What it is, what's in it, the size, who it's for. No marketing fog.
• The price, clearly — including anything that changes it (a large size costs more, a home visit costs more).
• The one thing that removes doubt for your business. For a bakery, that's "serves 8–10" and "48 hours' notice." For a clinic, it's "45 minutes, first consultation." For a coach, it's "12 lessons, lifetime access."
• One clear action: Add to cart, Book this, or Enquire on WhatsApp.

Resist the urge to stuff this screen with reviews, related items, videos and social share buttons on version one. Every extra element competes with the button you actually want tapped. The Detail screen exists to move one person, one step closer to yes. Keep it pointed at that.

Screen 4 — Checkout or Booking: the screen that decides if you get paid

If you get only one screen right, make it this one. Everything before it is persuasion. This is where intent becomes money — or quietly evaporates.

The pattern of failure here is brutal and invisible: the customer wanted to buy, reached checkout, hit friction, and left. You never see the sale you nearly made. High-friction flows lose a huge share of people right at this step — studies put onboarding-and-checkout drop-off anywhere from a fifth to over two-thirds of users when the flow is clumsy (Business of Apps). So the design goal is ruthless: fewest possible taps, fewest possible typed fields, zero surprises.

For an Indian business in 2026, that means one thing above all: UPI first. UPI is how the country pays. In May 2026 alone, Indians made 23.2 billion UPI transactions worth ₹29.9 trillion, and UPI now handles the overwhelming majority of retail digital payments (NPCI via ANI, June 2026). There are over 839 million UPI users. If your checkout doesn't lead with UPI, it's fighting how your customers actually behave.

There's a money angle too that surprises owners: on standard UPI paid straight from a customer's bank account, you as the merchant pay no cut. The merchant discount rate on bank-funded person-to-merchant UPI has been zero since January 2020, and remains zero in 2026 (Razorpay, PIB). Cards and wallets are different — a gateway like Razorpay charges about 2% plus 18% GST, so roughly 2.36% per card transaction, with no setup fee (Razorpay pricing). That's fine and worth offering as a backup, but for most small businesses UPI keeps far more of every rupee.

Whether it's a checkout (shop) or a booking (service), the same rules make or break it:

• Let people pay or book as a guest. Do not force account creation before you take the money. Ask for what you truly need — a name, a phone number, a delivery address or slot — and nothing more.
• Lead with UPI, then offer cards/netbanking and, where it fits your business, cash on delivery or pay-at-store.
• Show the full amount before they commit. Delivery charge, packaging, advance amount — all visible before the pay button. A fee that appears at the last second is the fastest way to lose a nearly-done sale and a customer's trust.
• For services, show real availability. A booking screen that offers slots you can't honour is worse than no app. Connect it to how you actually run your day.
• Confirm clearly. After payment or booking, a plain "You're confirmed — here's what happens next" screen removes anxiety and cuts down the "did it go through?" WhatsApp messages.

This is the screen to over-invest in. Spend more care here than on your logo. It's the difference between an app that looks nice and an app that pays for itself.

Screen 5 — Orders and Account: the memory that brings people back

The first four screens win a sale. The fifth wins the second sale. The Orders and Account screen is your app's memory — it holds the customer's order history, their saved details, their bookings, and (if you offer it) their loyalty status.

For a business, this screen is what makes an app worth more than a WhatsApp chat. On WhatsApp, every reorder starts from zero. In a good app, a returning customer taps "reorder my usual" and they're at checkout in seconds. That convenience is the honest reason a customer keeps your icon on their phone instead of just messaging you.

Keep it simple. A small-business Account screen usually needs only:

• Your orders or bookings — past and upcoming, with status.
• A one-tap reorder or rebook.
• Saved details — address, phone, maybe a delivery preference.
• Log out, and a way to delete the account (both stores increasingly expect an in-app account-deletion option, so build it in).

This is also the natural — and correct — place for login. Which brings us to something important about screens you don't design.

Notice what's not here: no elaborate profile with avatars and bios, no settings maze. A corner-shop app is not a social network. The Account screen earns its keep by making the next purchase effortless, nothing more.

Screen 6 — Help and Contact: the human screen that builds trust

The last core screen is the one owners most often skip and most often regret skipping. People need to reach a human. When something goes wrong — a wrong order, a payment that looks stuck, a question before buying — an app with no visible way to get help feels like a trap. And a customer who feels trapped once won't come back.

For most Indian small businesses, the Help screen is refreshingly cheap to build, because the answer is already on everyone's phone: WhatsApp. A single, prominent "Chat with us on WhatsApp" button that opens a chat to your business number does more for trust than any in-app chat system you could pay to build. WhatsApp reaches over 535 million people in India (Statista, 2025) — your customers already live there.

A good Help screen holds:

• A WhatsApp / call button to reach you quickly.
• Your address and hours, and a map link if you have a physical location.
• A short FAQ — the five questions you answer every single day (delivery time, cancellation, sizes, payment, returns). Answering them here quietly saves you hours.
• Basic policies — returns, cancellation, and a link to your privacy policy (which both app stores require anyway).

Don't build an in-app chat or a ticketing system for version one. A WhatsApp button and an FAQ cover the real need at a fraction of the cost. This is the honest, boring screen that turns a first-time buyer into someone who trusts you.

The "invisible" screens: real, but not pages you design

Six customer-facing screens do the visible work. But three more screens exist that you don't design as glossy pages — and forgetting them causes real problems.

The login step. As I said, don't force it up front. Let people browse and even reach checkout as guests, then use a single OTP on the phone number they already use — no passwords to forget, no long form. Forcing a sign-up on the first screen is one of the surest ways to lose the quarter of users who quit after one session. Login is a moment, not a wall.

The notifications permission. Push notifications are powerful — a "your order's out for delivery" or "your usual is back in stock" message brings people back. But the permission to send them is a screen the phone shows, and if you ask for it rudely (the instant the app opens, with no context), most people say no, permanently. Ask only after you've delivered some value, and explain what they'll get. Notifications deserve their own careful playbook, which is a topic for another day — here, just know that how you ask is a design decision, not an afterthought.

The owner's dashboard. This is the big one people miss. Every screen above is for your customer. But someone has to see the orders, update the menu, mark a booking done, change a price. That's your admin — and it's effectively a second app, for you. Sometimes it's a simple web page you open on a laptop; sometimes it's a section of the same app that only you can log into. Either way, budget for it. An app that takes orders but gives you no easy way to manage them just moves your chaos from WhatsApp to a place you can't see. When you get a quote, ask explicitly: "How do I run this day to day?" If there's no clear answer, the quote is incomplete.

One template, many businesses: the six jobs mapped

Because we counted by job, the same six screens fit wildly different businesses. Here's how the labels change while the structure holds:

If you can fill in this table for your business, you've just scoped your app — honestly, and in about ten minutes. That's the whole point of thinking in six jobs.

A fully worked example: Anjali's home-bakery app

Let me make this real. The details are generic, but the shape is true to dozens of projects.

Anjali bakes from home in Ghaziabad. She sells around forty cakes and a steady stream of cookie boxes each month, almost all through WhatsApp. It's working, but it's chaos: orders buried in chat, "is this available?" at midnight, forgotten custom requests, and payment screenshots she has to chase. She wants an app — but she was quoted for thirty-one screens and ₹4 lakh, and it scared her off.

Here's the six-screen app she actually needed, screen by screen.

Home. Opens to a clean screen: a row of "Fresh today," a big "Order your usual" button for repeat customers, and a small "Custom cake? Chat with us" link. One glance tells a customer she's open and what's available. No splash animation, no story — the story lives on her Instagram, and the app links to it once, at the bottom.

Browse. Three categories — Cakes, Cookies, Hampers — each a simple image list with the name and starting price. Sold-out items show "Back Friday" instead of vanishing. Better photos, shot on a phone in daylight against a plain background, did more for sales than any feature. Cost of that upgrade: one afternoon.

Detail. Tap a cake and you see two clear photos, "Serves 8–10," "Egg / eggless," the price, and the one line that saves her a dozen chats a day: "Please order 48 hours in advance." One button: "Add to cart." Custom orders get a "Discuss on WhatsApp" button instead, because those genuinely need a conversation.

Checkout. The screen she and I spent the most time on. Guest checkout — no forced sign-up. Name, phone, delivery area, date and slot. Full amount shown up front, including a clearly-stated delivery charge for far-off pin codes. UPI leads; cards are a backup through a standard gateway. On UPI, she keeps the whole amount — no cut. A plain confirmation screen at the end: "Order confirmed. We'll message you on WhatsApp when it's out for delivery." That one line cut her "did my order go through?" messages to near zero.

Orders / Account. A returning customer logs in with a one-time password on her phone number and sees past orders with a "reorder" button. Anjali's regulars — the birthday-every-year, festival-every-season crowd — now reorder in three taps instead of re-explaining what they want. That single screen is why they keep the app.

Help. A big "Chat on WhatsApp" button, her hours, her delivery areas, and a five-line FAQ (notice period, eggless options, delivery charges, cancellation, custom orders). Most questions now answer themselves.

The invisible ones. Login is a quiet OTP, only when saving an order. Notifications she asks for after the first successful order, with a friendly "Want delivery updates?" — most people say yes because the timing is right. And the admin: a simple screen only she can log into, listing incoming orders with a "mark as done" toggle and a place to update prices and mark items sold out. That admin screen is what turned the app from a toy into a tool.

Six customer screens. Three invisible ones. That's the whole app. It cost a fraction of the thirty-one-screen quote, shipped in weeks not months, sailed through store review because it was small and honest, and — most importantly — her customers actually use it, because there's nothing in it that isn't for them.

If you're weighing what a build like this really costs and where money gets wasted, I've broken the numbers down in how much it really costs to build an app in India, and how to judge whoever builds it in our guide to choosing an app developer in Delhi-NCR. And if you're not yet sure an app is even the right move, start with the signs your business is (and isn't) ready for one.

The honest trade-offs

I won't pretend six screens is a magic number that fits everyone with no compromise. A few real tensions worth naming:

• Six is a floor for simple businesses, not a law. A marketplace connecting many sellers and buyers, or an app with genuinely complex logic (multi-city logistics, medical records, real inventory across branches), needs more. That's fine — the point isn't "never exceed six." It's "justify every screen past the six by the job it does," so you add the seventh on purpose, not by habit.
• Cutting screens means saying no to features you'll be tempted by. A competitor will have a loyalty wallet and a blog and in-app chat. Copying them feels safe. But every one of those is a screen that costs money now and attention forever. The disciplined move is to launch the six, watch what customers actually ask for, and add only what earns it.
• A small app can look "too simple" to an owner who paid for it. I've had clients quietly wish their app had more stuff, because more felt like more value. It isn't. The apps that get used are the ones that do one job cleanly. Resist the urge to add screens to feel like you got your money's worth — you got your money's worth when customers came back.
• The admin screen is easy to under-budget. Because it's not glamorous, it's the first thing a cheap quote trims. Don't let it. An app you can't easily run is worse than no app. Insist on knowing how you'll manage it day to day before you sign anything.

The bottom line

The next time someone hands you a quote with a wishlist of screens, don't count the screens — count the jobs. A shop, a clinic, a bakery, a coaching centre: almost all of them need the same six. A front door, a shelf, a one-item page, a place to pay or book, a memory that brings people back, and a human to reach when something goes wrong. Behind them, three invisible screens — a gentle login, a well-timed notification ask, and an admin you can actually use.

Build those, and nothing else, for version one. It'll be faster to make, cheaper to quote, easier to get live on the Play Store and App Store, and — the only test that matters — far more likely to get used. Then let your real customers, not a feature list, tell you what the seventh screen should be.

That's not a smaller app. It's a better one.

If you'd like help scoping your own app down to the screens that matter — and getting it built for what it should actually cost — that's exactly the kind of honest, no-padding work we do at Roy Digital. You can see what a store-ready build includes on our pricing page. Bring your six jobs. We'll help you skip the other twenty-five.