Product Vision
Why Treeper exists
Section titled “Why Treeper exists”People plan their own trips across notes apps, screenshots, group chats, and inboxes — and the plan goes stale the moment they board the plane. Travellers also keep asking the internet two questions that nobody answers well: “who wants to come with me?” and “who’s a guide I can actually trust?”.
Treeper is a single mobile app that:
- Plans — turns ideas (yours, or a reel you forwarded) into a real itinerary you can edit.
- Tracks — works on the trip, offline, with photos and notes per stop.
- Connects — finds people going the same place at the same time, and verified guides / packages when you want them.
Beliefs
Section titled “Beliefs”- Mobile-first. Travel happens on phones; the planner has to live there.
- Local-first. Trips must be fully usable offline once opened.
- AI as a power-tool, not a chatbot. Forward a reel, get a draft. Don’t pretend to be a travel concierge.
- Verified > infinite. Better to ship 200 trustworthy guides than scrape 20,000 and ship them all.
- Specs over PRDs. Short, testable, in-repo. See SDD process.
Non-goals
Section titled “Non-goals”- Replacing booking sites. We link out for hotels and flights at v0.
- Becoming a social network. Communities are a means to an end.
- Web / desktop apps in the first release.
How we’ll know it’s working
Section titled “How we’ll know it’s working”| Signal | Target |
|---|---|
| Time from app open to first activity | < 60s for a returning user |
| % of trips opened during travel | > 60% of created trips |
| AI-ingested URLs per active user / mo | > 3 |
| Trips with at least one co-traveller | > 30% by month 6 of v1 |
| Marketplace items rated 4★+ | > 80% of attached items |
These are aspirational; each gets a real metric and dashboard once the related feature ships.
The full feature brief
Section titled “The full feature brief”See PRODUCT.md. This file stays short on purpose.