Festival Event Guide Android App

College fests run on chaos: posters on walls, WhatsApp forwards, and a schedule PDF nobody can find when the EDM night starts. Attendees miss events they would have loved simply because discovery is broken — the lineup lives in one Instagram story, the venue map in another, and timings change without notice. This project builds the attendee-side fix as an Android event guide app for a 3-day cultural festival: a home screen with dates, venue and headline artists; a schedule browser with day tabs covering all 42 events; event detail pages with time, venue, entry fee and description; an interactive venue map that spotlights the selected event's location; and a starred shortlist so each attendee builds a personal plan. The content model is a static-but-structured event dataset — exactly how real fest apps ship their first version — with an offline-first design so the guide works when 5,000 phones crush the campus network.

1. The app loads the festival dataset (3 days, events, venues, artists) bundled as structured local content.
2. The home screen renders festival dates, venue, stats and the headline artist cards.
3. The Schedule tab shows day tabs; selecting a day lists that day's events as tappable cards.
4. Tapping an event opens its detail page — time, venue, fee, description — and draws the venue map with that event's location highlighted.
5. The star control on cards and detail pages toggles shortlist membership, persisted locally.
6. The Saved tab aggregates all starred events into the attendee's personal plan, ordered by day and time.

Tech stack:

• Android (Kotlin) — native app target
• Offline-first local content model (JSON dataset)
• Canvas-based venue map rendering
• MVVM architecture
• Material Design components

• [Headline artist lineup] Home screen showcases the star performers with set times and stages — the first thing every attendee looks for.
• [Day-wise schedule browser] Three day tabs covering the full program; each event card shows time, name, venue and entry fee.
• [Event detail pages] Time, venue, entry fee and a description paragraph per event, so attendees can decide what is worth the walk.
• [Interactive venue map] A canvas-drawn campus map with Main Stage, Amphitheatre, EDM Arena, Food Court and Main Gate; the selected event's venue is highlighted with walking distance.
• [Personal shortlist] Star any event to build your own plan; starred state persists across screens.
• [Offline-first content] The event dataset ships inside the app — schedule, map and details work with zero network, which is when you need them most.
• [Bottom navigation] Fest, Schedule, Saved and Pass tabs mirror real event-app structure.

• Complete Android app source code (Kotlin)
• Festival content dataset (JSON: events, venues, artists)
• Venue map rendering module
• App icon and graphic assets
• Project report PDF (background, offline-first design, content modeling, methodology)
• PPT presentation for final review
• Viva Q&A preparation document (Android, offline strategies, canvas drawing, UX)

• The demo uses a fixed festival dataset; a CMS for organizers to edit events live is designed but not built — content updates ship as app updates in this version.
• No live schedule-change push notifications; the offline-first model means last-minute changes need a content refresh (documented as future scope with a backend).
• The venue map is schematic, not to scale — it guides, it does not navigate turn-by-turn.
• Ticket purchase is out of scope; the Pass tab is structural, with payment integration listed as future work.
• Crowd-density or "how full is the venue" features would need on-ground data feeds not available to a student project.