Health, home and travel decision

Ezan Vakti

A small technical team or capable individual can reproduce the core functionality (times, offline, alarms, qibla) in about a week using existing open source libraries; the vendor advantages are polish and extras rather than durable moats.

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

$50one-off28 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 Ezan Vakti alternatives, with the arithmetic →

What a replacement has to do

  • Show local prayer times for the user’s location, schedule local notifications/azan alarms, allow offline access to the next 30 days of times, and provide a qibla compass.

What it still won’t have

  • Polish of a mature App Store product (UX/UI, edge-case bug fixes, localized copy)
  • Built-in Apple Watch complications and deep watch integrations
  • Pro subscription management and analytics dashboards
  • Branded content bundles (Ramadan packs, curated hadith/corpus) and editorial updates
  • In‑app ad/subscription flows tuned for App Store revenue

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Ezan Vakti 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 iOS Swift/SwiftUI app (Xcode 15+) that: (1) uses the azan-mcp library for prayer time calculations; (2) stores 30 days of calculated times in Core Data or SQLite for offline access; (3) schedules local UNUserNotificationCenter notifications for each prayer with configurable pre‑reminders and azan sound; (4) implements a qibla compass using CoreLocation and CoreMotion and a map confirmation using MapKit; (5) provides screens for settings (calculation method, city override, location toggle) and a main view showing today’s times and next‑time countdown. Out of scope: Apple Watch complications, in‑app purchases/subscription backend, analytics dashboard. Include error handling for permission denial, timezone and DST changes, and unit tests for time calculation integration and notification scheduling.
How we checked2 sources · 2/3 runs agreed · evidence score 84

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 2 cited sources+1
  • Evidence score84

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

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