ProjectCase Study

Wild Route

A prompt-first adventure travel planner that turns a rough trip idea into ranked, shareable multi-stop routes with reasoning and external booking handoffs.

Date

2026

Category

Travel product + full stack

Key skills

Next.jsSupabaseStripeVitest
Wild Route editorial landing page
01Product direction

Travel planning with a point of view.

Most itinerary tools start with a form or a list of destinations. Wild Route starts with intent: the pace, climate, detours, budget, and activities that make a trip worth taking.

I designed the product around fewer, better-considered choices. The visual language is editorial and cinematic, while the planner stays explicit about route logic, estimates, persistence, and external booking handoffs.

04ranked route studies

Each brief resolves into a considered set instead of an endless result list.

25free generations

Plan limits are defined server-side and stay visible in the product model.

12saved routes

The free tier supports durable route saves before deeper provider integrations.

02Route Composition

A calm interface for a dense decision.

The current build uses a transparent scoring engine behind the prompt-first experience. That keeps the interaction explainable and gives the product a reliable spine before live provider or model-backed enrichment.

Wild Route selected-route planner with ranking reasons and estimate boundary
01

Interpret the brief

The planner extracts the origin, travel window, stop count, budget mode, and active wishes from the prompt and form controls.

02

Score destinations

Destinations are ranked against the selected wishes, activity profile, cost posture, and route constraints.

03

Compare route shapes

The interface keeps four recommendations in view, then opens the selected path with ranking reasons, estimate boundaries, and handoff actions.

03Production Stack

Designed past the mockup.

The product is wired as a production-style Next.js application: identity, private data, public sharing, billing, and operational endpoints are part of the system. Deterministic route generation, tests, and explicit fallback behavior keep the demo reviewable.

Planning surface

Prompt-first route composition, globe or 2D fallback comparison, destination reasoning, and provider handoffs.

Account data

Supabase Auth, Postgres, and row-level security for profiles, generations, saved routes, public shares, and handoff history.

Managed billing

Stripe Checkout, billing portal access, and webhook-driven entitlement syncing for free and pro limits.

Durable route lifecycle

Private saves, public share links, account export, deletion controls, and notification-ready delivery paths.

One product, end to end.

Wild Route is a current portfolio piece because it reflects the work I want to keep doing: shaping a distinct product idea, building the interface carefully, and carrying the system through save, share, handoff, account, and billing flows.

Explore the code
MoreSelected Work