ATTRACTIONS
Social routes

Routes are now first-class social objects

People should be able to discover, save, repeat and share routes directly from the feed. That applies to city walks, food paths, event chains and marine transitions.

Visible in feed
Yes
Routes should surface from the main home stream.
Use cases
4+
City, food, event and marine route formats.
Monetization
Strong
Tours, guides, tickets and affiliates can attach later.
Community fit
High
Routes naturally generate comments, joins and saves.
Featured route ideas
Feed-ready route formats that can later become share cards and landing pages.
Feed-ready
City
2.6 km · Evening · Riga
Old Riga → Riverside sunset route
A compact city route with photo points, coffee pause, bridge views and a soft sunset finish.
Photo spotsCoffeeWalkableFeed-worthy
Food
4 stops · Weekend
Local food crawl with hidden picks
A route that can evolve into a bookable experience, a local guide product or a community event.
FoodLocal expertBooking-ready
Marine
Draft concept · Social crew
Weekend marina hopping starter route
A marine route can begin as a social idea, then develop into crew finding, marina planning and booking.
MarineCrewOvernightExpansion path
Route architecture for your platform
Routes should exist as sharable cards
Each route needs a strong card identity with title, area, duration, tags, preview map and social metrics.
Routes must bridge City and Marine
Do not isolate them. A route engine should support both land and marine experiences under one product logic.
Routes are ideal monetization anchors
Affiliate hotels, local tours, marina services, guide offers and transport can attach to route pages naturally.
Where routes should connect next