Android Bus Pass Renewal for Students with Route Timetables

Android Bus Pass Renewal for Students with Route Timetables is an Android application that replaces paper bus-pass queues with a renewal workflow built for students. A student creates an application or renews an expiring pass inside the app, uploads a college ID card, a photograph and route proof, and tracks the request until an admin approves it. Approval issues a digital pass carrying a QR code, a pass ID and validity dates, so the pass can be shown to a conductor without paper. The app sends a renewal reminder seven days before expiry, so a student is warned before the pass lapses. Route timetables sit alongside the pass as a secondary feature: the admin enters routes, stops and departure times, and students read them in the app. No live vehicle tracking and no fare calculation sit at the centre of this system, and no connection to any real transport authority is claimed.

The system runs as one end-to-end renewal workflow with two roles: the student who applies, and the admin who verifies and approves. A student signs in, picks a route and a pass type, and uploads three documents — a college ID card, a photograph and route proof — and the request enters the admin queue as pending. The admin checks the documents against the requested route, approves the request or asks for a clearer document, and approval issues a digital pass carrying a QR code, a pass ID and validity dates. The QR check rests on a first-principles point: the pass ID and the validity dates travel with the code itself, so validity is judged by comparing the current date with the printed dates rather than by a live lookup. Seven days before expiry, the app sends a renewal reminder, and the student repeats the same workflow to renew.

1. The student signs in and creates a profile with college details, roll number and home route.
2. The student chooses a pass type and a route, then uploads the college ID card, a photograph and route proof.
3. The request enters the admin queue with the status pending, and the student can track it in the app.
4. The admin verifies the documents and the requested route, then approves the request or asks for a clearer document.
5. Approval issues the digital pass, showing a QR code, a pass ID, the route and the start and end validity dates.
6. The student shows the digital pass to the conductor, who checks the pass ID, route and validity dates.
7. Seven days before the expiry date, the app sends a renewal reminder, and the student renews through the same workflow before the pass lapses.

Tech stack:

• Kotlin · Android Studio
• Jetpack Compose · Material Design
• Room database · local storage
• Firebase Authentication · Cloud Firestore
• QR code generation · ZXing library
• WorkManager · renewal reminders
• REST API · admin web panel
• Git · version control

The strongest capabilities in this build are the renewal application with document upload, the admin approval workflow, the digital QR pass with validity dates, and the renewal reminder system, with static route timetables supporting the pass rather than leading it. A student moves from application to approved pass inside one workflow instead of visiting an office with paper forms, and the admin sees every request in a single queue with its documents attached. Builder note from the demo build: the demo queue holds three requests — one pending, one approved and one needing a document re-upload — and the three demo routes total 34 stops, from 14 plus 11 plus 9 stops. The timetable feature stays deliberately static, because a renewal system needs correct departure times and routes far more than it needs a moving dot on a map.

• [Renewal application with document upload] The student applies for a new pass or renews an expiring one, uploading a college ID card, a photograph and route proof through the app, with the request status visible at every stage.
• [Admin approval workflow] The admin reviews each request with its documents attached, approves it, rejects it with a reason, or asks the student to re-upload a single unclear document without restarting the whole application.
• [Digital QR pass with validity dates] Approval issues a digital pass showing a QR code, a pass ID, the route and start and end validity dates, which the student shows to a conductor instead of a paper pass.
• [Renewal reminders] The app schedules a reminder seven days before the pass expiry date, so the student can renew before the pass lapses and avoid a gap in travel.
• [Static route timetables] The admin enters routes, stops and departure times, and students browse the timetable for their route, including the next departures from their boarding point.
• [Pass status tracking] Every request shows one clear status — pending, approved, needs document, or expired — so the student always knows whether action is needed.
• [Admin configuration of routes and pass types] The admin manages routes, stops, timetables and pass types (Semester and Monthly in the demo data), so the system can be set up for one college without code changes.

Optional customization (not in the base build): a payment step inside the app, a conductor-side scanner app, and SMS reminders in addition to in-app reminders. Future scope (not implemented): live vehicle positions, automatic ID verification, and integration with a real transport authority system.

• Complete Android app source code (student app with renewal, documents, QR pass and reminders)
• Admin web panel source code for the approval queue and route configuration
• Working single-file demo of the app screens for presentation and testing
• Project report PDF (background, workflow design, database design, methodology, limitations)
• PPT presentation for final review
• Viva Q&A preparation document (Android components, approval workflow, QR validity logic, Room and WorkManager)