Health, home and travel decision
SkiMap
A competent technical user can build a useful offline map + tracking app using existing mapping SDKs and the cited open-source projects for offline maps and track recording; full polish and scale are costly but core functionality is realistic to replace.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off92 h to build
$100/mo6 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 SkiMap alternatives, with the arithmetic →
What a replacement has to do
- Download and cache offline map data for resorts, record GPS tracks while skiing, render 3D map view with runs overlaid, show per-day stats (speed, vertical, distance), and optionally broadcast/receive live friend locations and rankings.
What it still won’t have
- Polished cross-platform UX and app-store-grade polish
- Curated resort metadata and manually tuned 3D visuals
- Scale, monitoring, and operational reliability provided by a dedicated team
- Existing user reviews, brand trust, and social features maturity
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
SkiMap 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
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
Build a cross-platform mobile app (React Native) with a small Node.js/Express backend. In scope: (1) offline map tile/vector download and cache per resort (store tiles in app filesystem), (2) 3D-capable map view using Mapbox GL or an open-source WebGL mapping lib, (3) GPS track recording to local SQLite and upload sync, (4) per-session stat computation (max speed, distance, vertical) and day-summary UI, (5) a lightweight realtime endpoint (WebSocket or Firebase) for optional friend-location sharing and rankings, (6) background location handling, error handling for offline/restore cases, and unit/integration tests for tracking, caching, and sync flows. Out of scope: map tile creation pipelines, curated resort content import tools, app-store release automation, and advanced terrain-authoring. Include automated tests, telemetry for errors, and documented deployment steps for backend (Docker + small VPS).
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
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 · 3
Every page the run actually retrieved.
- official productSkiMap – Offline Ski Maps, 3D Resorts & Live Tracking
- open sourceorganicmaps/organicmaps
- open sourceFASTSHIFT/X-TRACK
Integrity checks
What held up, and what did not.
