TravelAssistant
README.md
Travel Assistant
A travel app: a trip plan that works offline, and a language model that helps you put together and adjust that plan on the go.
The successor to BeijingTrip—an app originally built for a single trip to Beijing for four people. Everything was hard-coded into the APK: one city, one language, one time zone, one reservation. Here, it’s the same concept, but for any trip, any language, and any number of travelers.
Status: skeleton. The build, navigation, database, theme, and module framework are working; sections are being filled in according to docs/ROADMAP.md.
Build and run
./gradlew :app:assembleDebug
android run --apks app/build/outputs/apk/debug/app-debug.apk
the emulator, if you don’t have it yet:
android emulator list
android emulator start <avd>
Tests:
./gradlew test testDebugUnitTest
What’s already available
| Build | AGP 9.4, Gradle 9.8, Kotlin 2.4, 17 modules, conventions in build-logic |
| Theme | Material 3 Expressive, colors based on the user’s wallpaper, spring animation |
| Navigation | Navigation 3, floating navigation bar instead of one pinned to the bottom |
| Data | Room with a layout ready for synchronization; DataStore for settings |
| Models | LlmProvider + Gemini Nano on the device; Markdown format for sharing the plan |
| Itineraries | Catalog of pre-made itineraries; sample “Beijing in Six Days” itinerary—54 stages |
| Camera | Screen in CameraX Compose; recognition packages are downloaded by region |
| Tips | Custom component on top of M3: cutout-based dim, screen rotation |
| Tests | 30 tests, including protecting the demo route from personal data leaks |
Docs
- docs/STACK.md — libraries, versions, and why they were chosen
- docs/ARCHITECTURE.md — modules, data flows, synchronization scheme
- docs/DESIGN.md — interface guidelines: Expressive, floating elements, chips
- docs/AI.md — models, plan exchange, AppFunctions, A2UI, ADK
- docs/SHARING.md — predefined routes and why personal data cannot be included in them
- docs/VISION.md — photo reports, recognition, and region packages
- docs/ROADMAP.md — development phases and tasks for agents
- docs/TOOLING.md — tools, CLI, skills, and MCP
- CLAUDE.md — how to work as an agent in this repository
The System in a Nutshell
The local database is the source of truth. The network is optional and always writes to the database, not
bypassing it: the app must work on a plane and in a country where half the services
are unavailable. Every record has had updatedAt, deletedAt and
remoteRevision — there’s no synchronization yet, but adding it later without rewriting everything
is only possible this way.
The model never writes directly to the plan. It returns text from which a list of changes is compiled, and the user clicks “Apply” themselves. The same rule applies to landmark recognition: a photo caption is just a suggestion until the user confirms it.
Private and public are distinguished by type, not by accuracy: in TripTemplate,
which is intended for external use, there are simply no fields for reservations, flights, or participants.
Details — docs/SHARING.md.
Releases
No releases yet.
Open issues
No open issues 🎉