I heard a question today — — “How would you build an Event Booking App?”
Just like that, so vague, I actually heard a very similar question last week as well. So I organized my thought really quick and created a flow chart, this is just a framework, there are so many details and detailed questions we can ask here. Such as the following:
- Who: who is this app is for?
- What: what is the app about? event booking app
- When: when is the event? or you can ask, when this app should be launched, timeline or urgency?
- How: how are you going to build it?
- Why: why do you need this app?
Now what we need to do is to layout some groundwork to help answer the above questions. Instead of focusing on all of the perspectives, try to focus on one perspective and anchor it as the starting point to develop your solutions. Remember, you can always add more features later on.
I created the following diagram to help with the thought process:
Once the groundwork is done, we can try to answer the questions listed above:
- Who: who is this app is for? → there could be a lot of audiences, since there are a lot of stakeholders, you can always add based on the above, the stakeholders that’s directly related to the event, should just be event organizer and attendees, you may argue that a venue should be considered as well, but at this stage, I just want to keep things simple.
- What: what is the app about? event booking app → rhetorical question here
- When: when is the event? or you can ask, when this app should be launched, timeline or urgency? → this will be based on case by case basis
- How: how are you going to build it? → What the interface should look like? What user experience are you looking to provide? (define 3-word design principal) Are there existing api out there that we can utilize?
- Why: why do you need this app? → can be linked with the 3-word design principal
With the above foundation, you can expand your answer/thought based on it. For example, if the question is “How can Uber, the app, help with events?” You can think about different angles, such as, Uber can promote ride share with event organizer, have an operator or create an algorithm specific for similar events to guide drivers to that area, etc. Or you can think from attendee’s standpoint, when getting to the event, you can order a ride ahead of time, and have a ride to be ready when the event is about to end, etc. Provide convenience would be the key, and how to shorten the waiting time for a ride, taxi use to have a designated waiting area, then for the event, we can create another space for Uber/Lyft, at the same time utilize taxi as well. In order to get people as many as possible out of the event location, we can ask whoever is ordering the ride to gather 4–5 people ahead of time, in that way, 1) event attendees who are waiting for the ride can have conversations, so the waiting time won’t be so boring; 2) it is saving time for the Uber driver to get to different places and pick up additional customers; 3) get more people out of the event at once to increase the efficiency. On the app, when user put in the pick up location, we can add one more question to suggest ride users to gather 4–5 people in order to take the ride, and offer a small discount as an encouragement. In order to identify if currently there is an event going on at a specific location, we can implement calendar function integration with the rider share app.
There are a lot of angles you can take from the diagram above. This is just how I would lay the ground work. I am not saying this is the best approach, but this is the approach that makes most sense for me.
P.S. You can even cooperate an algorithm question on top of this.