polar-habit

byJourney QA mobile full

Build Daylight, a simple personal habit tracker. Include a dashboard with daily progress, a habits page to add and complete habits, and a weekly insights page. Use a clean, friendly design with teal accents. Keep the first version focused on these three pages.

LandingSign UpLogin
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Daylight

1. Introduction

Daylight is a simple personal habit tracker for one daily user. The product helps a person record the habits they want to keep, mark them complete each day, see how much of today's plan is done, and review how the week went. The intent is calm encouragement rather than clinical measurement: the interface should feel clean, friendly, and warm, with teal accents marking progress and controls.

The audience is a single habit tracker user who wants a lightweight, private record of daily habits and a weekly view of their consistency. The first version is deliberately focused on three working pages — a Dashboard with daily progress, a Habits page to add and complete habits, and a Weekly Insights page — reached through a public Landing page and self-service Sign Up and Login.

Page 1 of 18

2. System Overview

Daylight is delivered as a first-party web application. A React frontend presents the public Landing page, the Sign Up and Login access surfaces, and the three working pages (Dashboard, Habits, Weekly Insights). A shared FastAPI backend owns the application APIs and domain logic for habits and daily completions, and a MariaDB database holds application-owned persistent data. Because habit records are private and must persist across visits, the application owns identity: a new user enrolls through Sign Up, and a returning user verifies identity through Login before reaching the Dashboard, Habits, or Weekly Insights pages.

The single active human actor is the Habit tracker user. The backend and database are supporting system actors, not personas. The current version covers exactly the six pages in the page contract: Landing, Sign Up, Login, Dashboard, Habits, and Weekly Insights. No other destinations, modules, or capabilities are in scope for this version.

Removed from scope

  • None. No concept from the authoritative requirement thread was removed or replaced.
Page 2 of 18

2a. Product Interpretation and Delivery Boundary

Daylight is a private, single-user habit tracker. All habit data belongs to the signed-in user and is only reachable after identity is established. The public Landing page explains the product and offers the entry action; Sign Up creates a new private habit record; Login verifies a returning user. The Dashboard, Habits, and Weekly Insights pages are protected and require login.

The first version is intentionally bounded to these six pages. There is no social, sharing, notification, reminder, goal-setting, or account-management surface beyond enrollment and login. Habit data persists in the application database so that daily progress and weekly insights remain available across sessions.

2c. Page Content and Component Coverage

Page 3 of 18

Landing

  • Information/state: Product name Daylight; hero headline "Small habits, steady daylight"; subline "Track your habits each day. See your progress and your weekly insights."; a large teal progress ring as the hero focal element; a short explanation of the three working pages (daily progress, adding and completing habits, weekly insights).
  • Primary action: "Start today" call to action leading to Sign Up.
  • Supporting action: A link to Login for returning users.
  • Domain entities: None persisted; presentational only.
  • Component responsibilities: Hero section (progress ring + stacked headline + CTA pill), section openers with a small terracotta dot and short label, still-life imagery in natural light.
  • States: Default static render; no loading, empty, or error states beyond standard page load. Reduced-motion users see the composed static arrangement.
Page 4 of 18

Sign Up

  • Information/state: Self-service enrollment form for a new user; explanation that habit records are private to the account.
  • Primary action: Submit enrollment to create the account and begin a private habit record.
  • Supporting action: Link to Login for users who already have an account.
  • Domain entities: User account (identity), which owns the user's habits and completions.
  • Component responsibilities: Enrollment form fields, submit control, inline validation messaging, link to Login.
  • States: Loading during submission; success redirects to the Dashboard; error shows inline validation or a submission failure message with recovery (retry or correct input); empty initial form.

Login

  • Information/state: Returning-user verification form.
  • Primary action: Submit credentials to verify identity and reach private habit records.
  • Supporting action: Link to Sign Up for new users.
  • Domain entities: User account (identity).
  • Component responsibilities: Credential fields, submit control, inline error messaging, link to Sign Up.
  • States: Loading during verification; success redirects to the Dashboard; error shows an invalid-credentials or failure message with recovery (retry); empty initial form.
Page 5 of 18

Dashboard

  • Information/state: Today's daily progress shown as one large progress ring (completed habits out of total habits for today); a habit list for today with each habit's completion state.
  • Primary action: View daily progress at a glance.
  • Supporting action: Navigate to Habits to add or complete habits; navigate to Weekly Insights.
  • Domain entities: Habit, daily completion record, today's progress summary.
  • Component responsibilities: Progress ring with slow 400ms fill easing; habit rows as soft oat cards with a thin warm rule and a round check button reflecting completion; navigation to the other working pages.
  • States: Loading while today's progress is fetched; empty state when the user has no habits yet, prompting navigation to Habits; success shows the ring and habit list; error shows a retry affordance.

Habits

  • Information/state: The user's list of habits; each habit row shows its name and today's completion state; an add form for new habits.
  • Primary action: Add a habit via the add form.
  • Supporting action: Complete a habit by toggling its round check button for today.
  • Domain entities: Habit (name, ownership), daily completion record.
  • Component responsibilities: Add form with submit control; habit rows with round check buttons; inline validation and error messaging; empty state when no habits exist.
  • States: Loading while habits are fetched; empty state with a prompt to add the first habit; success shows the updated list and check state; error on add or completion shows a message with recovery (retry).
Page 6 of 18

Weekly Insights

  • Information/state: A seven-day bar row in teal showing the week's completion counts, with one terracotta bar marking the best day; one summary panel summarizing the week.
  • Primary action: Review the week's habit consistency.
  • Supporting action: Navigate back to Dashboard or Habits.
  • Domain entities: Daily completion records aggregated by day for the current week.
  • Component responsibilities: Seven-day bar row; summary panel; navigation to the other working pages.
  • States: Loading while weekly data is fetched; empty state when there is no completion data for the week; success shows bars and summary; error shows a retry affordance.
Page 7 of 18

3. Functional Requirements

FR-1 — Public entry and product explanation (explicit; owner: Landing) As a Habit tracker user, I should see a public Landing page that explains Daylight and its habit tracking purpose, with the headline "Small habits, steady daylight", the subline "Track your habits each day. See your progress and your weekly insights.", and a "Start today" call to action, so that I understand the product before signing in.

  • Trigger: visiting the application while not signed in.
  • Observable result: the Landing page renders with hero, explanation, and CTA.
  • Continuation: the CTA leads to Sign Up; a supporting link leads to Login.
  • Failure/recovery: standard page-load failure shows a retry.

FR-2 — Self-service enrollment (required_inference; owner: Sign Up) As a Habit tracker user, I should be able to enroll through a Sign Up page so that I can begin a private habit record.

  • Trigger: selecting "Start today" on Landing or the Sign Up link on Login.
  • Input: enrollment form submission.
  • Observable result: a user account is created and the user is taken to the Dashboard.
  • Failure/recovery: invalid input shows inline validation; submission failure shows a message with retry.
Page 8 of 18

FR-3 — Returning-user verification (required_inference; owner: Login) As a Habit tracker user, I should be able to verify my identity through a Login page so that I can reach my private habit records.

  • Trigger: visiting Login directly or via the Landing link.
  • Input: credential submission.
  • Observable result: identity is verified and the user is taken to the Dashboard.
  • Failure/recovery: invalid credentials show an error with retry; the user may navigate to Sign Up.

FR-4 — Dashboard daily progress (explicit; owner: Dashboard) As a Habit tracker user, I should see my daily progress on the Dashboard so that I know how much of today's plan is done.

  • Trigger: opening the Dashboard while signed in.
  • Observable result: one large progress ring shows today's completed habits against today's total habits, with a slow 400ms fill easing; today's habit list shows each habit's completion state.
  • Failure/recovery: fetch failure shows a retry affordance; empty state prompts navigation to Habits.

FR-5 — Add habits (explicit; owner: Habits) As a Habit tracker user, I should be able to add habits on the Habits page so that I can track the habits I care about.

  • Trigger: submitting the add form on Habits.
  • Input: habit name.
  • Observable result: the new habit appears in the habit list and counts toward today's progress.
  • Failure/recovery: empty or invalid name shows inline validation; submission failure shows a message with retry.
Page 9 of 18

FR-6 — Complete habits (explicit; owner: Habits) As a Habit tracker user, I should be able to complete habits on the Habits page so that I can record today's progress.

  • Trigger: toggling the round check button on a habit row.
  • Observable result: the habit's completion state for today updates and is reflected in the Dashboard progress ring.
  • Failure/recovery: completion failure shows a message with retry and preserves the prior state.

FR-7 — Weekly insights (explicit; owner: Weekly Insights) As a Habit tracker user, I should see weekly insights on the Weekly Insights page so that I can review how my week went.

  • Trigger: opening Weekly Insights while signed in.
  • Observable result: a seven-day bar row in teal shows the week's completion counts, one terracotta bar marks the best day, and a summary panel summarizes the week.
  • Failure/recovery: fetch failure shows a retry affordance; empty state shows when there is no completion data for the week.

FR-8 — Clean, friendly design with teal accents (explicit; cross-cutting) As a Habit tracker user, I should experience a clean, friendly design with teal accents across all pages so that the tool feels calm and encouraging.

  • Observable result: teal marks progress and controls; terracotta marks one alert or streak only; oat background, warm surfaces, and the specified typography are applied consistently.

FR-9 — Focused first version (explicit; cross-cutting) As a Habit tracker user, I should encounter only the three working pages plus the public entry and access surfaces so that the product stays simple.

  • Observable result: no additional destinations or capabilities beyond Landing, Sign Up, Login, Dashboard, Habits, and Weekly Insights.
Page 10 of 18

4. User Personas

Habit tracker user

  • Product context: A single person who wants a lightweight, private record of daily habits. They open Daylight daily to check progress and mark habits complete, and weekly to review consistency.
  • Primary goal: Keep a small set of habits and see steady progress without friction or clinical measurement.
  • Distinct accepted responsibilities: Enrolls through Sign Up; verifies identity through Login; adds habits on the Habits page; completes habits by toggling round check buttons; views daily progress on the Dashboard; reviews the week on Weekly Insights.
  • Relevant inputs or decisions: Habit names; which habits to complete today; when to review the week.
  • Interactions with other accepted participants: None beyond the application itself; habit data is private to this user.
  • Observable success: The Dashboard progress ring reflects today's completions; the Habits list shows added habits and their check states; Weekly Insights shows a seven-day bar row with the best day marked in terracotta and a summary panel.

5. Core User Flows

Page 11 of 18

Flow A — First-time enrollment and first habit

  1. The user visits Daylight while not signed in and lands on the Landing page, seeing the headline "Small habits, steady daylight", the subline, and the "Start today" CTA.
  2. The user selects "Start today" and arrives at Sign Up.
  3. The user submits the enrollment form. On success, the account is created and the user is taken to the Dashboard.
  4. The Dashboard shows an empty state because no habits exist yet, prompting navigation to Habits.
  5. The user opens Habits, enters a habit name in the add form, and submits. The habit appears in the list.
  6. The user returns to the Dashboard and sees the progress ring reflect the new habit as not yet complete.
  • Failure/recovery: Invalid enrollment input shows inline validation; add-form errors show a message with retry.

Flow B — Daily completion

  1. The signed-in user opens the Habits page.
  2. The user toggles the round check button on a habit row to mark it complete for today.
  3. The habit's check state updates, and the Dashboard progress ring reflects the new completion on next view.
  • Failure/recovery: A completion failure shows a message with retry and preserves the prior state.
Page 12 of 18

Flow C — Daily progress check

  1. The signed-in user opens the Dashboard.
  2. The user sees the large progress ring showing today's completed habits against today's total, with a slow 400ms fill easing, and the habit list with each habit's completion state.
  3. The user may navigate to Habits to complete remaining habits or to Weekly Insights to review the week.
  • Failure/recovery: Fetch failure shows a retry affordance.

Flow D — Weekly review

  1. The signed-in user opens Weekly Insights.
  2. The user sees the seven-day bar row in teal with one terracotta bar marking the best day, and the summary panel summarizing the week.
  3. The user may navigate back to Dashboard or Habits.
  • Failure/recovery: Fetch failure shows a retry affordance; an empty state shows when there is no completion data for the week.

Flow E — Returning-user login

  1. The returning user visits Daylight and selects the Login link on Landing (or navigates directly to Login).
  2. The user submits credentials.
  3. On success, the user is taken to the Dashboard with their existing habits and progress.
  • Failure/recovery: Invalid credentials show an error with retry; the user may navigate to Sign Up.
Page 13 of 18

6. Visuals Colors and Theme

The creative direction (Humane technology after Yves Béhar) is authoritative for this section.

  • Muse and headline: Yves Béhar; the feeling is calm, warm, and encouraging, not clinical.
  • Mode: Light mode.
  • Colors by role:
    • Background (oat): #F4EFE6
    • Surface: #FFFDF8
    • Text (ink): #1F3A38
    • Primary (teal): #0E7C74
    • Accent (terracotta): #E8734A
    • Muted: #6E7F7C
  • Typography: Headings in Work Sans, Medium weight, sentence case, tight tracking, large calm sizes. Body in Karla. Modular scale 1.25: 48/38/28/20/16; mobile 34/28/22/17/15.
  • Shape language: Soft rounded cards with 20px radii; thin warm rules divide rows; one circle shows daily progress.
  • Layout: Single column with wide margins. Dashboard shows one large progress ring and a habit list. Habits page uses a simple add form and check rows. Weekly Insights shows a seven-day bar row and one summary panel.
  • Imagery: Soft still-life photos in natural light — a plant, a glass of water, and a notebook on oat cloth. No stock people.
  • Avoid: No blue or indigo accents; no gradient blobs or glass panels; no grid of identical hover-lift cards; no Inter, Roboto, or system-ui fonts; no sharp black-and-white editorial contrast.
Page 14 of 18

7. Signature Design Concept

The public entry (Landing) is composed as a warm oat ground filling the screen. A large teal progress ring sits left at 40 percent width, with a soft inner shadow. The headline stacks right in ink at 48px to 72px, reading "Small habits, steady daylight", with the subline beneath it and the "Start today" CTA as a solid teal pill under the headline. Section openers use a small terracotta dot and a short label above the heading. Habit rows elsewhere use a soft oat card with a thin warm rule and a round check button. The Weekly Insights page shows a seven-day bar row in teal with one terracotta bar for the best day. The concept recomposes only accepted content and controls.

Page 15 of 18

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: layered_2d

Landing Hero Motion Brief

  • Focal subject: The large teal progress ring beside the oversized headline, on a warm oat ground.
  • Input → transformation → outcome thesis: On load, the progress ring fills slowly (400ms easing) from empty to its resting state while the headline and subline fade in; the outcome is a composed, calm first frame that invites the "Start today" action.
  • Motion vocabulary: Slow 400ms easing on progress fill and check marks; no bounce; gentle fade reveals each section on scroll.
  • Composed first frame: Oat background, teal ring left at 40 percent width, ink headline stacked right, teal CTA pill beneath.
  • Reduced-motion state: The ring renders at its resting fill and all sections are visible without fade or scroll animation.
Page 16 of 18

9. Non-Functional Requirements

  • NFR-1 — Private data access (required_inference): Habit records are reachable only after identity is established through Sign Up or Login; the Dashboard, Habits, and Weekly Insights pages require login.
  • NFR-2 — Persistence (explicit via planning scope): Habit and completion data persist in the application database so daily progress and weekly insights survive sessions.
  • NFR-3 — Readable layout (explicit design constraint): Headlines, labels, numbers, cards' text, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit; no element covers readable text or controls.
  • NFR-4 — Reduced motion (explicit design constraint): With prefers-reduced-motion, a usable static arrangement is provided.
  • NFR-5 — Design consistency (explicit): Teal accents mark progress and controls; terracotta marks one alert or streak only; the specified palette, fonts, and shape language apply across all pages.

10. Tech Stack

  • Frontend: React application UI.
  • Backend: Shared FastAPI process for application APIs and domain modules (habits, completions, progress, weekly aggregation, identity).
  • Database: MariaDB for application-owned persistent data.
  • Deployment: docker-compose with the backend, database, and frontend services.
Page 17 of 18

11. Assumptions and Constraints

  • A-1: The product is named Daylight; "polar-habit" was a project-name selection and does not change the product name shown to users.
  • A-2: The first version is limited to the six pages in the page contract; no additional destinations or capabilities are added.
  • A-3: Identity is application-owned and self-service; enrollment and login are the only account surfaces.
  • A-4: Weekly insights cover the current week's daily completion counts.
  • A-5: The creative direction supplies all visual tokens; no additional designer selection is invented.

12. Glossary

  • Habit: A named behavior the user wants to track, owned by the user's account.
  • Completion: A record that a habit was marked complete for a given day.
  • Daily progress: Today's completed habits against today's total habits, shown as a progress ring on the Dashboard.
  • Weekly insights: A seven-day view of completion counts with the best day marked, shown on the Weekly Insights page.
  • Progress ring: The single circular indicator of daily progress.
  • Oat ground: The warm background color #F4EFE6 used across pages.
Page 18 of 18
Live
Landing design preview

Landing: Read product explanation

Sign Up: Select Start today

Sign Up: 1. Submit enrollment form

Sign Up: 2. Correct invalid input

Sign Up: 3. Retry failed submission

Dashboard: View empty progress state

Habits: Open add form

Habits: 1. Submit new habit name

Habits: 2. Retry failed habit add

Dashboard: View updated progress ring

Habits: 1. Toggle habit check button

Habits: 2. Retry failed completion

Dashboard: 1. View reflected completion

Dashboard: 2. Retry failed progress fetch

Weekly Insights: 1. Review seven-day bars

Weekly Insights: 2. Retry failed weekly fetch

Weekly Insights: View empty week state

Dashboard: Return to daily progress

Landing: Select Login link

Login: 1. Submit credentials

Login: 2. Retry invalid credentials

Login: Navigate to Sign Up

Dashboard: View existing habits and progress

Live
Landing design preview

Landing: Read product explanation

Sign Up: Select Start today

Sign Up: 1. Submit enrollment form

Sign Up: 2. Correct invalid input

Sign Up: 3. Retry failed submission

Dashboard: View empty progress state

Habits: Open add form

Habits: 1. Submit new habit name

Habits: 2. Retry failed habit add

Dashboard: View updated progress ring

Habits: 1. Toggle habit check button

Habits: 2. Retry failed completion

Dashboard: 1. View reflected completion

Dashboard: 2. Retry failed progress fetch

Weekly Insights: 1. Review seven-day bars

Weekly Insights: 2. Retry failed weekly fetch

Weekly Insights: View empty week state

Dashboard: Return to daily progress

Landing: Select Login link

Login: 1. Submit credentials

Login: 2. Retry invalid credentials

Login: Navigate to Sign Up

Dashboard: View existing habits and progress