Skip to content

v1 flow and deadline

v1 is complete when a group leader can do everything below, on stage, by Sunday 15 November 2026 (founder, 26 Oct 2026, decision P53). Things may change on the way; new items go through Prakash.

Date Milestone What it means
Sun 15 Nov 2026 v1 complete The whole flow below works end to end on stage
Sun 22 Nov 2026 v1 live On production; Prakash walks through it as a leader

The flow

flowchart TD
  A[Leader opens NepWalk<br>landing page] --> B[Signs up or signs in]
  B --> C[Picks a Paila and makes the trip<br>dates and exact group size]
  C --> D[Accepts NepWalk's vendor picks<br>or chooses others]
  D --> E[Admin is notified<br>in the app and on WhatsApp]
  E --> F[Admin sees the trip in full detail<br>arranges the logistics]
  F --> G[Admin marks each service confirmed]
  G --> H[Leader sees what is confirmed]
  C --> I[Leader invites members<br>any time, even before confirmation]
  C --> J[Leader updates the itinerary<br>any time]
  I --> K[Members read the trip day by day<br>today's plan opens offline]
  1. Find NepWalk. The landing page explains NepWalk; Plan your trip opens the Pailas. Help page for questions.
  2. Account. Sign up or sign in with Google or email (email verification).
  3. Make the trip. Pick a Paila, set the dates and the exact number of people.
  4. Services. Accept NepWalk's hotel, vehicle, flight and guide picks with one OK, or choose others from the verified list.
  5. Admin notice. The admin portal shows the new choice; the founder also gets a WhatsApp message (how: O24).
  6. Admin portal. Every trip in full detail: group, days, services, vendors, members. The admin arranges the logistics outside the app and marks each service confirmed.
  7. Leader sees confirmations on the trip as they come in.
  8. Members. The leader invites members at any time, before or after confirmation.
  9. Changes. The leader can still update the itinerary.
  10. Travellers. Members read the trip day by day; today's plan opens without a connection.

Features

# Feature In v1
0 Landing page Yes (approved)
1 Accounts, joining a trip, help Yes
2 Planner: trip from a Paila Yes
3 Trip day plan Yes
4 Plan editor Yes
5 Services and vendors Yes
6 Trip settings: group size Yes
7 Shared trip and traveller view, offline day Yes
8 Place library Place data yes (Kathmandu, Pokhara, Chitwan, Bhaktapur, Patan, Nagarkot); page redesign later
9 My trips Yes; My Pailas only at the end, if time allows
10 Admin portal: trips, notices, confirmations Yes
11 Help, offline day, install as an app Help and offline yes; install later

Feature cards: features/README.md.

If time runs short, Prakash cuts in this order: plan editor design changes, then day plan design changes, then joining by link.

Places and Pailas

Niwesh researches popular Nepal itineraries and adds the places and Pailas they need as seed data in nepwalk-be, working locally with AI, by pull request. Prakash reviews, merges and migrates them to production.