Contact

The short version

This site is a small, independent project, and the fastest way to improve it is a clear message from someone who uses it. A direct email channel is being set up and will be published here as soon as it is live — we would rather publish nothing than publish an address that silently swallows mail. In the meantime, this page explains exactly what makes a report useful, so your first message (when the channel opens) is also your most effective one.

What to contact us about

Reports fall into a few buckets, and each one is genuinely welcome:

• Bugs — the timer drifts, the alarm does not sound, fullscreen misbehaves, the layout breaks on a particular device. If something behaves differently from what these pages promise, that is a bug and we want it.
• Feature ideas — a duration preset you expected and did not find, a sound you wish existed, a display option your classroom needs. Concrete classroom stories beat abstract feature requests every time.
• Accessibility feedback — anything that makes the timers harder to use with a screen reader, low vision, or a keyboard-only setup. These reports get priority.
• Content corrections — if a translated page reads awkwardly in your language, tell us. The site is maintained in English, French, German, Spanish, Japanese and Korean, and native ears catch what templates cannot.
• Privacy questions — anything on the privacy page that seems unclear or overreaching. Answering those honestly matters more than any feature.

What to include in a bug report

The difference between a bug fixed in a day and a bug fixed in a month is usually the first message. Include what you can of this list:

1. The page and what you did. The URL (for example the 10 minute timer page) and the exact steps: "Started the timer, switched to another tab for two minutes, came back."
2. What you expected and what happened. "Expected 04:12 remaining, display showed 09:58." One sentence each is enough.
3. Device and browser. "Chrome on Windows," "Safari on an iPad," "school-managed Edge." Managed school machines have unusual settings, and knowing that saves hours.
4. Whether sound was involved. Alarm sounds depend on the browser granting audio permission after your first click — if the bell stays silent, note whether you pressed Start first.
5. A screenshot if the layout is wrong. A picture of broken digits is worth a thousand words of description.

You do not need all five. Two of them already shrink the search space enormously.

Known limitations (not bugs)

A few behaviors are intentional, so you can save a report:

• Refreshing a timer page resets the countdown to that page's default duration. Persisting sessions across reloads is a deliberate non-feature for now.
• The alarm cannot play while the device is asleep — the page shows the finished state as soon as it wakes.
• Laps on the stopwatch live only for the current visit. There is no history by design, and nothing about your usage is stored on a server.
• The countdown measures time with your device's clock; it cannot control other apps, lock your screen or send notifications after the tab closes.

If one of these limits blocks a real classroom workflow, that is exactly the kind of feedback worth sending — "known limitation" is not the same as "correct forever."

What happens after you write

Reports are read by the people who build the site, triaged by how much they break classrooms, and answered when an answer is useful. Small fixes (wrong label, broken layout on one browser, awkward translation) usually ship quickly because each page is deliberately simple. Bigger ideas get weighed against the project's core promise — free, fast, no account — and anything that conflicts with it gets a polite no with the reason stated.

No newsletters are sent, no accounts are created, and your address is never used for anything beyond the reply to your message.

A note on response expectations

This is a side project maintained with care but not with a support team. Most messages get a reply within a couple of weeks; fixes for clear bugs often appear before the reply does. If something is urgently broken for your lesson tomorrow, the workaround is almost always another page on this site or a browser refresh — the tools are deliberately interchangeable that way.

Thank you

Every report makes the timers better for the next teacher, student, coach and cook who types "10 minute timer" into a search box at the start of something. That is the whole feedback loop, and it works because people like you spend ninety seconds writing what happened. When the direct channel opens, it will be linked right here — plain, single, and actually read.