Mobile Shop is a multi-page website for a mobile phone shop. It exists so that everyday shoppers can browse mobile phones, view the details and price of a single phone, compare models and prices, and place an order for the phone they choose — and so that the shop owner can keep the phone catalog and its prices current.
The product intent is calm, honest and easy to trust: a shop that sells objects people hold every day, presented with quiet order rather than hype. The audience is everyday shoppers comparing models and prices, plus the shop owner who maintains what the shop shows.
The site-wide theme is Deep Indigo (#4F46E5) and Dark Slate (#0F172A), applied on every page. Section layouts are revised across all pages, and every button and metric card carries a smooth hover elevation effect. The site header is redesigned on every page, and a new, more creative logo — a custom-drawn mark rather than a plain wordmark — appears in both the header and the footer of every page.
This document is the System Requirements Document for the project named Mobile Shop, requested by Hussain Bekhushi.
Mobile Shop is delivered as a first-party, application-owned multi-page website with a shared backend and application-owned persistent data. The website must have multiple pages; each page below is a separately navigable destination. Every page shares one redesigned site header and one shared footer, and both carry the same new creative logo mark.
Public, anonymous access. Landing, Phones, Phone Details, Sign Up and Login are reachable without an existing account. Landing explains the shop before any protected work. Phones and Phone Details let a shopper browse the catalog with prices and compare one phone and its price. Sign Up is where a new shopper establishes an account; Login is where a returning shopper or the shop owner verifies identity.
Protected access. Checkout is restricted to a signed-in shopper, because an order is a durable commitment that must remain bound to the correct shopper. Catalog Management is restricted to the shop owner's provisioned role, because it changes the shared catalog that every shopper sees. A protected destination cannot establish access to itself: a shopper who reaches Checkout without an account is directed to Sign Up, and a returning shopper or the shop owner is directed to Login; after identity is established they continue to the protected work they intended.
Current and future boundary. Everything described in this document is current. No future-horizon capabilities are accepted; nothing outside the accepted catalog, comparison, ordering, identity and catalog-maintenance behavior is in scope.
#4F46E5) and Dark Slate (#0F172A) theme.#4F46E5) and Dark Slate (#0F172A) theme.#4F46E5) and Dark Slate (#0F172A) theme.#4F46E5) and Dark Slate (#0F172A) theme.#4F46E5) and Dark Slate (#0F172A) theme.#4F46E5) and Dark Slate (#0F172A) theme.#4F46E5) and Dark Slate (#0F172A) theme.#0F172A) with a 1px bottom rule in #334155, wide desktop margins matching the 12-column grid, and a single row that holds the new logo mark and wordmark at the left and the identity links at the right. The header is not a floating pill, not a glass panel and not a heavy bordered box; it reads as a quiet shelf above the page.#4F46E5) price-tag notch at its lower-right corner — the shop's "phone plus price" idea reduced to two soft shapes. The mark is drawn as inline SVG so it stays crisp at every size, uses only the theme tokens (#4F46E5 mark accent, #F8FAFC mark body, #334155 hairline), and is paired with the "Mobile Shop" wordmark set in Zen Kaku Gothic New, Medium weight, wide tracking, sentence case, in #F8FAFC.font-size: clamp(...)) to fit; nothing covers them.prefers-reduced-motion, the hover state is shown without animated elevation.FR-1 — Multi-page website. As a visitor, I should move between the shop's separate pages (Landing, Phones, Phone Details, Checkout, Sign Up, Catalog Management, Login) so that each job has its own place. Provenance: explicit. Lifecycle: trigger — visitor selects a navigation link; result — the requested page loads; failure — a page that cannot load shows a plain message and the header navigation remains usable; continuation — the visitor moves on from the header. Acceptance: the site has multiple distinct pages and every page is reachable through navigation.
FR-2 — Browse the phone catalog with prices. As a Shopper, I should browse the shop's phone catalog with prices on Phones so that I can see what is available. Provenance: explicit. Lifecycle: trigger — the shopper opens Phones or selects "See the phones" on Landing; input — none; result — the catalog of phones with prices is shown as product cards; failure — a plain message with a retry action if the catalog cannot be loaded; continuation — the shopper selects a phone. Acceptance: every listed phone shows its name and price.
FR-3 — View phone details. As a Shopper, I should open one phone's details and price on Phone Details so that I can judge it before a purchase. Provenance: explicit. Lifecycle: trigger — the shopper selects a phone on Phones; result — that phone's details and price are shown; failure — a plain message with a link back to Phones; continuation — the shopper proceeds to Checkout or returns to compare another model. Acceptance: the selected phone's name, price and details are shown.
FR-4 — Compare phones and prices. As a Shopper, I should compare phones and their prices across Phones and Phone Details so that I can choose the model that fits. Provenance: explicit. Lifecycle: trigger — the shopper moves between the catalog and individual phone details; result — prices and details are presented in consistent label-and-value rows so models can be compared; failure — if a phone's details cannot load, the shopper returns to Phones and selects another; continuation — the shopper settles on a phone and proceeds to Checkout. Acceptance: prices are visible on the catalog and on each phone's details, in a consistent presentation.
FR-5 — Place an order for a phone. As a Shopper, I should place an order for the selected phone on Checkout so that I can buy it. Provenance: explicit. Lifecycle: trigger — the shopper selects the order action on Phone Details while signed in; input — the selected phone and its price; result — an order is recorded and a confirmation shows the ordered phone and price; failure — a plain message that the order could not be placed, with a retry action and the selection preserved; continuation — the shopper sees the confirmation. Acceptance: a signed-in shopper can complete an order for a selected phone and receives an observable confirmation.
FR-6 — Self-service enrollment before a protected order. As a new Shopper, I should create an account on Sign Up before placing an order so that my order remains bound to me. Provenance: required_inference. Lifecycle: trigger — the shopper reaches Checkout without an account, or chooses Sign Up; input — enrollment details; result — the account is established and the shopper continues to Checkout; failure — a plain message identifying what needs correction with entered values preserved; continuation — resubmit, or switch to Login. Acceptance: a new shopper can establish an account and then reach Checkout.
FR-7 — Verification at Login. As a returning Shopper or the Shop owner, I should verify my identity on Login so that I can reach protected work. Provenance: required_inference. Lifecycle: trigger — the visitor opens Login or is directed there from a protected destination; input — verification details; result — identity verified and the visitor continues to the intended protected destination; failure — a plain message that verification failed with entered values preserved; continuation — retry, or use Sign Up. Acceptance: a verified shopper reaches Checkout and a verified shop owner reaches Catalog Management.
FR-8 — Provisioned shop owner role for Catalog Management. As the Shop owner, I should hold a provisioned role that grants Catalog Management so that only I change the shared catalog. Provenance: required_inference. Lifecycle: trigger — the shop owner verifies at Login; result — Catalog Management is available to the owner and not to shoppers; failure — a visitor without the role is not granted Catalog Management; continuation — the owner proceeds to maintain the catalog. Acceptance: Catalog Management is reachable only by the shop owner's provisioned role.
FR-9 — Maintain the phone catalog and prices. As the Shop owner, I should add, update and remove phones with their prices and details on Catalog Management so that shoppers see current models and prices. Provenance: required_inference. Lifecycle: trigger — the owner selects add, edit or remove; input — phone name, price and details; result — the change is saved and reflected on Phones and Phone Details; failure — a plain message that the change could not be saved with entered values preserved; continuation — retry the save, or continue with another entry. Acceptance: a saved change is visible to shoppers on the catalog.
FR-10 — Site-wide Deep Indigo and Dark Slate theme. As a visitor, I should see the same Deep Indigo (#4F46E5) and Dark Slate (#0F172A) theme on every page so that the shop reads as one coherent place. Provenance: explicit. Lifecycle: trigger — any accepted page loads; result — the page renders with the Deep Indigo and Dark Slate theme applied to its ground, surfaces, text, actions and price accents; failure — if a themed asset fails, the page still renders readable text and usable controls in the theme's base colours; continuation — the visitor moves on through the header. Acceptance: Landing, Phones, Phone Details, Checkout, Sign Up, Catalog Management and Login all use the Deep Indigo and Dark Slate theme.
FR-11 — Revised section layout on every page. As a visitor, I should see the revised section layout on every page so that each section reads in a clear, calm order. Provenance: explicit. Lifecycle: trigger — any accepted page loads; result — each section is composed in the revised layout (one calm column on mobile; the desktop grid with wide margins on larger viewports), with label-and-value rows kept consistent; failure — if the layout cannot be applied, content still renders in a readable single column; continuation — the visitor continues within the section. Acceptance: every accepted page presents its sections in the revised layout, and no readable text or control is cropped or covered at 375px, 768px or 1280px.
FR-12 — Smooth hover elevation on buttons and metric cards. As a visitor, I should see buttons and metric cards lift smoothly on hover so that interactive surfaces feel responsive. Provenance: explicit. Lifecycle: trigger — the pointer hovers a button or a metric card; result — the element elevates smoothly (soft shadow plus a small upward translate with a smooth ease) and returns to rest on leave; failure — if motion is unavailable, the element keeps a clear hover state without elevation; continuation — the visitor activates the control. Acceptance: every button and every metric card on every accepted page shows a smooth hover elevation, and the effect never covers or crops readable text or controls; with prefers-reduced-motion, the hover state is shown without animated elevation.
FR-13 — Redesigned shared header on every page. As a visitor, I should see the redesigned header at the top of every page so that the shop reads as one coherent place and I can always reach identity links. Provenance: explicit. Lifecycle: trigger — any accepted page loads; result — the shared header renders as a calm full-width bar on the Dark Slate ground with a 1px bottom rule, the logo mark and wordmark at the left and the identity links at the right; failure — if the wordmark font fails to load, the fallback stack renders the wordmark at the same size and colour and the header links stay usable; continuation — the visitor uses the header to move to Landing, Login or Sign Up. Acceptance: Landing, Phones, Phone Details, Checkout, Sign Up, Catalog Management and Login all render the same redesigned header, and the logo mark, wordmark and every link stay entirely inside the viewport and their container at 375px, 768px and 1280px.
FR-14 — Creative logo mark in the header and footer on every page. As a visitor, I should see a more creative logo than a plain wordmark, in both the header and the footer of every page, so that the shop is recognizable and feels considered. Provenance: explicit. Lifecycle: trigger — any accepted page loads; result — the custom-drawn logo mark (a rounded phone silhouette with a single thin screen rule and a small Deep Indigo price-tag notch) is rendered as inline SVG beside the "Mobile Shop" wordmark in the header and again in the shared footer, using only the theme tokens; failure — if the mark cannot render, the wordmark still shows in #F8FAFC and the header and footer links stay usable; continuation — the visitor selects the logo to return to Landing. Acceptance: the same logo mark appears in the header and the footer of all seven accepted pages, is drawn from the shop's own phone-and-price subject rather than a plain wordmark, and never covers or crops readable text or controls.
The creative direction is authoritative: Super normal calm for a phone and accessory shop, muse Naoto Fukasawa, headline idea "Phones and accessories, simply made clear." The user's latest refinement sets the site-wide theme to Deep Indigo (#4F46E5) and Dark Slate (#0F172A) on every page, revises the section layout, adds smooth hover elevation to all buttons and metric cards, redesigns the site header, and replaces the plain wordmark with a more creative logo mark used in both the header and the footer of every page.
Colour tokens (Deep Indigo and Dark Slate theme, applied on every page):
| Role | Hex |
|---|---|
| Background (Dark Slate ground) | #0F172A |
| Surface (product cards, panels) | #1E293B |
| Surface border (thin 1px rules) | #334155 |
| Text (primary) | #F8FAFC |
| Muted (labels, secondary text) | #94A3B8 |
| Primary (Deep Indigo, actions) | #4F46E5 |
| Accent (Deep Indigo, price and focus only) | #4F46E5 |
| Metric value | #38BDF8 |
| Status — active/safe | #16A34A |
| Status — warning | #FACC15 |
| Status — critical | #EF4444 |
Typography: Headings — Zen Kaku Gothic New, Medium weight, wide tracking, large sizes, sentence case, soft and plain. Body — Karla. Modular scale 1.25: display 44/64/96, section 28/32/36, body 18, label 14. Mobile display starts at 40px.
Shape language: Soft rounded blocks with 20px to 28px radii. Thin 1px rules in #334155. No sharp corners, no heavy borders.
Layout (revised on every page): One calm column on mobile; a 12-column grid on desktop with wide margins. Each section is re-composed in the revised layout: the section opener (small caps label above a thin full-width rule) leads, the primary content block follows, and supporting blocks sit beside it on desktop and stack beneath it on mobile. Product rows use clear label and value pairs.
Hover elevation: every button and every metric card lifts smoothly on hover — a soft shadow plus a small upward translate with a smooth ease — and returns to rest on leave. The lift never covers or crops readable text or controls, and with prefers-reduced-motion the hover state is shown without animated elevation.
Header and logo: the shared header is a calm, low, full-width bar on the Dark Slate ground (#0F172A) with a 1px bottom rule in #334155 and wide desktop margins matching the 12-column grid — not a floating pill, not a glass panel, not a heavy bordered box. The logo is a custom-drawn inline-SVG mark: a rounded phone silhouette whose screen is cut by a single thin horizontal rule, with a small Deep Indigo (#4F46E5) price-tag notch at its lower-right corner, drawn in #F8FAFC with a #334155 hairline and paired with the "Mobile Shop" wordmark in Zen Kaku Gothic New, Medium weight, wide tracking, sentence case, in #F8FAFC. The same mark and wordmark appear in the shared footer on every page. The mark is one reusable component, never a per-page variant.
Imagery: Softly lit still lifes of phones and accessories on plain Dark Slate grounds; close detail shots showing material and edges.
Accessibility of text and controls: Headlines, wordmarks, labels, numbers, cards' text and controls stay entirely inside the viewport and their container at 375px, 768px and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit. No element covers any part of them. Imagery and decoration may bleed, crop or overlap as the direction asks, but never over readable text or controls.
Avoid: Gradient blobs and glass panels; neon or saturated colour fields; bouncy or playful motion; identical hover-lift card grids. The generic indigo/blue-on-white SaaS template is forbidden; Deep Indigo is used here only as the user-requested action and accent colour on the Dark Slate ground, never as a light-mode template.
The public entry (Landing) is a wide Dark Slate field (#0F172A) holding one large, softly lit phone still life at the right that bleeds off the right edge of the hero. A 64px to 96px headline in #F8FAFC sits flush left on two lines — "Phones and accessories, simply made clear" — with the subline beneath it in Karla in #94A3B8. A Deep Indigo button (#4F46E5) reading "See the phones" sits under the headline and lifts smoothly on hover. A thin 1px rule in #334155 and a small Deep Indigo price label (#4F46E5) balance the left column. Above the hero, the redesigned header sits as a quiet shelf: the custom logo mark — a rounded phone silhouette with a single thin screen rule and a small Deep Indigo price-tag notch — beside the "Mobile Shop" wordmark at the left, identity links at the right, and a 1px bottom rule in #334155. The same mark closes the page in the shared footer. Section openers below use a thin full-width rule with a small caps label above, and each section is composed in the revised layout. The gesture of the still life bleeding off the edge is carried entirely by imagery; all readable text, the logo mark, the wordmark and the button remain whole at every viewport.
Interaction Model: Static (direction) Motion Tempo: still Hero Dimensionality: flat
Landing Hero Motion Brief
#0F172A), oversized left-aligned headline on two lines in #F8FAFC, subline in #94A3B8, Deep Indigo button (#4F46E5), thin rule in #334155 and Deep Indigo price label on the left; still life at the right.prefers-reduced-motion, the hero and product cards appear immediately in their final arrangement with no fade, and hover elevation is shown as a static hover state without animated lift; all text and controls remain whole and readable.prefers-reduced-motion, a usable static arrangement is provided; content that fades in appears immediately, and hover elevation is shown as a static hover state without animated lift.#4F46E5) and Dark Slate (#0F172A) theme for its ground, surfaces, text, actions and price accents.frontend, backend, database.#4F46E5) and Dark Slate (#0F172A) on all pages.
Mobile shop
Compare models and prices, then order the phone that fits your hand.
Every model shows its price beside its name.
Phones · Accessories
Phones & accessories

Mobile shop
Compare models and prices, then order the phone that fits your hand.
Every model shows its price beside its name.
Phones · Accessories
Phones & accessories
No comments yet. Be the first!