How it started

TickAt was born as part of a class project for Database Technology. The task was to design and develop a fully functioning web application that effectively utilized database principles to manage real-world operations.

I wanted to create something meaningful and practical, something that solves a real problem. Inspired by the cluttered and complicated ticket-buying experiences I often faced, I came up with the idea of TickAt, a modern, user-friendly ticketing platform that brings together event organizers and customers through a simple and efficient interface.

Challenge

Developing TickAt came with several key challenges:

• Role-based access control: Managing three different user roles (admin, event organizer, and customer) required clear separation of privileges and strong data validation.
• Relational database design: Building a scalable schema to manage complex relationships between users, events, and tickets while ensuring data consistency.
• Payment and ticket status logic: Implementing a logic system where tickets are only usable after payment verification or activation posed logical and backend workflow challenges.
• QR Code generation and validation: Creating a system where customers can redeem their tickets via QR code required backend integration and event organizer interaction.

Through iterative development and debugging, I implemented a solution that effectively addressed all these challenges using Laravel's rich ecosystem.

Product

Here’s a breakdown of what TickAt offers:

👤 Admin Dashboard

• Full control over the platform
• Activate or deactivate event organizers and customers
• Verify payments manually if needed