--- title: "Five Tabs, One AI: Structuring a Chat-First App" description: "Chat is the core. Tools, Trips, Passport, and Profile are escape hatches for when users need structured views — but every tab knows the conversation is home base." canonical: https://nowah.xyz/blog/five-tabs-one-ai-structuring-chat-first lastModified: "2026-08-07T08:01:19.133Z" --- # Five Tabs, One AI: Structuring a Chat-First App Chat is the core. Tools, Trips, Passport, and Profile are escape hatches for when users need structured views — but every tab knows the conversation is home base. A chat-first app faces a structural paradox. The conversation can theoretically handle everything — search, booking, management, configuration. So why have tabs at all? Why not just a single chat screen? Because humans need escape velocity from conversation. Sometimes you want to scan a list of trips, not describe them in words. Sometimes you want to tap a currency converter, not ask the AI to do math. Sometimes you want to adjust a setting in a form, not explain what you want changed. The five tabs exist not because the chat cannot do these things but because structured views are sometimes better. The art is designing tabs that complement conversation without competing with it. ## Tab 1 — Tools: what does not need AI ![Illustration for this section](https://pics.nowah.xyz/website-media/design-035-img-1.webp) The Tools tab houses three utilities: currency converter, tip calculator, and bill splitter. These are purely computational tools with deterministic outputs. You input a number, you get a result. There is no ambiguity for an AI to resolve, no preferences to consider, no follow-up questions to ask. Putting these in a tab rather than in the chat has two advantages. First, speed. The tools produce instant results with zero network latency. A [currency conversion](/blog/launching-currency-conversion-global-travelers) in the chat would work — the AI could convert currencies — but it would take several seconds for the message to process, stream, and render. The standalone tool takes milliseconds. Second, repeated use. During a trip, a traveler might check currency conversions dozens of times per day. Opening a conversation for each check would clutter the chat with trivial messages. The standalone tool is a quick in-and-out interaction that leaves no trace in the conversation history. The principle: if it does not benefit from AI reasoning and it is used frequently, it belongs in a tool, not in the chat. ## Tab 2 — Trips: structured views of conversational outputs The Trips tab is where the conversation's outputs live in organized form. After booking through chat, the trip appears here as a structured detail view with tabs for Overview, Flights, Hotels, and Documents. This tab exists because structured data is sometimes easier to consume visually than conversationally. Asking the AI "When does my Tokyo flight land?" works, but scanning a flight card in the Trips tab is faster when you just want a quick answer. The structured view is optimized for information retrieval — finding specific data points quickly. The Trips tab also serves a management purpose. Sorting trips by date, filtering upcoming versus past trips, and viewing a chronological timeline of travel segments are all visual operations that benefit from a list/grid layout more than a conversation. The connection to chat is bidirectional. Every trip view includes a "Chat about this trip" action. Every chat booking includes a "View your trip" link. The user flows between conversation (for complex queries and modifications) and structured views (for quick reference) as needed. ## Tab 3 — Chat: the hero ![Supporting diagram](https://pics.nowah.xyz/website-media/design-035-img-2.webp) The center tab. The AI conversation. The reason the product exists. In a chat-first app, the chat tab has a unique property: it is the only tab where the user can initiate any action the product supports. [Search flights](/blog/launching-[tool-calling](/blog/tool-calling-at-scale-ai-travel-search)-layer-ai-agent-search-flights), book hotels, check weather, look up [visa requirements](/blog/ai-agents-visa-requirements-documents), cancel bookings, modify trips — everything starts here. This makes the chat tab the default. When the user opens the app with no specific task, they land on chat. When they are unsure which tab has what they need, they go to chat. When they want to do something they have never done before in the app, they ask the chat. The other tabs handle specific, well-defined tasks. The chat handles everything, including the tasks the designer did not anticipate. This asymmetry — one general-purpose tab surrounded by four specific-purpose tabs — is the structural foundation of the app. ## Tab 4 — Passport: the travel journal The Passport tab houses the user's travel journal and document storage. It is a personal space for travel memories, document archives, and a record of places visited. This tab fills a gap that the chat cannot. Conversations are ephemeral — they scroll up and out of view. Documents generated during conversations ([boarding passes](/blog/launching-document-management-boarding-passes), confirmations) need a permanent, organized home. The Passport tab provides that permanence. The journal aspect adds an emotional dimension. A list of countries visited, a collection of trip photos, a timeline of travel history — these are not transactional features. They are personal features that give the user a sense of their travel identity. The chat is about the future (planning trips). The Passport is about the past (remembering them). ## Tab 5 — Profile: configuration and control The Profile tab contains settings, preferences, account management, and the preference transparency dashboard. It is the least frequently accessed tab, matching its position at the far right edge. In an AI product, the Profile tab has additional importance. This is where the user sees what the AI knows about them, edits stored preferences, manages notification settings, and controls privacy options. The preference dashboard — showing seat preference, dietary needs, home airport, travel style — is the user's window into the AI's memory. The Profile tab is also where trust infrastructure lives. Security settings (sessions, devices), privacy controls (data export, account deletion), and connected services are accessible here. These features may be rarely used, but their existence communicates that the product takes user control seriously. ## Designing tab responsibilities The key design principle: each tab has a clear, non-overlapping responsibility. Tools does computation. Trips does management. Chat does everything else. Passport does memory. Profile does configuration. When a new feature is proposed, the first question is: does this belong in a conversation or in a structured view? If the feature benefits from AI reasoning, context accumulation, or natural language interaction, it belongs in chat. If it benefits from visual organization, quick reference, or offline capability, it belongs in a tab. Tab transitions use a 150-millisecond cross-fade that feels instant without being jarring. The transition speed communicates that moving between tabs is a lightweight action, not a navigation event. The user should feel like they are pivoting within one product, not switching between five mini-apps. Five tabs is enough structure to organize a complex travel product. More would dilute each tab's purpose. Fewer would overload the remaining tabs. Five hits the sweet spot where every tab is necessary and none is redundant. One AI at the center. Four structured views at the edges. Five tabs, one product. --- Nowah is an AI travel agent that searches and books real flights and hotels through conversation — no filters, no thirty open tabs. [Plan your next trip](https://app.nowah.xyz).