Waiting in long queues taking tens of minutes is an exhaustive process. The idea is to be free to use your waiting time however one pleases by making classical waiting queue ticket systems even more digital.

What it does

We use an SMS and Phone call based enqueueing, notification and dequeuing system with pre-emptive notifications and prediction of queue speeds to allow people more freedom of movement during busy days at public counters etc.

How we built it

We used a python / flask / swagger based backend deployed on AWS using trilio as provider for sms and text-to-speech phone call services. The frontend is built on bootstrap and jquery as static dynamic web pages accessing the backend via REST standards.

Challenges we ran into

The framework we used for our backend is easy to setup but immature and impossible to debug with the difficulties already coming in python. Twilio's API and Website proved to be quite a handful at times, yet the biggest difficulty was its name, getting mistaken for "twillo" and causing typos numerous times.

Accomplishments that we're proud of

We had a good team. We decided early on on a good seperation of responsibilities leading to good individual components being built with care. The second part of the project was spent in cooperation unifying our ideas and minding interfaces. Our final quarter of the project was spent testing layer by layer, making our project a successfully executed and carefully planned project; an accomplishment during a hackathon.

What we learned

I think everybody learned their fair share during the project. Whether it be about the working of swagger / flask, the details of the python 3 language and modules, frontend development and working with bootstrap or just the sheer challenge of fighting a 3rd party api knowing one 's not gonna win.

What's next for iTicket

Built With

Share this project: