Trip coordination
Trips, members, phantom participants, invites, and per-trip settings all live in one mobile-first browser flow.
Web-first, mobile next
TravelBTW now ships as a mobile-first web app before it becomes a packaged mobile product.
The browser is the fastest place to finish the real product. Once the flows are stable here, the mobile shell becomes an execution detail instead of a blocker.
Current focus
Finish the product surface in the browser
- Create and edit trips in the browser first
- Manage members, invitations, and phantom participants
- Add expenses, sync drafts offline, and settle up
Expense engine
Flexible splits, currency conversion, offline draft queue, settlement, and exports are ready to move faster on the web.
Native later
The browser product is now the proving ground, so the eventual mobile app inherits stable flows instead of half-tested ideas.