Dog Walking App is a route-planning tool for people who walk dogs. It records the home locations where dogs live, builds a walking route that visits those locations, and shows the information needed to judge and improve that route — the distance between stops and a more efficient ordering of the same stops.
The product serves two participants. A Dog owner supplies the home address where their dog lives. A Dog walker plans the walk that reaches those homes, reads the leg distances, and chooses a more efficient route. Both participants must have an account before dog locations or routes are saved, and a returning participant must verify identity before opening saved dog locations or routes.
The audience is small-scale, practical, and route-first: someone who needs clear distance data and a fast route, not a social or booking platform. The interface follows a functional-clarity direction (Dieter Rams): ordered data, honest controls, one signal colour, and no decoration that competes with the route.
The application is a first-party web product with application-owned identity. The public entry is the Landing page, which explains the product and offers the primary action "Plan a route". From there a new participant establishes identity on Sign Up; a returning participant verifies identity on Login. Both identity surfaces are reachable without being signed in, and neither is protected by the state it creates.
Once identity is established, the participant works inside three protected destinations:
All route computation, distance calculation, and route ordering run in the shared backend; the browser only presents state and collects input. Saved dog locations and saved routes are durable, application-owned data held in the provisioned MariaDB database and bound to the account that created them.
Nothing beyond this is in scope. There is no booking, scheduling, payment, messaging, dog profile management, live tracking, or social feed. Route optimisation is limited to producing a more efficient ordering of the stops the walker has selected; it is not a general-purpose navigation or turn-by-turn service.
Not applicable — no reference directive declares content_source.
FR-1 — Route to where dogs live (explicit) As a Dog walker, I should get a route that reaches the home locations where dogs live, so that the walk visits every dog I have selected.
FR-2 — Make a route to those dog locations (explicit) As a Dog walker, I should have the app build the walking route to the selected dog locations, so that I do not have to work out the order myself.
FR-3 — Show distance between stops (explicit) As a Dog walker, I should see the distance between each pair of consecutive stops, so that I can judge the effort of each leg.
FR-4 — More efficient route (explicit) As a Dog walker, I should get a more efficient route over the same selected stops, so that the walk is shorter.
FR-5 — Save dog locations (explicit, via accepted identity requirement) As a Dog owner, I should save the home address where my dog lives, so that the walker can route to it.
FR-6 — Review saved dog locations (explicit, via accepted identity requirement) As a Dog walker or Dog owner, I should see the saved homes where dogs live, so that I know which stops are available.
FR-7 — Save a route (explicit, via accepted identity requirement) As a Dog walker, I should save a route, so that I can return to it later.
FR-8 — Create an account before saving (required_inference) As a new Dog walker or Dog owner, I should make an account before I save dog locations or routes, so that my saved data belongs to me.
FR-9 — Verify identity before opening saved data (required_inference) As a returning Dog walker or Dog owner, I should verify my identity before I open saved dog locations or routes, so that only I see my saved data.
The visual system follows the supplied creative direction: functional clarity after Dieter Rams — ordered data, honest controls, one signal colour.
Colour tokens (light mode)
| Role | Hex | Use |
|---|---|---|
| Background | #EFEDE6 | Warm grey ground, ~70% of the page |
| Surface | #F7F6F1 | Map panel, form surfaces, data rows |
| Text | #1C1B18 | Headlines, values, body copy |
| Primary | #2F5D3A | Route lines, primary controls |
| Accent | #E4571B | Active stop and key numbers only; the primary CTA |
| Muted | #7A766C | Small-caps labels, secondary rules, supporting text |
Exactly one accent colour is used. No gradients, no glass panels, no second accent.
Typography
clamp() with the mobile size as the floor so text stays whole at 375px, 768px, and 1280px.Shape and layout
Imagery
The public entry is a composed, flat, full-width warm grey ground (#EFEDE6) divided by the 12-column hairline grid.
#E4571B) sits directly under the headline, with "Log in" and "Create an account" as quiet text links beside it.#F7F6F1: a deep green route line (#2F5D3A) threading circular numbered stop markers, with the active stop filled in orange and aligned label-and-value distance rows beneath, separated by hairline rules.The concept recomposes only accepted content — the product name, the hero copy, the primary action, and the route-with-distances illustration — and introduces no new behaviour.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
clamp(); no element covers readable text or controls.prefers-reduced-motion, the route line and all data render statically and every control remains usable.#E4571B) is used, reserved for the active stop, key numbers, and the primary button.docker-compose.yml with the three provisioned services: frontend, backend, and database. The frontend depends on the backend gateway; the backend depends on the database.
Save the homes where dogs live and get the shortest walk between them.
Active stop 2: Bramble, Wren Court

Save the homes where dogs live and get the shortest walk between them.
Active stop 2: Bramble, Wren Court
No comments yet. Be the first!