Good things happen
close to home.

The starting point

Design question: how might someone find a nearby event and understand its time, cost and area before deciding to attend?

This is a design hypothesis, not a finding from user research. The intended audience is anyone nearby interested in local events.

The core flow

Discover → Event details → Saved events.

Discover puts date, area and price on each event card. Details adds duration, what to bring and location guidance. Saved keeps one consistent event visible for later.

Why it looks this way

• A bold headline and one featured card create a clear starting point.
• Neutral surfaces and a purple accent separate content from primary actions.
• The same date, event name and price repeat across all three screens for continuity.
• Text labels accompany navigation and price, rather than relying on colour alone.

Privacy and trust

Discovery shows approximate public areas, not people's exact locations. The concept does not request GPS access or display attendee tracking.

The details and saved screens distinguish saving from booking. A real service would need host checks, reporting and a reliable public meeting-point flow before launch.

Scope and limitations

These are responsive visual mockups with anchor links between screens, not a working app. Search, filters, booking and persistence are not implemented. Dates, communities, events and prices are fictional.

No interviews, usability sessions, accessibility audit, competitor study or success metrics were conducted. No improvement or business outcome is claimed.

What to test next

Ask a few people to find a free weekend event, explain where and when it happens, and save it for later. Observe whether they can complete those tasks without help.

Then test filter labels, larger-text layouts, screen-reader navigation and colour contrast. Add empty, cancelled-event and past-event states based on what is learned.