Nepscape

Travelers and trekking guides mostly found each other through social media and phone calls. Trail details, who was guiding, and whether they were free lived in different chats.

Starting a trek meant searching social media, finding a guide separately, and then calling them. There was no single place for the map, the trail, and the guide.

We built Nepscape as a mobile app for Android and iOS, with the web alongside it, and a separate admin panel. The app opens on a map. Zoomed out, trails show as pins. Zoomed in, the route line appears. Opening a trail shows duration, distance, altitude, difficulty, season, permits, and the guides linked to that route.

People can browse without an account. Saving a trail, saving a guide, checking availability, and contacting a guide ask them to sign in. Travelers can register with email or Google.

Guides can register, but they stay hidden from travelers until an admin approves them. That review happens in the admin panel.

Booking and payments are outside this version. Offline maps are not in the app yet. The pilot catalog currently holds 9 trekking trails, and no guides are in that pilot data yet.

Next.js runs the web app. Flutter runs the Android and iOS apps from one codebase. MapLibre draws the trails. GalliMaps handles place search in Nepal, next to Nepscape's own trail list. Node.js and MongoDB run the API behind the app and the admin panel.

Nepscape gives travelers one path from a map to a trail to a guide, in place of a search across social media and phone calls. A guide reaches travelers only after approval.

The pilot lists 9 trekking trails. Guide profiles are added through that approval step.