Health · Local-first timer
Begin a focused session, keep a private practice history, and own the app you use.
Meditation App is a phone-friendly timer for people who want a simple self-directed practice. Choose or create a preset, run the countdown, and keep completed or partial sessions in this browser. This Foundationbase version includes validated JSON backups, a real installable web manifest, an offline service worker, and source instructions for changing the practice flow.
Open the working toolProduct preview
These screens come from the working Foundationbase implementation.
What this tool helps you do
A basic alarm can end a session, but it does not preserve reusable intentions, distinguish completed and partial practice, or provide a portable backup. Larger meditation platforms often add content libraries, accounts, subscriptions, and cloud profiles that are unnecessary for a personal timer.
This tool keeps the practice loop small: select a named duration, begin, finish when the countdown reaches zero or end early, and let the app record what happened. Presets, session records, and preferences remain in versioned browser storage until you export, import, delete, or reset them.
What is included
Select a saved duration and intention, then run a second-by-second countdown. Ending after at least one minute records a partial session; reaching zero records a completed one.
Why it matters: A familiar practice starts in one step while the history remains honest about how the session ended.
Verified in: MeditationApp.tsx Timer component
Add a preset with a name, a duration from one to 240 minutes, and an intention. The new preset becomes the selected session and persists locally.
Why it matters: Different routines can carry their own timing and purpose without being rebuilt each day.
Verified in: Preset type, validation, and Presets view
Each record keeps its start time, date, preset identity, duration, and completed state. Individual history entries can be removed.
Why it matters: The tool can summarize real practice while keeping the underlying records understandable.
Verified in: Session type and History view
The timer and history views calculate sessions today, total minutes, completed sessions, and consecutive completed days.
Why it matters: Useful continuity signals are derived from session records rather than entered as decorative metrics.
Verified in: currentStreak and history summary calculations
Export downloads a versioned JSON envelope. Import checks the schema, presets, sessions, and preferences before replacing current data.
Why it matters: Data can move between browsers without accepting an incompatible or malformed file blindly.
Verified in: validateData, exportData, and importData
A web manifest supplies a standalone display mode, start URL, theme, orientation, and 192- and 512-pixel icons.
Why it matters: Supported browsers can add the timer to a phone home screen without an app-store package.
Verified in: public/manifest.webmanifest and demo layout metadata
The registered service worker caches the app shell and recent navigation responses, then falls back to an offline page when the network is unavailable.
Why it matters: After a successful first visit, the timer has a deliberate repeat-use path when connectivity drops.
Verified in: public/sw.js service-worker registration and cache strategy
The source separates template metadata and the agent prompt from timer behavior, and includes README, DATA, CUSTOMIZE, DEPLOY, and AGENTS guidance.
Why it matters: A coding agent can inspect the data contract and PWA files before changing the timer.
Verified in: foundationbase.ts and packaged documentation
How it works
The actual workflow follows the timer and local data model rather than a generic onboarding sequence.
Select Morning reset, Midday pause, Evening release, or a preset you created with its own duration and intention.
The countdown resets to that preset's duration.Press Begin to record the start time and run the timer once per second.
The circular progress indicator and remaining time update during the session.Let the countdown finish, or end early. Sessions shorter than one minute are discarded; longer early endings are saved as partial.
History reflects what actually happened.Open History to see each preset, duration, timestamp, and completed or partial status, plus aggregate totals.
You can inspect or remove individual records.Export the JSON file from Settings and import it in another browser. The importer validates the file before replacement.
Presets, sessions, and preferences move manually without a cloud account.Real use cases
For an individual meditator
Situation: You use the same short morning practice and do not need guided audio or social features.
Workflow: Select the morning preset, run the timer, and review the completed-day streak when useful.
Outcome: A repeatable practice and history stay in the browser you control.
For someone alternating short and long sessions
Situation: Weekday pauses and weekend sessions use different durations and intentions.
Workflow: Create separate presets, choose the relevant one before each sitting, and let history retain the preset name.
Outcome: One small tool supports distinct routines without a complex content library.
For a meditation or wellness coach
Situation: You want a branded timer that reflects a method before investing in accounts or a backend.
Workflow: Create the source copy, rename the presets and guidance, adjust the theme, and deploy a stable URL for clients.
Outcome: A focused prototype starts from working timing, storage, backup, and PWA behavior.
For a developer or curious builder
Situation: The core need is a trustworthy countdown and local history, but the domain is breathwork or deep work.
Workflow: Adapt the preset fields and timer labels while preserving the versioned storage and import validator.
Outcome: The timer becomes a different focused tool without discarding its tested data boundaries.
Who it is for
Use it, install it, or make it yours
Open the live timer, select a preset, and begin. Sessions and settings are written to this browser's localStorage; no registration screen or remote profile is involved.
On a supported Android browser, use Install app; on iPhone, use Safari's Share menu and Add to Home Screen. Installation uses the real manifest. Offline repeat use depends on the service worker having cached the app after an online visit.
Download the MIT-licensed source package with the timer code, versioned data model, manifest, service worker, icons, and setup, data, customization, deployment, and agent instructions.
Ask a coding agent to add interval bells, a preparation phase, notes, different themes, or another practice model. Prompts should preserve import compatibility when the stored schema changes.
Run the project's checks, publish it to a host that supports the chosen Next.js/static configuration, and use that stable HTTPS URL as your own app link and installation target.
Customization ideas
The timer, presets, data validator, PWA files, and template metadata are identifiable seams. Small visual changes can stay local to copy and CSS; data-model changes should update validation and backup compatibility together.
Add preparation and interval bells to Meditation App. Let each preset choose a preparation delay and interval length. Update the Preset type, validateData import checks, and JSON backup format without breaking existing version 1 backups.Add optional notes to completed and partial meditation sessions. Keep Foundationbase.meditation-app.v1 readable, migrate records that have no note, update export/import validation, and keep all data local by default.Create a weekly practice review from the existing Session records. Show completed minutes by day and do not add accounts, analytics, or a remote API.Technical details
Privacy and data behavior
By default, Meditation App stores presets, sessions, and preferences in this browser. The implementation does not call an application API, create an account, or transmit practice records. Manual export creates a file only when you request it.
Location: localStorage in the current browser profile under Foundationbase.meditation-app.v1
Network: The app loads site assets and the service worker may fetch and cache app responses. No third-party data service receives the stored meditation records in the current code.
Delete: Delete individual sessions, remove presets while at least one remains, or confirm Reset Data to replace the local dataset with defaults. Clearing site data also removes it.
Export: Export Data downloads a JSON backup; Import Data validates a selected JSON file before replacing current data.
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 choice is not which product makes the broadest promise; it is which starting point already contains the timing, history, privacy, and ownership boundaries you need.
| Decision | Foundationbase tool | Starting from scratch | Generic alternative |
|---|---|---|---|
| Timer logic | Working preset countdown with completed and partial session records | You design countdown, interruption, and completion behavior | Usually fixed by the provider |
| Practice history | Local session records, totals, and derived streak | Requires a data model and summary calculations | Often tied to a cloud account |
| Offline use | Manifest and service-worker fallback are included | You implement and test the PWA lifecycle | Varies by plan and platform |
| Data portability | Validated JSON export and import | You define format, validation, and migration | Export may be absent or provider-specific |
| Guided content | Not included; this is a self-directed timer | You source and license content | Often the main product feature |
| Customization | MIT source plus architecture-specific agent instructions | Complete freedom with no working baseline | Usually limited to settings |
| Accounts and sync | No account and no automatic sync | You choose whether to add them | Commonly required for history |
FAQ
Yes. The live tool is free to use, and the downloadable source is listed under the MIT license. Review the license text in your copy before distributing a modified version.
Yes, where the browser supports installation or Add to Home Screen. The app has a standalone web manifest and icons. Android and iPhone use different browser menus, and offline repeat use starts only after the service worker has cached the required app responses.
Sessions, presets, and preferences are stored in localStorage for the current browser profile under Foundationbase.meditation-app.v1. They do not automatically appear on another device or in another browser.
Not through the current settings. The source is structured so a developer or coding agent can extend the Preset type and Timer component. Any new stored fields should also be added to import validation and backup compatibility.
No. This implementation is a self-directed timer and history tool. It stores a sound preference, but the current countdown does not play a chime or include an audio library.
Yes, manually. Export a JSON backup from Settings, move the file to the other device, and import it there. The tool validates the backup before replacing current local data.
No. There is no account, backend, or automatic sync in the current implementation. Optional sync is an advanced customization that would change the privacy and deployment model.
Start from something real
Start a private session in the working tool, or take the source and adapt the presets, practice flow, data model, and visual language into your own app.