Public Roadmap
Direction without false promises
Each phase contains objectives you can open for details. Dates appear only when staffing, scope, budget, and dependencies support them.
What the status labels mean
- Live
- Available on production and linked to release evidence.
- Up next
- Accepted, scoped, and scheduled for the active delivery window.
- Planned
- Accepted direction without a committed date.
- Exploring
- A problem and possible value under discovery, not a promise.
- Later
- Intentionally outside the current phases.
- Released
- Historical work linked to the release archive.
Product phase
Phase 1
Up next · R14-TRANSPARENCYA clearer closed-alpha home
- Problem
- Members need one reliable place to understand the product and its progress.
- Who benefits
- Visitors, members, and prospective contributors
- Scope
- About, Help, Roadmap, Contact & Trust, feedback, release notes, and role guides.
What would help you understand GoJumpingJack more quickly?
Make a suggestionUp next · R14-EVENT-DISCOVERYEvents as a first-class city experience
- Problem
- Useful events are difficult to discover when they are mixed into place lists.
- Who benefits
- Residents, daydreamers, and travelers
- Scope
- A dedicated Events tab with bounded dates, accessible list/calendar/map views, saves, and calendar downloads.
Which event filter helps you decide what to do first?
Make a suggestionUp next · R14-EXTERNAL-SHARINGSafer external sharing
- Problem
- Members should not have to retype provider-owned titles and author details.
- Who benefits
- Contributors and reviewers
- Scope
- Provider-aware URL preview, canonicalization, duplicate checks, relationship disclosure, and safe fallbacks.
Which supported source would make sharing local finds easier?
Make a suggestionProduct phase
Phase 2
Planned · P2-RECOGNITIONAchievements, badges, and city leaderboards
- Problem
- Useful local work deserves visible recognition before monetary rewards exist.
- Who benefits
- Contributors and emerging city communities
- Scope
- Quality-weighted achievements, category expertise, seasonal leaderboards, anti-gaming controls, and community spotlights.
Which recognition would feel meaningful without rewarding spam?
Make a suggestionExploring · P2-DISCOVERY-FEEDRicher social discovery
- Problem
- A single-column feed does not always show the range of useful city content well.
- Who benefits
- Members who browse frequently
- Scope
- Accessible mosaic layouts, user follows, topic collections, and community spotlights after feed-density testing.
Do you prefer a calm timeline or a denser mosaic for discovery?
Make a suggestionPlanned · P2-TRIP-INTELLIGENCEFrom saves to suggested itineraries
- Problem
- Saved discoveries still require people to assemble a practical trip manually.
- Who benefits
- Travel planners and daydreamers
- Scope
- Trip intent, dates, party needs, budgets, pace, constraints, explainable suggestions, and editable itineraries.
What should an itinerary always ask before suggesting a day?
Make a suggestionProduct phase
Phase 3
Exploring · P3-SUSTAINABILITYSustainable community revenue
- Problem
- The service needs revenue without corrupting organic local knowledge.
- Who benefits
- The whole community
- Scope
- Clearly labelled sponsorships, affiliate experiments, creator products, and merchant tools with ranking separation.
Which revenue model would feel least intrusive and most transparent?
Make a suggestionLater · P3-TRAVEL-CONVERSIONTravel search and booking
- Problem
- Inspiration and planning eventually need a trustworthy path to purchase.
- Who benefits
- Travelers with a completed plan
- Scope
- Search, offer revalidation, payments, servicing, refunds, fraud controls, and support only after operational gates pass.
Where would you want a handoff from planning to booking?
Make a suggestionReleased work
Protected maintenance and release health
Release notes, protected maintenance, liveness/readiness, worker receipts, and an attended production rehearsal.
Release 1.3.5