The first 60 seconds that shape everything
Swiggy is one of India's two dominant food delivery platforms — a duopoly with Zomato where the battle is fought less on inventory (both have the same restaurants) and more on experience. The first 60 seconds — from app open to first restaurant listing — is where that battle is won or lost.
This audit covers two related but distinct experiences: the first-run onboarding flow (from install to home screen) and the home screen information architecture. These are inseparable — what you ask during onboarding determines how relevant the home screen feels. Swiggy's problem is that they've invested heavily in the home screen's surface area while underinvesting in the data that would make it genuinely useful.
I audited the Android app (v4.x) across 3 devices in November 2024. Two first-run sessions (fresh installs) and multiple returning-user sessions across different times of day and locations.
Disclaimer: Independent audit. No affiliation with Swiggy. All observations based on publicly available app behaviour.
10 heuristics. One honest score.
Each heuristic scored 1–10. Scores below 5 indicate significant usability issues. Swiggy scores notably lower than Zomato on H4 (Consistency) and H8 (Minimalist Design) — both directly traceable to home screen information architecture decisions.
Location detection feedback is slow with no visible progress indicator. Users are left staring at a blank screen for 3–5 seconds with no explanation.
Food category labels are mostly clear, but 'Swiggy Genie' and 'Swiggy Instamart' introduce brand names where functional descriptions ('Courier' and 'Groceries') would reduce cognitive load.
Skipping onboarding is possible but not obvious. Users who skip cannot set dietary preferences later without navigating to a buried settings screen.
Three distinct card styles on the home screen with no consistent logic for which restaurants get which treatment. Visual hierarchy communicates priority that has no user-relevant meaning.
No dietary preference capture during onboarding means vegetarian users are shown non-veg restaurants until they manually filter. The most common customisation need is not addressed at the most appropriate moment.
Past orders are accessible but require 2 taps from home. Frequently ordered restaurants have no persistent shortcut. Users must remember and search rather than recognise and tap.
No power-user shortcuts. Repeat orders require the same 4-tap flow regardless of how frequently you order. Expert users get no acceleration over first-time users.
The home screen contains: search bar, location selector, promotional carousel (5 cards), category row (12 icons), "What's on your mind" row (8 food type chips), a second promotional banner, restaurant listings, and a floating nav. That is 8 competing attention zones above the fold.
Location errors are handled reasonably well. Other error states (restaurant unavailable, item out of stock) have clear messages.
In-app support is accessible. Swiggy's chat support is notably better than competitors. Loses points for no onboarding guidance after signup.
Nine points where Swiggy loses users
Ranked by conversion impact. Onboarding friction is listed first because it determines every subsequent home screen interaction — a broken first impression compounds throughout the session.
F1 — Onboarding skips dietary preferences entirely CRITICAL
India has one of the world's highest rates of vegetarianism — approximately 30% of the population. Swiggy's onboarding asks for your name and phone number. It does not ask whether you're vegetarian, Jain, or have any dietary restrictions. The result: a home screen showing meat dishes to users who will never order them, requiring manual filter application on every single session. This is the single highest-impact missing feature in the entire flow — one question at onboarding would make every subsequent session more relevant.
F2 — Home screen has 8 competing attention zones above the fold CRITICAL
Counting every distinct visual element above the restaurant listings: (1) location selector + search bar, (2) promotional carousel (auto-scrolling, 5 cards), (3) service category icons row (Swiggy Food / Instamart / Genie / Dineout), (4) "What's on your mind" food type chips, (5) a second static promotional banner, (6) "Top picks for you" section header, (7) restaurant card row. That's 7 distinct UI zones before a user sees the restaurant listings they actually opened the app for. Each zone competes for attention. None of them yields — they all shout simultaneously.
F3 — Auto-scrolling carousel interrupts reading CRITICAL
The promotional carousel at the top of the home screen auto-scrolls every 3 seconds. When a user is trying to read a restaurant name or delivery time below the carousel, the automatic movement triggers peripheral motion detection — involuntarily pulling attention upward. This is a well-documented accessibility violation (WCAG 2.1 criterion 2.2.2) and a usability anti-pattern. Auto-scrolling content that the user did not initiate interrupts every cognitive task on the screen.
F4 — Location detection blank screen: no feedback for 3–5 seconds CRITICAL
On first run and on location change, the app displays a blank or near-blank screen while detecting location. No spinner, no message, no progress indicator. Users don't know if the app is working, crashed, or waiting for them to do something. This violates H1 (Visibility of System Status) completely — and at the worst possible moment: the very first impression. Competitive benchmark: Zomato shows a pulsing location pin animation during the same process. Same wait time, radically better perception.
F5 — "Swiggy Genie" and "Instamart" require brand literacy MODERATE
The service switcher row uses brand names (Swiggy Genie, Instamart) instead of functional descriptors (Send a Package, Groceries). New users have no way to know what these services do without tapping them — adding an unnecessary discovery step. Returning users eventually learn, but the cognitive cost is real on every first-run session. A simple sub-label ("Genie · Send anything") would eliminate this entirely.
F6 — Inconsistent restaurant card styles with no clear logic MODERATE
Three distinct restaurant card treatments appear on the home screen: large hero cards, standard grid cards, and compact list cards. The visual treatment communicates hierarchy — users assume larger cards are better restaurants or better matches for them. In reality, card size is determined by promotional placement, not relevance. This creates false information — the interface implies a ranking that doesn't exist — and erodes trust when users notice promoted content that doesn't match their preferences.
F7 — No persistent "Reorder" shortcut for frequent orders MODERATE
The most efficient path for a user who orders the same thing every Tuesday is still 4+ taps: home → search or scroll → restaurant → menu → add items → cart. There is no "order again" shortcut on the home screen for frequently ordered items. This is the power-user efficiency gap — Swiggy's most valuable customers (high-frequency repeat orderers) get no UX reward for their loyalty.
F8 — Filter preferences reset between sessions MODERATE
If a vegetarian user applies the "Pure Veg" filter, it applies for that session only. On the next session, it resets — requiring reapplication. For a user who will never deviate from this filter, it is friction on every single session. Persistent filter preferences (stored to user profile, not just session) would eliminate this friction permanently for the 30%+ of users with consistent dietary requirements.
F9 — Past orders require 2 taps from home LOW
Order history — a primary navigation destination for repeat users — requires Profile → Orders. There's no home screen shortcut. On a platform where repeat ordering is the highest-frequency behaviour, the reorder path should be a first-class navigation element, not a Profile submenu. A dedicated "Reorder" tab in the bottom nav would serve repeat customers significantly better.
The cognitive principles being violated
Swiggy's home screen problems aren't primarily visual — they're cognitive. The information architecture creates mental load that exhausts users before they've made a single choice.
Paradox of Choice — too many zones, no clear start
Barry Schwartz's paradox: more options reduce satisfaction and increase paralysis. Swiggy's home screen presents 8 distinct zones before any food choice — each demanding a decision about whether to engage with it. The user's cognitive goal is "find something to eat" — but the interface demands they first navigate a promotional carousel, assess a service selector, engage with food type chips, and read two promotional banners before they reach restaurant listings. Decision fatigue sets in before the actual decision.
Attentional capture — auto-scroll exploits involuntary attention
The visual system is hardwired to detect motion — it's a survival mechanism. Auto-scrolling content hijacks this reflex, pulling attention to the carousel regardless of the user's intent. This is not a UX dark pattern in the traditional sense — it doesn't deceive — but it is an attention tax paid on every home screen visit. Multiply by daily sessions across millions of users and the aggregate cognitive cost is enormous.
False hierarchy — visual weight implies relevance that doesn't exist
Users are trained — by every well-designed interface — to interpret visual size as importance or relevance. Large card = most relevant. Swiggy's card sizes are determined by paid promotion, not relevance. This creates a silent trust violation: users who select a large-card restaurant and have a poor experience begin to mistrust the interface's implied hierarchy. Over time this erodes confidence in Swiggy's recommendations entirely — a long-term retention risk masquerading as a UI inconsistency.
Peak-End Rule — the blank location screen sets the wrong peak
The very first experience of Swiggy — the moment of highest anticipation — is a blank screen with no feedback. This 3–5 second silence is the first "peak" moment of the onboarding experience. Per Kahneman's Peak-End Rule, this negative peak anchors the user's overall memory of onboarding disproportionately. A product that signals "something is happening" during this wait changes what new users remember about their first session.
Six fixes. Sequenced by impact.
All six fixes below are implementable without redesigning the home screen from scratch. They are surgical improvements that remove friction at specific points — ordered by impact-to-effort ratio.
Add dietary preference to onboarding (1 question)
Impact: Very High. Effort: Low. A single screen after phone verification: "Do you have any dietary preferences?" with options for Pure Veg, Jain, No Preference. Store to user profile. Apply as a persistent default filter on the home screen. This single addition makes every subsequent session more relevant for 30%+ of users. Implementation: 1 sprint for the screen, filter persistence logic, and profile storage. The ROI — in reduced filter friction across millions of daily sessions — is immediate.
Stop the auto-scrolling carousel
Impact: High. Effort: Trivial. Make the promotional carousel manual-only. Users swipe when they want to see the next card. The carousel doesn't scroll without user input. This is a one-line CSS/config change that eliminates attentional hijacking on every home screen visit. The business concern — that promotions get less visibility — is addressable: a dot indicator shows users there are more cards, inviting exploration without forcing it.
Add location detection loading state
Impact: High. Effort: Low. Show a pulsing pin animation and "Finding restaurants near you" text during the 3–5 second location detection wait. This is purely a perception change — the wait time is identical, but the experience of waiting is transformed. Users who see visible progress assume the app is working; users who see a blank screen assume it has crashed. One animation changes the first impression of every new install.
Reduce home screen zones from 8 to 4
Impact: High. Effort: Medium. Ruthless prioritisation: keep the search bar, the service selector (with functional labels), the restaurant listings. Remove or collapse the second promotional banner (merge with carousel), remove the food-type chips (replace with a persistent filter bar above listings). The result is a home screen where the user's first viewport is dominated by actual restaurant choices — the thing they opened the app for.
Persist dietary filters across sessions
Impact: Medium. Effort: Low. If a user applies "Pure Veg" filter, store it to their profile and apply it by default on subsequent sessions. Show a persistent "Filtered: Pure Veg ✕" chip at the top of listings so the filter is visible and dismissible. This eliminates per-session reapplication for users with consistent dietary preferences — a meaningful quality-of-life improvement for a large user segment.
Add "Order Again" shortcut for top 3 repeat orders
Impact: Medium. Effort: Medium. Below the service selector, show a "Your Usuals" row with the 3 most frequently ordered items — restaurant name, item name, last price — with a one-tap reorder button. Users who order the same thing regularly get a dramatically faster path. This feature rewards high-frequency users and increases repeat order velocity — both directly valuable to Swiggy's unit economics.
What fixing this is worth
Swiggy's most acute UX problem is not any single friction point — it's the compounding effect of friction on every session. Each of the 9 friction points identified costs a small amount of conversion, attention, or trust. Together, they create a first-run experience significantly worse than it needs to be, and a returning-user experience that never gets faster or more relevant.
The most important structural observation about Swiggy's UX problems: they are almost entirely self-inflicted. Zomato and Swiggy have essentially identical restaurant inventory in most Indian cities. The product differentiation battle is fought entirely on experience. Swiggy's home screen currently cedes ground on the first impression (blank location screen), the first engagement (8-zone cognitive overload), and the first personalisation moment (no dietary preference capture). All three are fixable without touching the core product.
Swiggy has demonstrably better in-app support than Zomato, and the underlying checkout experience is solid. The gap is entirely in the first 60 seconds and the home screen architecture. Fix those, and Swiggy's retention story changes substantially.
This is an independent audit conducted without access to Swiggy's analytics, user research, or internal data. All impact estimates are directional, based on published industry benchmarks. The intent is constructive — the same analysis a senior UX leader would present in an internal product review.
