We Want to Hear From You

What happens after feedback

We group feedback by product area: timer reliability, sounds and notifications, mobile layout, accessibility, embeddable timers, guide accuracy, and workflow tools. Reports that affect core timer behavior or data privacy are treated as higher priority than cosmetic preferences.

If a request matches a common workflow, we usually improve the existing page rather than creating a disconnected feature. That keeps the site easier to crawl, easier to maintain, and easier for users to understand.

We also use feedback to catch confusing language in guides, missing alt text, broken links, and workflow pages that should be merged, expanded, or redirected.

Good feedback does not need to be polished. A short note with the page URL and the moment where you got stuck is usually enough to improve the product.

For timer issues, the most useful detail is timing: did the problem happen before starting, while running in the background, at completion, after a browser sleep, or after returning from another tab? That tells us whether to inspect state, notifications, audio, storage, or page visibility behavior.