Health, home and travel decision

Stoppuhr-timer

A competent developer can reproduce the core browser stopwatch/timer/countdown feature set in about a week as a static web app; the paid site mainly provides hosted convenience and brand polish.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$50one-off22 h to build

$0/mo1 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Stoppuhr-timer alternatives, with the arithmetic →

What a replacement has to do

  • Open a webpage, start/stop a timer or countdown, optionally record laps/presets, and hear an alarm when time elapses.

What it still won’t have

  • Hosted brand, domain and fixed public traffic handling
  • Built-in analytics, telemetry, or multi-device sync for users
  • SEO, blog and site-wide pages maintained by the vendor
  • Polish from continuous A/B testing and large-user accessibility fixes

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Stoppuhr-timer does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a single-page responsive stopwatch/timer/countdown app using plain HTML, CSS and vanilla TypeScript (or React) served as static files (Netlify/Vercel). In scope: a Stoppuhr (start/stop/pause, lap times, best-lap highlight, hundredths), a Timer (set duration, extend without restarting, four selectable alarm tones), a Countdown (set event date/time, ready-made holiday presets, checkpoints), fullscreen mode, localStorage for presets/settings, selectable alarm audio via Web Audio API, keyboard accessibility, and unit tests for timing logic. Out of scope: multi-user sync, server-side analytics, paid account features, invoicing. Include error handling for audio loading failures, cross-tab consistency (if open in multiple tabs), basic accessibility attributes, and automated tests for core timing behaviors.
How we checked3 sources · 3/3 runs agreed · evidence score 90

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 3 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score90

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded