Personal · Daily tracker
Mark the habit you actually did and let the history—not guilt or points—show the pattern.
Habit Tracker is a small daily check-in tool for people who want an honest view of consistency. Add a habit, toggle completion across the last seven days, and review current streak, best streak, and rolling 30-day activity. This Foundationbase implementation stores one simple habit array in the current browser, requires no account, and provides source you can adapt into a routine coach, monthly tracker, or scheduled-habit system.
Open the working toolProduct preview
These screens come from the working Foundationbase implementation.
What this tool helps you do
A reusable checklist can say what should happen today, but it does not show whether the behavior happened yesterday or how a pattern developed. At the other extreme, points, social competition, and complex goal systems can make a small routine feel like another product to manage.
Each habit contains only a name and the date keys on which it was completed. The interface turns that history into a seven-day grid, a current streak, a best streak, total check-ins, and a rolling 30-day completion rate. There are no generated achievements or invented trends.
What is included
Each habit displays today and the previous six dates as individual toggle buttons.
Why it matters: Daily use is fast, and a recently missed or mistaken check-in can be corrected without editing raw data.
Verified in: WeekGrid date generation and toggle
A completion is stored as a yyyy-mm-dd value in the habit's done array, not as a visual counter.
Why it matters: Streaks and statistics can be recalculated from the actual history.
Verified in: Habit type and useLocalState
The tracker counts backward from today when completed, or yesterday when today is not yet complete, until it reaches a missing date.
Why it matters: A current run remains meaningful during the day before the next check-in is made.
Verified in: streak function
The app sorts completion dates and finds the longest sequence of consecutive days for each habit.
Why it matters: Past consistency remains visible even after a current streak ends.
Verified in: bestStreak function
For each habit, the tracker counts completion dates from 29 days ago through today and displays days completed out of 30.
Why it matters: The recent pattern is visible without relying only on a fragile streak.
Verified in: last30Count and HabitStats
The Stats view totals all 30-day check-ins, divides by habits times 30 for an overall rate, and shows the largest best streak.
Why it matters: A small dashboard gives context across the whole habit list.
Verified in: HabitStats aggregate calculations
Add a habit from one name field or delete a habit and all completion dates attached to it.
Why it matters: The list can stay short enough to remain usable.
Verified in: Manage view
The habit array is serialized to one versioned localStorage key and restored in the same browser.
Why it matters: The tracker needs no account or database while keeping its storage model easy to customize.
Verified in: Foundationbase.habit-tracker.v1 and useLocalState
How it works
The implemented loop is intentionally small: define, check in, inspect, and prune.
Open Habits & streaks, enter a short name, and add it to the existing list.
The new habit begins with an empty completion history.Tap today's cell when the habit is done, or toggle one of the six preceding dates to correct recent history.
That date is added to or removed from the habit's done array.The week and management views calculate consecutive completion days from the stored date keys.
You see continuity without manually maintaining a counter.Open Stats to compare check-in count, overall rate, best streak, and per-habit recent activity.
A broader pattern can balance the all-or-nothing feeling of a streak.Delete habits that are no longer useful. The current app removes the habit and its history immediately.
The tracker stays focused, though deletion has no undo.Real use cases
For an individual
Situation: You want to track a few concrete actions such as walking, stretching, or reading without planning a whole day.
Workflow: Keep each action as a habit, tap today's cells, and glance at the recent-week pattern.
Outcome: The routine remains visible without becoming a complex task system.
For someone rebuilding a routine
Situation: A missed day makes a single streak feel discouraging even when the last month was mostly consistent.
Workflow: Use current streak for continuity and the 30-day completion count for broader context.
Outcome: Recent behavior is judged from more than one number.
For a coach
Situation: You want to test a simple habit model and language before adding clients, reminders, or shared data.
Workflow: Create a source copy, group or rename habits, adjust supportive copy, and add only the fields needed for the method.
Outcome: The prototype begins with real history and statistics rather than static mockups.
For a developer learning React
Situation: You need a small domain model with persistence and derived statistics that is understandable in one component.
Workflow: Inspect Habit, toggle, streak, bestStreak, and last30Count, then add a scoped schedule or backup feature.
Outcome: A concrete tracker becomes the base for learning or experimentation.
Who it is for
Use it, install it, or make it yours
Open the live tracker, toggle the seeded habits, add your own, or reset the demonstration state. Changes persist in the same browser profile.
Download the source package and inspect the compact Habit type, date helpers, check-in grid, statistics, and local-storage hook.
Ask a coding agent for weekday schedules, quantity targets, a monthly view, archive, export, or reminders. Each adds new behavior beyond the current simple date-array model.
Publish the customized Next.js project to a compatible host and use its stable URL as your own tracker. Add a manifest and service worker before presenting the copied version as installable or offline-capable.
Customization ideas
The current model is deliberately narrow: each habit is a name plus completion dates. Preserve that simplicity for visual changes, or version and migrate the stored data when schedules, quantities, notes, or archive state are introduced.
Add weekday schedules to Habit Tracker. A habit can run every day or on selected weekdays. Update streak and 30-day completion calculations so unscheduled days do not count as misses, and migrate existing local habits to every day.Add JSON backup and restore to Habit Tracker. Export habit names and completion dates with a schema version, validate every date and id on import, preview replacement, and keep the app account-free.Add a monthly calendar view to Habit Tracker using the existing yyyy-mm-dd done arrays. Do not replace the seven-day quick-check view, and keep keyboard labels descriptive for each habit and date.Technical details
Privacy and data behavior
By default, Habit Tracker stores habit names and completion dates in localStorage in the current browser. The component does not require an account or send check-in records through an application API. Local storage is a device boundary, not a backup or encryption guarantee.
Location: One JSON state object in the current browser profile under Foundationbase.habit-tracker.v1
Network: The Habit Tracker component performs no application data fetches. Normal site assets still load from the host serving the page.
Delete: Delete a habit to remove its name and history immediately, reset to restore sample habits, or clear the site's browser data.
Export: No export or import method is included in the current implementation.
Verification and known limitations
Foundationbase verification checks expected functionality, packaging, setup clarity, and common implementation concerns. It is not a professional security audit, accessibility certification, legal review, or guarantee of production suitability.
Comparison
The useful comparison is how each option records time, calculates consistency, and handles data ownership.
| Decision | Foundationbase tool | Starting from scratch | Generic alternative |
|---|---|---|---|
| Habit model | A name and exact completion dates | You choose schedule, goal, and history fields | Often includes categories, schedules, goals, and reminders |
| Recent check-in | Editable seven-day date grid | You build date navigation and toggles | Usually available with product-specific UX |
| Streak logic | Current and best consecutive calendar days | You define edge cases and test them | May account for schedules, freezes, or grace days |
| Broader trend | Rolling 30-day counts and rate | You design summary windows | Often richer charts and reports |
| Reminders | Not included | You choose browser, native, email, or calendar | Commonly included |
| Data location | One browser localStorage record | You choose local or remote | Usually cloud account data |
| Customization | MIT source and small date-array model | Full freedom without working behavior | Limited to exposed settings |
FAQ
The app counts consecutive stored completion dates backward. If today is complete, it starts today; otherwise it starts yesterday. It stops at the first missing calendar day.
Not accurately in the current implementation. Every habit is treated as daily, so a scheduled day off would interrupt a streak. Weekday schedules require a model and calculation change.
Habit names and completion dates are stored in localStorage in the current browser profile under Foundationbase.habit-tracker.v1.
No. The current app has no export or import control. JSON backup with validation is a recommended customization before relying on the tracker for long-term records.
No. It does not schedule browser, push, email, or calendar notifications. The tracker records check-ins only when you open and use it.
The current Habit Tracker does not have a dedicated verified manifest and service-worker package, so this page does not present it as installable or offline-capable.
Yes, by modifying the source. A monthly calendar can reuse the existing date-key history; grouped routines or schedules need new fields and migration defaults for existing habits.
Start from something real
Use the working seven-day tracker, or take the source and add the schedules, views, backups, and supportive language that fit your routine.