Local Train Timetable Android App

Millions of suburban rail commuters plan their day around local trains, yet the timetable lives in cluttered PDFs, unofficial websites that need connectivity, or plain memory. A missed fast train versus a slow one can mean a 20-minute difference, and visitors have no idea which trains skip their station. A dedicated timetable app solves the information problem at the platform: type two station names, get the next trains with times, durations and halt counts, and drill into any train for its full halt list. This project implements that as a native Android app with a bundled offline timetable database, station search with swap, line filtering, train detail views with halt-by-halt timings, and a live-status screen design — built with modern Android architecture (MVVM, Room, Navigation).

1. On first launch, the app seeds its Room database from the bundled timetable dataset (stations, trains, halts, fares) — no download needed.
2. The search screen queries stations with typeahead; selecting source and destination runs a query for trains serving both, ordered by next departure from the device clock.
3. Each result computes journey time and halt count from the halt table, and tags fast trains that skip stations.
4. Tapping a train opens the detail screen, which lists every halt with scheduled times, highlighting the boarding station and destination.
5. The live-status screen is architected against a timetable-derived estimate layer, with the integration point for a real-time feed documented for future work.
6. Saved routes store station pairs in preferences; opening one re-runs the same query pipeline instantly.

Tech stack:

• Kotlin
• Android Jetpack (MVVM)
• Room (offline timetable DB)
• Navigation component
• Coroutines · Flow
• Material Design 3
• Retrofit (future live-feed layer)

• [Offline timetable database] The full suburban timetable ships in a Room database — station search and train lookup work with zero connectivity, including in tunnels and basements.
• [Station-to-station search] Typeahead search over all stations with a one-tap source/destination swap for the return journey.
• [Next-train listings] Upcoming trains with departure/arrival times, journey duration, halt counts and fast/slow indicators, sorted by departure.
• [Train detail with halts] Open any train for its station-by-station halt list with timings, platform hints and first/second-class fare.
• [Line filtering] Filter by Central, Western, Harbour or Trans-Harbour corridors to cut through the noise.
• [Service advisories] A banner system surfaces planned disruptions (e.g. Sunday mega blocks) above the results.
• [Saved routes] Bookmark daily commutes for one-tap lookup of the next trains on a saved route.

• Complete Android app source code (Kotlin)
• Offline timetable dataset + seeding scripts
• Build and install instructions (APK generation)
• Project report PDF (data model, Room schema, MVVM design, offline strategy)
• PPT presentation for final review
• Viva Q&A preparation document (Room, MVVM, coroutines, offline-first design)

• Timetable data is static as bundled — real schedule revisions need a dataset update; the report documents the update procedure.
• Live running status in this build is estimated from the timetable, not from a real-time GPS feed; the feed integration point is designed and documented as future scope.
• Platform numbers are hints from the dataset and can change on the day — the app labels them as such.
• Fares are indicative and follow the dataset's fare table; they are not fetched from the railway's live systems.
• Coverage is limited to the suburban corridors in the dataset; long-distance trains are out of scope.
• Station search needs the exact station spelling to match best — typeahead helps, but transliteration variants are limited.