A conventional Pomodoro timer has a simple job: count down a work interval and announce a break. That is useful, but it leaves out the parts of a session that determine whether someone can stay with the work: sound, context, rhythm, and visibility.
Pomoria started as an experiment in treating focus as an environment instead of a counter.
The session is a small state machine
A flexible focus session can be represented as a sequence of steps. Each step has a duration, a type such as work or break, and optional context such as a note or intention.
That model supports more realistic routines:
- a short planning step before a writing block;
- two deep-work blocks separated by a recovery break;
- a longer reading block followed by a short review;
- a custom sequence for a recurring creative workflow.
The important design decision is that the sequence belongs to the user. A fixed 25/5 preset is a useful starting point, but it should not be the boundary of the product.
Why local audio is useful
Ambient audio can be created and mixed directly in the browser with Web Audio APIs. A focus environment can use oscillators, gain nodes, filters, and scheduled changes to build a sound layer without sending the session to a server.
There are practical benefits:
- no audio file needs to be uploaded for the core experience;
- the sound can respond to the current step;
- users can adjust layers independently;
- the session can remain usable offline after the page is available;
- the design is easier to explain in privacy terms.
Local does not mean every browser feature works identically everywhere. Autoplay restrictions, device volume, headphones, and browser power-saving behaviour still matter. A good interface should make the first interaction explicit and keep controls understandable.
Mixing layers without making noise
More layers do not automatically make a better environment. Each source should have its own gain control, and the default levels should be conservative. White, pink, and brown noise can be treated as alternative beds rather than three sounds that must all play together.
Rain can add texture. A binaural tone can be optional. The user should be able to remove any layer immediately and still keep the timer running.
Keeping the session visible
Picture-in-Picture changes the relationship between the timer and the work surface. Instead of asking the user to keep returning to a full tab, the active session can remain visible in a small window while the user writes, codes, or reads elsewhere.
This is a small feature with an important product implication: visibility should support attention rather than interrupt it. The timer should be available when needed and quiet when it is not.
What “local-first” does not promise
Local processing is not a promise that the entire product is offline or that every browser stores every setting forever. It is a design direction: keep the core focus experience in the browser, make data movement explicit, and avoid requiring an account just to start a session.
Being precise about this builds more trust than using “private” as a vague marketing word.
The product lesson
The main lesson from building Pomoria is that a focus product should model the environment around the work. The countdown is one component. A useful session also needs a beginning, a middle, and an end; a rhythm that fits the task; sound that can be tuned; context that can be remembered; and a view that stays available.
Pomoria is an early implementation of that idea: a browser-based focus environment with custom sequences, local ambient sound, and Picture-in-Picture. It is freemium and can be started without installing anything or creating an account: https://pomoria.app/
Questions for other builders
- Which browser audio constraints have affected your product design?
- When does a persistent timer help rather than distract?
- Which settings should belong to a session template instead of a user account?
Top comments (0)