Health, home and travel decision

UV Tan

A technically capable developer can build a narrow, working UV-tracking app (location + UV API + notifications) within a few weeks, but reproducing the polished cross-platform product, distribution, and any vendor-collected data/scale is substantial work and not fully covered by a minimal replacement.

Visit website

Built by Emmett Deen, who ships 3 products in this index

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

$100one-off120 h to build

$30/mo6 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Get user's location → fetch local UV index from a weather/UV API → evaluate against stored skin profile → schedule/send push notifications and show in-app recommendations.

What it still won’t have

  • Polished native UX and cross-platform edge-case polish
  • App store optimization, review, and distribution support
  • Scale, analytics, and monitoring built by the vendor
  • Marketing, brand recognition, and any proprietary dataset the vendor may collect

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

UV Tan 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 minimal cross-platform mobile app (React Native or Flutter) that: 1) captures and stores a simple skin profile in local storage or Firebase; 2) obtains device location with permission handling; 3) queries a public UV/weather API for current UV index for the user's location; 4) computes simple recommendations (e.g., SPF needed, reapply interval) from profile + UV value; 5) displays current UV and recommendations in a simple UI and allows profile edits; 6) schedules background checks and sends push notifications via FCM/APNs (or a push provider). Out of scope: marketing, analytics dashboards, enterprise features, offline-first sync. Include error handling for denied permissions and API failures, unit tests for recommendation logic, and end-to-end test for the main flow.
How we checked1 sources · 3/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 3/3 assessment runs agreed+4
  • Evidence score56

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 · 1

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