Learning and careers decision

Tariq

A minimal, useful Tariq replacement (local reader + prayer times + Qibla + subscription) is realistic for one capable developer to build and maintain; no durable moats in the supplied pages prevent self-hosting.

View on the App Store
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-off36 h to build

$0/mo3 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 Tariq alternatives, with the arithmetic →

What a replacement has to do

  • Open app → read verse with translation/tafsir → save/bookmark verse → view prayer times and Qibla → resume reading

What it still won’t have

  • Polish, accessibility and multi-language editorial quality in the shipped UX
  • App Store presence history, ratings, and any proprietary content curation
  • Any cloud-based sync or cross-device account features (if present)
  • Ongoing marketing, analytics configuration, and frequent feature cadence

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Tariq 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 native iOS Quran companion app (Swift + SwiftUI) with a local SQLite store for Quran text, translations and tafsir, StoreKit subscription support, geolocation-based prayer time calculations and Qibla direction using CoreLocation and CoreMotion. In scope: import JSON/SQLite Quran corpus, verse-by-verse reader UI (RTL support), search, bookmarks/favorites, local notifications for prayer reminders, Qibla compass screen, subscription gating for premium content, settings (language, theme), error handling, unit tests for core logic (prayer calc, StoreKit entitlements) and end-to-end UI tests. Out of scope: cloud sync, social sharing, server-side components. Include offline-first behavior, graceful sensor permission handling, analytics opt-out, and CI to run tests.
How we checked4 sources · 2/3 runs agreed · evidence score 86

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 4 cited sources+3
  • Evidence score86

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded