dinQ

The pickleball queuing app. - Find a court. Fast.

Comment

Our inspiration for dinQ

Have you ever gotten to the pickleball courts and had to wait forever to get onto a court? Have you ever wished there was a more organized way to view court availability than to walk around the entire field? Look no further than dinQ, a lightweight, accessible way for pickleball players to start, queue, and organize matches without needing complicated software or sign-up processes.

What dinQ does

dinQ (dink, with a queue) is a browser-based web app that manages queues for up to 12 pickleball courts. Players can quickly create a temporary profile with their name, gender, and age, then join as individuals or groups of up to 4. They choose a time slot (30 or 60 minutes), and the system automatically assigns them to the first available court. The app displays each court visually, like a real pickleball court, with player spots filling as groups join.

How we built dinQ

We built dinQ using HTML, CSS, and JavaScript, using localStorage to persist data between refreshes.

Challenges we faced

  • Designing a queueing system that works seamlessly for both individuals and groups.
  • Making the courts visually appealing while keeping the interface simple.
  • Persisting data without using a backend (solved with localStorage).

Accomplishments that we're proud of

  • Building a fully functional, self-contained app with no backend.
  • Creating a clean, court-like interface that visually represents the game.
  • Supporting flexible group queueing (1–4 players).
  • Keeping the user flow intuitive and lightweight for quick adoption.

What we learned

We learned how to balance functionality and usability when designing sports management tools. We also deepened our experience with client-side storage, UI design, and logic for handling real-world constraints like group placement and time limits.

What's next for dinQ

  • Adding mobile responsiveness for players to join queues easily from their phones.
  • Introducing smart court rotation rules (e.g., prioritizing wait times).
  • Allowing organizers to export data or view match histories.
  • Adding player stats, profiles, or skill levels to balance games.
  • Supporting online/multi-device synchronization with a lightweight backend.

Built With

Share this project:

Updates