Shipped Product

An AI Journey Planner App

Roles
Product Design & Development
Marketing
Tech
Client side: Vue, Capacitor, Swift
Backend: FastAPI, Supabase, Resend
Timeframe
May 2026, San Francisco and Tokyo
Founder @ Deejiar
Deejiar on the App Store — "Deejiar: AI Trip Planner", Curated spots & what to order

The best journeys aren't planned. They're inherited.

Inherit, don’t generate

Taste can’t be generated. A local’s day is already proven — the model’s job is fitting it to you.

Deejiar empowers travelers to share the taste from real local tour’s journey

A generated itinerary is a guess; an inherited one is proof. Verified locals publish the days they actually live — you take one whole, then adjust it stop by stop until it’s yours.

How to guide people with micro interactions

Inheriting a day works once you know where you’re going, so planning your own has to be easy to begin. Nobody reads instructions on a phone, so the guidance lives in motion: the one action that matters moves until it’s taken, and every step answers back, so the next one is obvious.

Show the next step, then answer it.

On an empty Journey tab, one tile moves. Every three seconds its plus hops and flips a half turn while the dashed border runs clockwise, so the eye lands on the one action that matters. Tap it, and a new journey asks for a name and the dates. The title rolls to each day you pick and the month flips over, so the trip reads back to you as you choose. Confirm, and it already has a name and a span: the next step is filling it in, not starting it.

Operating model

Every generation drifts. So judgment sits at both ends and never in the middle: /plan defines intent from zero, /build executes the approved plan and may only stop and ask, /inspect checks what actually came out. Red-teaming lives in /inspect, not /plan — attacking a plan is speculation about speculation; attacking an audit is verification.

Feature build flow:

Defines intent. Writes no code.

Commands that support the build

Cuts a file to its smallest, highest-signal form — zero information loss.

Twelve releases in four months, v0.02.0 to v0.03.1 — nearly 2,000 commits.

Designing and building it myself is what makes that pace possible. There is no handoff, so the distance between deciding something and shipping it is an afternoon.

GitHub release notes for v0.03.1 — self-planned trips, open messaging, themed collections: the release that retires the guide model, 668 commits

Where It Goes Next

Tokyo and Taipei today, with more of Asia rolling out. Guides join city by city, and when a guide covers your city, booking a private tour is one tap from the journey you already inherited. The harder problem stays the same: the more the model does for you, the more it has to be right about.

A boat crossing turquoise water, overlaid with the line: the best journeys aren't planned, they're inherited