address-list-map is a compact, responsive address book that pairs a scannable saved-address list with a single live map. Every saved address appears as one line of type containing exactly three facts — Name, Mobile Number, and Full Address — and every saved address also appears as a marker on one map displayed beside the list. Selecting an address row highlights the corresponding marker and centers the map on that location, so the list and the map always agree about which place is in focus.
The product intent is a working instrument, not a marketing surface: a person checking a name, a number, and a full address at a glance, then finding that same person on a map. The audience is anyone who keeps a list of places — couriers, small-business owners, families, operations staff — working on desktop and on a phone, who need the layout to stay clean, compact, and easy to scan in both contexts.
The current delivery is a first-party custom UI with two pages: an anonymous Landing page that presents the address list and map experience as a full-viewport instrument, and the Address List working view that contains the saved address list, the adjacent map, all address markers, and the selection synchronization between them. Both pages are reachable without an account; no sign-in, registration, or permission model is part of the accepted scope.
The single active human actor is the Address List User, who reads the list, selects an address, and observes the map respond. The map tile provider is a non-persona external actor that supplies the base map imagery; the application owns the list, the marker set, the selection state, and the camera behavior.
Accepted behavior in scope: a responsive address list where each address is one line of Name, Mobile Number, and Full Address; all saved addresses rendered as markers on one map beside the list; click-to-select that highlights the matching marker and centers the map on that location; and a layout that stays clean, compact, and scannable on desktop and mobile.
Narrow exclusions: no address creation, editing, or deletion workflow is accepted; no search, filter, sort, or grouping of addresses is accepted; no routing, directions, or turn-by-turn navigation is accepted; no multi-map, split-map, or per-address map view is accepted; no accounts, roles, or permission controls are accepted; no marketing hero, illustration, or stock photography is accepted.
The product is delivered entirely as first-party application pages. The Landing page is an anonymous entry surface that shows the instrument itself — a ruled header, a populated address list plate, and a map plate with the first address pre-selected — so a visitor immediately understands what the tool does before entering the working view. The Address List page is the working view where the list scrolls against a stationary map on desktop and against a pinned map plate on mobile.
Access is anonymous on both pages. The accepted requirements describe viewing and selecting saved addresses; they do not describe a private, resumable, or per-person state that must be bound to an identified owner, so no identity establishment, verification, or account management is introduced. The map base imagery is owned by an external map tile provider; the application owns the list, the markers, the selection state, and the camera movement.
Everything described in this document is current. No future-horizon capability has been accepted, and nothing in the current pages depends on one.
ADDRESSES in Archivo 700 uppercase at 13px with +0.14em tracking on the left, a live count in tabular figures (for example 24 SAVED) on the right, and a 3px orange segment under the rule. Below the header, an asymmetric two-plate composition fills the remaining height: the left plate is the address list already populated and scannable, the right plate is the map with all markers and the first address pre-selected in orange. The largest type on the page is the 64px desktop / 40px mobile display line set flush-left in the left plate's header — Every place you keep. — in graphite Archivo 700 with tight leading, sitting directly above the tabular column labels.NAME / MOBILE / ADDRESS and one-line rows; right map plate with indexed circular markers and one active orange marker; entry control into the working view.#D8D3C8 border and shows a muted inline notice that the map is unavailable, while the list plate remains fully readable and selectable.Add address control right.Add address control, orange underline segment that slides to sit above the active list column); tabular list header with NAME / MOBILE / ADDRESS labels; one-line address rows with a 3px orange left rule and faint warm tint when selected; the 28px detail strip on the selected row; the sticky map plate with 1px border, 6px radius, and one soft low shadow; indexed circular markers with graphite rings and the active marker in solid orange with a white ring.FR-1 — Responsive address list UI (explicit) As an Address List User, I should see a clean, responsive address list UI so that I can read my saved addresses comfortably on desktop and on mobile.
FR-2 — One-line address rows with Name, Mobile Number, and Full Address (explicit) As an Address List User, I should see each address displayed in a single line containing the Name, the Mobile Number, and the Full Address so that I can scan the list quickly.
FR-3 — All saved addresses as markers on one map beside the list (explicit) As an Address List User, I should see all saved addresses as markers on one map displayed beside the address list so that I can see where my saved places are.
FR-4 — Clicking an address highlights the corresponding marker (explicit) As an Address List User, I should have the corresponding location marker highlighted when I click an address so that I can see exactly which marker belongs to the row I chose.
#D9540E with a white ring and scales from 1.0 to 1.15, settling in 140ms; the previously active marker returns to its graphite-ringed puck state.FR-5 — Clicking an address centers the map on that location (explicit) As an Address List User, I should have the map centered on that location when I click an address so that the selected place is brought into view.
FR-6 — Clean, compact, scannable layout on desktop and mobile (explicit) As an Address List User, I should get a layout that stays clean, compact, and easy to scan on both desktop and mobile so that the list and map remain usable at any size.
#D8D3C8 rules separate every row and panel edge, and no card shadows or decorative elevation appear except the single soft low shadow under the map plate.FR-7 — Row detail strip for the selected address (required_inference) As an Address List User, I should see the full untruncated address and its copy and route controls on the selected row's detail strip so that truncation in the one-line row never hides the address I need.
FR-8 — Hover preview of a row's marker (required_inference) As an Address List User, I should see a hover preview of a row's marker so that I can confirm which marker a row belongs to before committing to a selection.
FR-9 — Live saved-address count in the header (required_inference) As an Address List User, I should see a live count of saved addresses in the header so that I know how many places the list and map are showing.
24 SAVED) and updates whenever the collection changes.FR-10 — Add address control in the header (required_inference)
As an Address List User, I should see an Add address control in the header so that the list can grow beyond the addresses already saved.
Add address control in the ruled header.Product context. The Address List User keeps a list of saved places — delivery destinations, customer sites, family addresses — and needs to check a name, a mobile number, and a full address at a glance, then find that same person on a map. They work on desktop at a desk and on a phone in the field, often in a hurry, and they treat the tool as an instrument rather than a destination to browse.
Primary goal. Read the saved address list quickly and confirm where a specific saved place is on the map.
Distinct accepted responsibilities.
Relevant inputs and decisions. Which row to select; whether the truncated address in the row is enough or the detail strip is needed; whether to copy the address or open a route; whether to move on to another address.
Interactions with other accepted participants. The Address List User is the only active human actor. Their work depends on the external map tile provider, which supplies the base map imagery the markers sit on; the application owns the list, the markers, the selection state, and the camera movement, so the user never negotiates with the provider directly.
Observable success. The selected row carries the orange left rule and warm tint, its detail strip is expanded, its marker is solid orange with a white ring at 1.15 scale, and the map has panned and zoomed so that location is centered — with the list and map never disagreeing about which address is active, on either desktop or mobile.
ADDRESSES in Archivo 700 uppercase at 13px with +0.14em tracking on the left, the live count in tabular figures on the right, and the 3px orange segment under the rule.Every place you keep. flush-left above the NAME / MOBILE / ADDRESS column labels.NAME / MOBILE / ADDRESS.#D9540E with a white ring and scales from 1.0 to 1.15, settling in 140ms; the previously active marker returns to its graphite-ringed puck state.The muse is Dieter Rams, and the headline is "Less, but better — one signal orange on honest grey." The direction is authoritative for this section.
Colour tokens (light mode).
| Role | Hex | Use |
|---|---|---|
| Background (page ground) | #EDEAE3 | Warm grey page ground so panels read as physical plates |
| Surface | #F7F5F0 | Warm off-white working surface for the list and map plates |
| Text | #1C1B18 | Near-black graphite for all type and the primary control fill |
| Primary | #2A2925 | Primary control fill |
| Accent | #D9540E | Braun signal orange — the only saturated colour |
| Muted | #8C877C | Labels, rules, and secondary metadata; never body copy |
| Hairline rule | #D8D3C8 | 1px rules separating every row and panel edge |
| Water | #C9C4B8 | Desaturated water on the map tiles |
Accent rationing is strict: the selected row's left rule and index chip, the active map marker, focus rings, and the one primary action. No blue, indigo, or violet appears anywhere in the palette.
Contrast. #1C1B18 on #F7F5F0 ≈ 15:1. White text on #D9540E ≈ 4.6:1, used only at ≥16px semibold. #8C877C is used only for 11–12px uppercase labels on #F7F5F0 (≈ 4.6:1).
Typography. Headings use Archivo at 600/700 with tight tracking (−0.02em), uppercase for section labels and the wordmark, sentence case for the display headline. Headline
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!