App Flow - How to use it
How I imagine people using the app. Everyone has the number and no cheating in the queue before the show

Concert Q: Fan Queue Organization

FOR EVERYONE WHO WANTS TO TRY: CHECK-IN IN A SPECIAL VENUE LOCATED IN FRANCE, PARIS, ABC TEST PLACE - IT HAS A SPECIAL RADIUS SO EVERYONE CAN PASS THE CHECK

Inspiration

Music fans often spend 20+ hours standing on concrete outside stadiums to get a good spot near the stage.

These fan-made queues are often unorganized, physically exhausting, and sometimes unsafe. Fans often try to organize themselves using Sharpies, paper numbers, or wristbands, but these systems are easy to cheat, lose, non-eco.

We wanted to digitize this culture while keeping the spirit of first-come, first-served fairness: giving fans the freedom to wait more comfortably while preserving the integrity of the queue.

What it does

Concert Q is a virtual queue management system designed specifically for concert venues.

Core features

Arrive & Verify
Users must be physically near the venue to join a queue, verified through GPS.
Structure Your Queue
Fans can create or join specific queues based on ticket type, such as VIP, General Admission, or Early Entry.
Virtual Numbering
Once verified, the app issues a unique sequential queue number.
Fair Play
Queues automatically open at 6:00 AM local venue time for every venue worldwide, ensuring a fair start regardless of where the user is located.

How we built it

The application is built with a modern web stack:

React
Tailwind CSS
Supabase

Our secret weapon during development was medo.dev. Using the AI agent allowed us to move from an idea to a working MVP much faster while still handling complex product logic.

How medo.dev helped us

Iterate at lightning speed
We moved from concept to a fully functional, multi-country app in record time.
Solve complex logic
The AI helped us implement IANA timezone-aware opening hours and device-based anonymous authentication.
Ensure code quality
Every component, like GPS distance logic, was built with clean and scalable code.

Challenges we ran into

Timezone management

Managing a 6:00 AM opening time for a venue in Paris while the user may be in London, New York, or Tokyo was tricky.

We had to build a robust system using IANA timezones to make sure the countdown and opening logic always respect the venue’s local time.

Anonymous security

We wanted a zero-friction experience with no passwords or mandatory accounts.

To achieve this, we built a secure identity system based on unique device IDs stored locally, allowing users to restore their ticket even after closing the browser.

GPS reliability

We had to fine-tune radius-based verification so that users must actually be near the stadium or venue before they can join a line.

Accomplishments that we're proud of

The slot-machine verification code
We created a polished animated verification system that looks fun while also making screenshots harder to reuse.
Clean architecture
Despite the speed of AI-assisted development, the project structure is modular, readable, and scalable.
Simple user experience
We successfully hid technical complexity like GPS verification, timezones, and anonymous authentication behind a simple one-tap interface.

What we learned

Building Concert Q taught us that AI-driven development with medo.dev is not just about writing code faster.

It felt like working with a senior architecture partner that helped us think through edge cases, from global timezone offsets to UI behavior across different devices.

We also learned that niche real-world problems, like concert fan lines, require very specific and carefully designed UX solutions.

What's next for Concert Q

Our next steps include:

Real-time notifications
Alert users when their check-in time is approaching.
Live queue stats
Show a live dashboard with the number of people in each line.
Venue partnerships
Collaborate with stadiums and event organizers to integrate Concert Q into official entry protocols.
Expanding
Adding more countries, cities and venues.