Design rationale

• Both users see the same search bar in the same position first — the split between "explore visually" and "already have data" happens below it, not by forking into two different home screens entirely, so the app feels consistent the moment a first-time user becomes a returning one.
• The first-time CTA grid and the returning-user pills/data occupy the exact same real estate — once a user has something saved, that space simply switches from "here's how to start" to "here's what you have," rather than the whole layout being redesigned.
• "My Plots" is a placeholder title for Rohit's data panel; "My Land" or "Saved & Recent" are open alternatives.

Design rationale

• Search stays the single, unambiguous entry point on both home states — everything else (pills, doc entries) is a shortcut around it, never a competing first action.
• 2c (map not available) exists because DP data doesn't cover every urban pocket; rather than a dead end, the banner reframes "no map" as "type it instead," keeping the task completable without a support call.
• The back icon and doc-search shortcut were added identically across every screen in this flow so a reviewer can jump straight back to the home screen from any depth without hunting for a distinct nav pattern per screen.

Design rationale

• Each zoom level reveals exactly one new layer of information (district label → village names + plot counts → individual plot outlines) so the map never looks dense or requires the user to parse overlapping labels at any single zoom.
• Boundaries and counts appear before individual plots do — this primes the user's sense of scale ("49 plots in this taluka") before asking them to pick one.
Note: This section still needs exact data to be refined properly

Design rationale

• A quick tap opens the essentials (name, area, owner) as a small floating card — enough to confirm "is this the right plot?" without committing to a full-screen view.
• Asking for more expands into a bottom sheet rather than navigating away, so the map stays visible underneath and the user's sense of location is never lost.
• Save and share sit at the very top of the expanded sheet, ahead of the ownership history and documents — these are the two actions a broker takes most often and shouldn't require scrolling to reach.
Note: This section still needs exact data to be refined properly

New

Design rationale

• The onboarding tooltip is spotlighted (rest of the screen dimmed) rather than a plain banner — this is a one-time, high-value shortcut that's easy to miss among the map's visual noise, so it briefly demands full attention instead of competing with it.
• Picking a document type before showing the form keeps each form short and specific (5 fields max) rather than one long generic form with irrelevant fields for whichever document the user didn't mean.
• Fields the user is likely to already know (District, Taluka) are pre-filled from their last search context; only the fields that actually vary by document (Survey/Gat No., Owner name) are left for input.

Design rationale

• The activity layer is opt-in, not on by default — most searches are about a specific plot, and showing mutation/sale counts everywhere by default would visually compete with the primary plot data the majority of users came for.
• The choropleth uses a single-hue (monochromatic) scale rather than a multi-hue traffic-light scale: it's colorblind-safe, reads correctly in black-and-white printouts, and still communicates "more/less activity" through lightness alone without implying good/bad the way red/green would.
• Selecting an activity type (Mutations, Sales, …) as chips rather than a dropdown keeps the broker's mental model simple — one visible row of options, no extra tap to open a menu just to see what's available.