Personal · Newborn event tracker
Record the event now so you do not have to reconstruct the day later.
Baby Tracker is a one-tap local log for a caregiver recording bottles, nursing, wet and dirty diapers, sleep, and wake events. Each tap stamps the current date and time, updates today's feed and diaper counts, and contributes completed sleep/wake pairs to sleep duration. This Foundationbase implementation keeps the event list in the current browser and offers source for adding quantities, editable times, notes, exports, or family synchronization.
Open the working toolProduct preview
These screens come from the working Foundationbase implementation.
What this tool helps you do
Care events are frequent, similar, and easy to forget. A free-form note takes too much effort during the event and makes daily counts difficult later. A larger tracking service may add accounts and shared infrastructure before a family knows which details it actually needs.
The Today view reduces capture to event buttons. A tap creates an event with the current local date and time. The interface derives counts and sleep duration from those stored events, while History groups up to 14 dates that contain records into compact daily summaries.
What is included
Dedicated buttons create bottle, nursing, wet diaper, dirty diaper, sleep, or wake events without opening a form.
Why it matters: A caregiver can record the category with minimal attention during a busy moment.
Verified in: Today log buttons and EventType
Each new event receives today's local yyyy-mm-dd key and the current local hour and minute.
Why it matters: The timeline is usable immediately without typing a time for routine real-time capture.
Verified in: todayKey, nowTime, and log
The tool inspects the most recent sleep-related event and shows Wake when the latest state is asleep; otherwise it shows Sleep.
Why it matters: The main action follows the current recorded state rather than displaying both choices all the time.
Verified in: Today asleep calculation and buttons array
Bottle and nursing events are counted together for today's Feeds summary.
Why it matters: A quick total is derived from the timeline instead of maintained separately.
Verified in: Today feeds filter
Wet and dirty events are counted together for today's Diapers summary while remaining distinct in the timeline.
Why it matters: The overview stays compact without discarding event type.
Verified in: Today diapers filter
For one day, sleep and wake events are sorted by time; each wake following a sleep contributes the non-negative minute difference to the total.
Why it matters: Displayed sleep time comes from stored pairs rather than an entered summary.
Verified in: sleepMinutes
Today's events appear newest first with time and event label; any event can be removed from the list.
Why it matters: An accidental tap can be corrected and the totals recalculate from the remaining records.
Verified in: Today timeline
History selects up to 14 unique dates that have events and shows feed, diaper, and sleep summaries for each.
Why it matters: A caregiver can scan recent recorded days without opening every event.
Verified in: History day grouping and slice(0, 14)
How it works
The current implementation is optimized for real-time capture. It does not ask for amount, duration, side, notes, or a corrected time before saving.
The page shows the seeded baby name, current feed, diaper, and paired-sleep totals, and event buttons.
The current day's context is visible before another event is added.Choose Bottle, Nurse, Wet, Dirty, or the current Sleep/Wake action.
A new event receives the current date and time and appears at the top of the timeline.Tap Sleep when a period begins and Wake when it ends on the same day.
Completed pairs contribute minutes to the daily sleep total.Remove an incorrect item from today's timeline. The current interface does not edit its type or timestamp.
Counts and sleep totals recalculate from the remaining events.Open History to see up to 14 dates containing events, each summarized by feeds, diapers, and paired sleep time.
The recent pattern is easier to scan than the full event stream.Real use cases
For a parent using one phone browser
Situation: Feeds and diapers are frequent enough that the order and count blur together by the end of the day.
Workflow: Tap each event when it happens and check today's summary before a handoff or question.
Outcome: The day is reconstructed from timestamped events rather than memory alone.
For two caregivers using the same device and browser profile
Situation: The next caregiver wants to see what was recorded earlier without reading a long message thread.
Workflow: Review today's timeline and totals on the shared browser, then continue logging new events there.
Outcome: A single local record provides continuity as long as everyone uses the same browser storage.
For a caregiver preparing general observations
Situation: You want a quick count of recorded feeds, diapers, and completed sleep pairs across recent days.
Workflow: Open History and scan up to 14 dates that contain events, noting that the app does not capture amounts or medical measurements.
Outcome: A concise personal log can support recall without being treated as a medical record.
For a developer or product builder
Situation: You want to test the minimum event categories before adding quantities, editing, backup, accounts, or sync.
Workflow: Create the source copy, extend BabyEvent deliberately, migrate local data, and add validation for every new field.
Outcome: The richer tool starts from working capture, grouping, and summary calculations.
Who it is for
Use it, install it, or make it yours
Open the live tracker and tap an event at the time it happens. The seeded records and any new events live in the current browser; reset restores the demonstration dataset.
Download the source package and inspect the BabyEvent model, current-time capture, same-day sleep pairing, day grouping, and local-storage state.
A coding agent can add editable timestamps, amounts, notes, pumping, growth, multiple children, or export. These are new data fields and workflows, not existing hidden capabilities.
Publish the customized Next.js project to a compatible host. If separate caregivers need shared data, design authentication, authorization, encryption, conflict handling, and deletion before introducing a remote database.
Customization ideas
Baby Tracker's event model is a useful minimum, but family tracking becomes sensitive quickly. Visual and label edits are small; quantities, medical details, multiple caregivers, and cloud storage require explicit data design and privacy review.
Add editable date and time to Baby Tracker events. Let a caregiver correct an event from the timeline, validate local date and HH:MM input, preserve existing records, and recalculate daily summaries after edits.Add bottle volume in milliliters and nursing duration in minutes to Baby Tracker. Show those fields only for relevant event types, migrate existing events with unknown values, and keep feed count separate from total recorded volume.Add versioned JSON export and import to Baby Tracker. Validate every event id, type, date, and time; preview how many records will replace local data; and do not add an account or third-party service.Technical details
Privacy and data behavior
By default, Baby Tracker stores the baby name and event records in localStorage in the current browser. The component does not require an account or send those records to an application API. That does not make the data encrypted, backed up, synchronized, or suitable for medical use.
Location: One JSON state object in the current browser profile under Foundationbase.baby-tracker.v1
Network: The Baby Tracker component performs no application data fetches. Normal site assets still load from the host serving the page.
Delete: Delete individual events from today's timeline, reset to the seeded demonstration state, or clear site data in the browser. Older events are not individually exposed for deletion in History.
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 relevant questions are which events are captured, how time and totals are calculated, and whether caregivers can safely share the record.
| Decision | Foundationbase tool | Starting from scratch | Generic alternative |
|---|---|---|---|
| Capture speed | One tap creates a current-time event | You design event forms and defaults | Often quick capture plus more fields |
| Feed detail | Counts bottle and nursing events | You choose amount, side, and duration fields | Often includes amounts and nursing timers |
| Sleep logic | Completed same-day sleep/wake pairs | You handle active sessions, midnight, edits, and overlap | Often includes active timers and richer sleep reports |
| History | Up to 14 dates containing events with daily totals | You choose retention and reports | Often long-term charts and exports |
| Caregiver sharing | Only when using the same browser storage | You design identity, permissions, and conflicts | Commonly account-based |
| Data location | One browser localStorage record | Local or remote is your decision | Usually provider-hosted |
| Customization | MIT source with a compact event model | Full flexibility with no baseline | Limited to provider settings |
FAQ
The current app records bottle, nursing, wet diaper, dirty diaper, sleep, and wake event types. Each tap stores the current local date and time.
No. Feeds are event counts only. Amount, side, and duration are recommended data-model customizations and should remain optional for existing records during migration.
Within one day, the app sorts sleep and wake events by time and adds the minutes from each sleep to the next wake. Unmatched sleep events and sleep spanning midnight are not included accurately.
Not with shared data in the current implementation. Each browser has separate localStorage. Real sharing requires accounts or another trusted synchronization design.
The baby name and events are stored in localStorage in the current browser profile under Foundationbase.baby-tracker.v1. The current component does not send them to an application backend.
No. Today's events can be deleted, but their type and timestamp cannot be edited. Editable date and time is a practical source customization.
No. It is a personal event log and is not presented as a clinical system, diagnostic tool, regulated record, medical-device workflow, or substitute for professional care.
No export is currently included. History can be read on screen, but a date-range PDF, CSV, or JSON backup must be added before claiming export support.
Start from something real
Use the one-tap tracker in this browser, or take the source and add the fields, corrections, backups, and caregiver model your family actually needs.