Image and video decision

Arc Raiders Map

A competent developer can reproduce the core interactive-map, marker and event features using open mapping libraries, but full parity with the App Store app’s polish, performance optimizations and App Store presence is a multi-week effort and therefore only a partial DIY replacement is realistic.

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-off120 h to build

$20/mo4 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

  • Browse interactive tiled map → filter/search markers → open marker details (loot/enemy/quest) → track events/timers → optionally compare weapons/loadouts.

What it still won’t have

  • App Store distribution history, reviews and discoverability
  • The developer’s polished rendering and performance optimizations (e.g. 60fps with 1,000+ markers)
  • Ongoing small UX fixes and incremental content updates handled by the original developer

What remains hard

  • Execution qualitybuttery-smooth rendering, even with 1,000+ markers on screen.
  • Execution qualityTiled interactive maps: Riven Tides now renders in high detail at every zoom level
Read the build prompt

First-year cost

No published price

Arc Raiders Map 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 companion app in SwiftUI + MapLibre GL (or Mapbox SDK) with a small Node/Express or Supabase backend for hosting marker and event data. In-scope: 1) tile-serving via S3+CloudFront (or Mapbox/MapTiler), 2) client tiled map rendering with marker clustering, category filters and full-text marker search, 3) local JSON-backed enemy/loot/weapon databases with comparison UI and skill-tree planner, 4) event scheduling and local push notifications (APNs) with countdowns, 5) StoreKit in-app purchase and restore flows, and 6) basic CI, error handling and unit/UI tests. Out of scope: large-scale analytics, multiplayer sync, training ML models, and App Store submission negotiation. Provide thorough error handling for network and purchase failures and include automated unit tests for data parsing and UI snapshot tests for core screens.
How we checked2 sources · 2/3 runs agreed · evidence score 53

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Evidence score53

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! 2 moats quoted from the page