The Summit Music Festival app

Hey Justin,

Great start on the information architecture here. You’ve included the core information users would expect to find in a music festival app.

It would be helpful to understand a bit more about the project itself. For example, who is the festival aimed at and what is the app hoping to achieve? That context would really shape the structure and priorities.

Based on what you’ve shared, here are a few suggestions:

• Since there’s a “My Events” area, I’m assuming the app is designed for both users who haven’t bought a ticket yet and those who already have. The ideal experience for these two groups will likely look quite different. I’d recommend starting by defining those user types more clearly and mapping out their individual journeys.
• On the homepage, the buttons for schedule, tickets, artist list, and map feel like primary navigation items. A common UX pattern would be to place these in a bottom navigation bar or within the top navigation. That would free up the homepage to focus on the most relevant information for each user type.

For example:

• For potential attendees, the homepage could highlight what the event is about, key selling points, standout artists, dates, and what makes it unique.

• For ticket holders, it might prioritise a countdown, planning tools, important updates, what to pack, add-ons, and quick access to their schedule.

Overall, you’ve got a solid foundation. The next step is really about clarifying who the app is for, what its primary purpose is, and shaping the ideal journeys around that.