NoBS Timers
No accounts. No ads. No tracking. No bullshit.
Support Independent Development
NoBS Timers is built without ads, telemetry, forced accounts, paid feature gates, or cloud sync. If you want to support the work, use the donation options on the NoBS Apps support section.
Download app
Store listings are not live yet. Use the placeholders below until mobile downloads are ready.
Coming soon
Coming soon
Feedback & Feature Requests
Bug reports, feature proposals, and platform feedback for NoBS Timers belong in the public NoBS Apps feedback queue:
Simple Clock Tools
NoBS Timers keeps everyday timing tools plain, local, and quick to reach from a portrait-only mobile layout.
Pick a time, choose whether it repeats every day, and save it. The app remembers the last saved alarm time and defaults first use to six hours in the future.
The stopwatch has one button: Start, Stop, then Resume. There are no laps, split times, exports, or extra controls.
Enter hours, minutes, and seconds, then start. The last used duration is remembered, the running action becomes Cancel, and the standard app sound plays at zero.
Pomodoro uses fixed 25-minute work periods and 5-minute rests. Each transition plays the standard sound and the next period starts automatically until you cancel.
Local App Behavior
The core timing workflow works on-device without accounts, analytics, cloud sync, or a required network connection.
The first bottom row uses larger buttons for Alarm, Stopwatch, Countdown, and Pomodoro. A smaller second row keeps Settings and Support available without crowding the timer tools.
Settings stay consistent with other NoBS apps: language and theme options apply immediately and remain local to the device.
Alarms, countdowns, and pomodoro transitions use local system alerts where the platform allows them. Permission is requested only when a timing feature needs it.
NoBS Timers uses one standardized alert sound across alarm, countdown, work completion, and rest completion. There is no sound picker.
Privacy Policy
Privacy details are published in the standalone policy page: