Journey strip
Review a saved rail itinerary with station cards and Imported schedule timestamp.
Back to work
- Rail journey notebook
- AI mobile concept
Routeplume
A rail-journey notebook connecting imported tickets, timestamped itineraries and searchable station notes.
Designed around4 AI workflows
Project overview
Routeplume explores rail journey notebook through a mobile experience built around a vertical journey timeline with ticket drawer. A rail-journey notebook connecting imported tickets, timestamped itineraries and searchable station notes. The proposed journey connects journey strip, ticket reader, travel-note helper, trip archive. Four original phone showcases establish the visual direction, while the case study defines the supporting feature set and a proposed Java architecture.
The challenge
Rail travelers need saved tickets, station notes and revised personal plans connected without treating unverified AI text as live departure information. On a phone, the person also needs to capture information quickly, understand where an answer came from and return to the original material without navigating through a dense desktop interface.
- Keep journey strip and ticket reader connected within a short mobile flow.
- Make ticket extraction correctable when the model misreads the input.
- Explain itinerary questions through visible references or user-selected preferences.
- Keep changes, sharing and data retention under explicit user control.
Our solution
The design begins with a vertical journey timeline with ticket drawer, using large touch targets, short task sequences and contextual sheets. Draft journey fields from user-supplied tickets. Condense saved station and transfer notes with links. The companion views keep drafts, original material and accepted decisions distinct. A rail blue, cream and signal red visual system gives this app its own character within the collection.
- Draft journey fields from user-supplied tickets.
- Condense saved station and transfer notes with links.
- Answer from imported plans while showing their timestamps.
- Suggest a checklist from the user's trip duration and preferences.
Key features
Inside the platform
Keep a journey's details within reach.
Original mobile interface concepts with fictional content. AI responses illustrate proposed interactions; they are not live model results.
Proposed technology stack
Proposed Android architecture using Java and Android Views. AI processing, storage and synchronization are design proposals for this concept, not integrations implemented by this portfolio.
- Java
- Android Views
- SQLite
- AI services
The results
The concept defines four mobile views, four AI workflows and twelve feature areas. The next validation would ask a user to complete journey strip, inspect the proposed ticket reader output and correct an intentional extraction or suggestion error. Evaluation would focus on source traceability, correction effort and task completion. No usability study or business-impact measurement is claimed.
4Original mobile showcase views
4Proposed AI workflows
12Designed feature areas
Ready to build something similar?
Let's bring your idea to life
Whether it's a platform for your industry or something completely different, we can help you build, integrate and scale.