Tithi Mondal

Article5 min readUpdated

App Home Screen Design: What to Show First and Why

App home screen design explained: what to show first, the order of blocks, example wording, every state and the mistakes that bury your main action.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

App Home Screen Design: What to Show First and Why: cover illustration

Suppose a tiffin service in Durgapur builds an app. The owner wants the home screen to show offers, the weekly menu, a referral card, a blog link and the order button. A customer opens the app at 12:30 hungry, scrolls past three banners, and orders on WhatsApp instead. App home screen design is the work of deciding what goes first so that does not happen. The home screen is the first screen a user sees after login, and it should answer the question "what can I do here right now?"

What should an app home screen show first?

It should show the action or content that most users come for, above everything else. Ask one question: what did the user open the app to do today?

  • A food app: search and "Reorder your last meal".
  • A learning app: "Continue your lesson".
  • A loan app: current loan status and "Pay EMI".
  • A marketplace: search, then categories.

This is the idea of what to show first. Write down the top three tasks from real user behaviour or your team's best knowledge. The first task gets the top of the screen. The second and third follow. Everything else goes lower or into a menu. If you do not know the tasks yet, read user research for startups.

What is the order of blocks, from top to bottom?

A good home screen has a clear order, so users learn where things are. Keep the same order every day, because users build a habit of where to tap, and a layout that moves each week breaks that habit. Here is a common order for a consumer app.

  1. Top bar. Logo or greeting on the left, one or two icons on the right, such as notifications. Example: "Good afternoon, Riya".
  2. Search or main action. A wide field with a hint like "Search for dishes or restaurants".
  3. Quick actions. A row of 4 to 5 icons with short labels, such as "Orders", "Offers", "Wallet".
  4. Primary content. The thing people come for. For returning users it is personal: "Continue where you left off".
  5. Discovery. Categories, popular items, or recommended courses.
  6. One promotion block. A single banner, with a clear end date.
  7. Bottom navigation. Four or five tabs.

Keep the top block short. On a small phone the first screen is about the top 600 pixels of content. Whatever sits there is the whole app for many users.

How do you make a personalised home screen?

A personalised home screen uses what the app knows about the person to change what appears, and it must stay honest about what it knows. Start with simple facts, not clever guesses.

  • Last action. "Reorder: 2 paneer rolls" for a returning customer.
  • Progress. "Lesson 4 of 12, 8 minutes left."
  • Location. "Delivering to Salt Lake" with a tap to change.
  • Status. "Your order is on the way, arriving in 15 minutes."

For a new user with no history, do not show a block called "Recommended for you" with random items. Show "Popular near you" instead. That label is true. Fake personalisation makes users stop trusting the app. Also let users correct the app. A small "Not interested" option on a recommended item, or "Change location" on the delivery line, shows that the user stays in control of what the app learns about them.

A dashboard for a consumer app works best when it is small. A loan app might show one card: "Next EMI: ₹2,450 due 5 December", with a "Pay now" button. Nothing else needs to compete with that card. For admin tools with many numbers, see admin dashboard UI/UX design.

What are the states of a home screen?

A home screen has at least five states, and designers often draw only the full one. Every state needs a design.

StateWhat to showExample wording
First visit, no dataDefault content and one clear step"Welcome, Riya. Add your first meal plan."
LoadingGrey placeholder shapes in the layout of the real blocksNo text needed
Partly loadedShow blocks that arrived, retry the others"Could not load offers. Try again"
OfflineLast saved content with a thin banner"You are offline. Showing saved items."
ErrorPlain message and a retry button"Something went wrong. Try again."
FullPersonal blocks first"Continue your lesson"

Use placeholder shapes instead of a spinning wheel for loading, because they show the shape of the page and feel faster. On a slow network, the page should show something within a second or two. See designing for low-end phones and slow networks and empty, loading and error screens.

Which home screen mistakes should you avoid?

Most bad home screens come from internal politics: every team wants its feature at the top. The fix is to rank by what users do, not by who asks loudest.

  • Too many banners. Two or three carousels push real content off the screen. Keep one promotion block.
  • Auto-rotating carousels. Users cannot read at the speed they move. Let people swipe.
  • Every feature as an icon. Twelve icons in a grid means no priority. Show five and add "See all".
  • Hiding the main action in a menu. If most users do one task, show it on the screen.
  • Layout that jumps while loading. Reserve space for images so the screen does not shift.
  • No language choice. Mixed Hindi, Bengali and English labels with no logic confuse users. See regional language app design in India.
  • Ignoring small screens. Test on a phone with a 5.5 inch screen, not only on your own device.

How do you decide what is on top?

The decision should come from use, not opinion.

Make a simple list of every block your team wants. Next to each, write how often a typical user needs it: daily, weekly or rarely. Daily goes first. Weekly goes below. Rarely goes in a menu or a profile screen. I do this exercise with clients before I open Figma, and it usually removes a third of the blocks.

On a food ordering app I designed, the home screen decisions started with exactly this list, before any visual work. For an industry example, see food delivery app UI/UX design.

If you are planning a home screen and want a second opinion, my UI/UX design service covers exactly this kind of decision.

Frequently asked questions

What is the difference between a home screen and a dashboard?

A home screen is the first screen of a consumer app and points to many tasks. A dashboard shows numbers and status for one job, and is more common in admin or business tools.

How many sections should a home screen have?

Four to six blocks is enough for most apps. Each block should earn its place by serving a task people do often.

Should the home screen be personalised from day one?

Only where you have real information about the person, such as their last order. For new users, show a sensible default rather than a fake recommendation.

Where should banners and offers go?

Below the main action, not above it. A banner that pushes the main action off the screen makes the app harder to use.

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.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.