Health, home and travel decision

Unpopular Opinion

A competent developer can build the core swipe-vote+stats experience and ship a small replacement, but you would lose the packaged App Store presence, existing curated content, and polish—so rebuilding is realistic for a narrow replacement, not a full commercial clone.

View on the App Store
You pay

$8.99/mo

$108/yr

Read off the official pricing page.

You’d pay instead

$100one-off60 h to build

$0/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 1 seat.

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

  • Show an opinion card -> player swipes agree/disagree -> record vote -> calculate and display whether opinion is POPULAR or UNPOPULAR and per-player stats.

What it still won’t have

  • App Store listing, ratings, and existing userbase
  • Curated set of +1500 original opinion cards
  • Polish and platform-specific QA across iPhone/iPad/Apple Vision
  • Integrated App Store subscription handling and review history

What remains hard

  • Content rightsTons of opinions: +1500 original opinions for hours of gameplay
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

Paid seatsseats

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 cross-platform mobile app in React Native (Expo optional) with a SQLite-backed seed of ~1500 opinion cards, a swipeable card UI, player-name/session selection, vote recording, simple aggregate stats (percentages, popular/unpopular determination), local persistence and export, and App Store IAP subscription integration. Out of scope: social multiplayer networking, leaderboard servers, analytics dashboards. Include error handling, unit tests for vote/stat logic, and end-to-end smoke tests for the main flows.
How we checked1 sources · 2/3 runs agreed · evidence score 20

How the score was reached

  • Pay verdict base20
  • Price verified on pricing page+3
  • Hard moats found in the evidence-3
  • Evidence score20

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.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat quoted from the page