MS3 ‐ Decision process - S3-G31-Kotlin-QueueHub/mobile-app-android GitHub Wiki
Decision process of The App Idea.
To start, we want to clarify that the evidence of this brainstorming process is in this page of the wiki.
We started by looking for pros for each of the ideas we had individually chosen for an application.
Once we had the pros we started to place the cons to converge on the ideas that were not feasible or did not suit our tastes.
Finally, we took a vote on which idea we should implement. The final idea was the Turn Machine because we think that is a real problem and is into our development skills.
In the brainstorming process we let us to imagine whatever we want in the apps and say it before writing, if the idea was unrealistic, we decided to don't put in the list.
Decision process of features
To make the decision process, as mentioned above, we performed a convergence process in which we categorized the ideas, voted for the ones we liked the most, and refined them more and more. Finally, we chose the ideas that had our 3 votes but were also basic functions of the application and would provide an optimal solution for potential users of the application. The main features and ideas that emerged from this process are the following:
- There must be a login system that allows the information to be persisted for several devices.
- Dynamically calculate the average waiting time for queues at different companies.
- Send reminders when your turn is near via SMS/Whatsapp/Pushup notification.
- Recommend locations based on average wait time.
- Enter the queue remotely.
- The solution should provide companies with a summary of statistics and insights on their attention in the queues.
- There should be a visible and interactive map showing the location.
- Show feelings of the people in the queue through the reviews.
- Rate the service.
- The number of people in the waiting line should be displayed in real time.
- There must be the ability to reserve at any time
- Limit the number of reservations per person.