The 1st screen app's UI and authentication part was dealt by my teammate Mayank Padhi and the details can be found in his
blogpost. After the sample UI design, it is time to get real and get the real data from the database and use that to populate our first page( the songs queue page). So, as soon as the authentication takes place, another request is sent to get the songs list in queue via the data endpoint of our project. The response data of each song is then sent passed through a template creating function that fills all the details of songs at the right places and an accordion tab is ready. Similar process occurs with the rest of the data and then the HTML is then populated with our queue list, something like this:
 |
| First look of our Home Screen |
Now, if you click on any of the song tabs, you will get the song details of that particular song. Like this:
 |
| Song details on clicking a tab |
The "Get the List" button would take you to the app's 2nd screen. the song database. The complaints button would open a prompt for user to provide feedback.
Comments
Post a Comment