Daylight is a simple personal habit tracker for everyday people who want gentle daily momentum and a weekly view of their effort. The product is deliberately small: a dashboard that shows daily progress, a habits page where the user adds habits and marks them complete, and a weekly insights page that shows how the week is going. The first version stays focused on these three pages, wrapped in a clean, friendly design with teal accents.
The audience is a single kind of person: someone tracking their own habits privately, day by day, who wants a warm and encouraging surface rather than a clinical productivity tool. Because habit records are personal and must persist between visits, Daylight establishes a private, application-owned record for each person and lets them return to it.
This document is the System Requirements Document for Daylight (project name: icy-habit). It specifies the product's features and workflows in full, together with the design language, delivery boundary, and technical stack.
Daylight is a three-page personal habit tracker with a private, per-person record. The current delivery consists of:
The only active human actor is the Habit tracker user, who owns their own habits and progress. The application itself owns identity, habit records, completion records, and the derived daily and weekly views. There are no other human roles, no shared or team state, and no differentiated permissions: every signed-in person sees only their own data.
Removed from scope
Daylight is delivered as a first-party web application. The public entry (Landing) and the two identity surfaces (Sign Up, Login) are anonymously reachable. The Dashboard, Habits, and Weekly Insights pages are protected: they require a verified identity so that each person's habits and progress remain private and resumable across visits.
Identity is application-owned and established through self-service enrollment on Sign Up, with returning verification on Login. This is the minimum continuity needed for a personal tracker whose records must persist and belong to exactly one person. It does not introduce roles, sharing, or account administration. All habit data, completion data, and the daily and weekly views are computed and stored by the application backend against the provisioned database.
The first version is bounded to the three core pages plus the entry and identity surfaces required to reach them. Nothing beyond that — reminders, social features, categories, or additional analytics — is part of the current delivery.
FR-1 — Public entry explains Daylight. As a Habit tracker user, I should see a public Landing page that explains Daylight and its habit-tracking purpose, so that I understand the product before starting. (explicit)
FR-2 — Self-service enrollment. As a Habit tracker user, I should be able to create a private account through Sign Up, so that my habits and progress are mine and persist. (required_inference)
FR-3 — Returning identity verification. As a Habit tracker user, I should be able to log in with my credentials, so that I can reach my private pages on return. (required_inference)
FR-4 — Protected access to core pages. As a Habit tracker user, I should only reach Dashboard, Habits, and Weekly Insights after verifying identity, so that my records stay private. (required_inference)
FR-5 — Dashboard shows daily progress. As a Habit tracker user, I should see my daily progress on the Dashboard, so that I know how today is going. (explicit)
FR-6 — Add habits. As a Habit tracker user, I should be able to add a habit on the Habits page, so that I can track something new. (explicit)
FR-7 — Complete habits. As a Habit tracker user, I should be able to mark a habit complete on the Habits page, so that I record today's effort. (explicit)
FR-8 — Weekly insights. As a Habit tracker user, I should see weekly insights on the Weekly Insights page, so that I can review my week's effort. (explicit)
FR-9 — Clean, friendly design with teal accents. As a Habit tracker user, I should experience a clean, friendly interface with teal accents across all pages, so that tracking feels kind rather than clinical. (explicit)
FR-10 — Focused first version. As a Habit tracker user, I should encounter only the three core pages plus the entry and identity surfaces, so that the product stays simple. (explicit)
Following the creative direction (muse: Pablo Stanley — warm modular clarity):
#FBF6EC (cream ground, holds most space)#FFFFFF#12332F#0E8C7F#F2A03D (streaks and small rewards only)#6B807Bclamp(40px, 8vw, 96px) / 40 / 28 / 20 / 16.The public entry is a cream hero with a three-line Nunito headline at left, scaling from 40px on mobile to 96px on desktop, with a hand-drawn teal underline beneath the last word. To the right, three tilted habit sticker-cards stack with teal check marks and soft offset shadows. A pill "Start today" CTA sits under the headline. The concept recomposes only accepted content — the headline, subline, CTA, and Login link — into a warm, sticker-like composition that signals a friendly personal tracker rather than a corporate dashboard.
Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d
Landing Hero Motion Brief
prefers-reduced-motion, motion is suppressed and a usable static arrangement is provided. (explicit via creative direction)
Track your habits each day and see your week grow.
Start today
Track your habits each day and see your week grow.
Start today
No comments yet. Be the first!