A deterministic trip builder
The roadmap defines a rules-based engine that composes the itinerary, map pins, budget, packing list, and checklist. Core planning does not depend on a language model guessing the structure.
aiqorxCities Unveiled / Architecture & product design preview
An editorial travel platform that turns an expert-curated guide into a personal trip, connecting the itinerary, map, budget, packing, and memories in one place.

01 / The brief
Buy a city guide and begin with a trip that is already organized. Cities Unveiled connects expert editorial content to a practical travel workspace: days, places, spending, packing, documents, and a companion that can refer back to the guide.
The roadmap specifies React Native and Expo for the mobile apps, with Next.js for the web companion. A single editorial source feeds the guide, downloadable material, and retrieval system. The new identity pairs a portal-shaped monogram with cobalt and terracotta, balancing travel inspiration with useful detail.
02 / The challenge
Travelers collect guides, saved places, tickets, and notes across different tools. Turning that research into an actual day in a city takes work. The product needs to bridge inspiration and practical preparation while staying useful without a connection.
03 / The experience
Discover a guide on the web, shape the trip on your phone, and carry useful details into the city. The roadmap connects planning, offline access, and travel memories.
Browse an editorial guide and purchase through the appropriate web or mobile payment flow.
A short setup captures travel dates and preferences before the guide becomes an itinerary.
Keep places, budget, packing, and permitted offline content close at hand.
Collect journal entries and photos, then return to a trip recap after coming home.

04 / Under the surface
The roadmap defines a rules-based engine that composes the itinerary, map pins, budget, packing list, and checklist. Core planning does not depend on a language model guessing the structure.
Sanity supplies canonical guide content. The planned publishing pipeline derives in-app guides, PDFs, and retrieval chunks from the same versioned material.
A bounded Claude-based concierge is planned to retrieve relevant passages from the purchased guide. Source context, refusals, and evaluation are part of the architecture.
Purchased guide content and permitted map regions are designed for download. Offline status and synchronization should be visible before the traveler needs them.
The roadmap proposes client-side document encryption, controlled key access, and a later collaboration phase. These require implementation and security verification before release.
The hero purchase-to-trip flow precedes the wider feature set. Concierge, subscriptions, collaborative trips, and future marketplace ideas are separate delivery stages, not claims of completed features.
05 / Technology
Each part of the stack has a job. These are the proposed technologies in the project architecture.
Primary iOS and Android codebase, native integrations, and mobile delivery.
Web discovery, checkout, and administration companion.
Planned accounts, relational data, storage, realtime events, and vector retrieval.
Editorial source for city guides and place information.
Planned map presentation and permitted offline regions.
Web checkout and mobile purchase entitlement handling.
Guide-grounded concierge and bounded writing assistance.
Planned error visibility and consent-aware product measurement.
Technology choices reflect the supplied roadmap. Product visuals are design concepts; roadmap targets and future phases are not presented as shipped outcomes.
06 / The result
A detailed technical roadmap defines the path from a focused guide-to-trip experience to a broader travel companion. This case study presents that architecture and a proposed visual direction. Release dates, adoption, performance targets, and commercial results remain to be validated.
Something in mind?
Let's build