Skip to main content

7.1 User Feedback and Testing

The App is ready for testing purposes now and the app can be accessed here. But before you start using the app, I recommend you going through this post which explains in detail the functioning of the app.
Since our app is to be run on a local server in a shop, it is not possible to actually show you the full functioning of the app. So, the best we could do was upload our app online for the user feedback. Now, you can access all the functionalities of the app(all pages can be accessed by anyone) but in the real life scenario, only the song queue and song database pages will be accessible by the customers of the shop, the admin login page and admin console page will be accessible by the shop owner and the player page will be just opened by the shopkeeper on a window and that will automatically play the songs either from the queue or if the queue is empty, a random song will be played.
Now, I will explain the pages in detail and the flow of the pages:

Customers:

The first screen you see when you visit the page is the current song queue in the shop's database.
First screen in Customer mode
Here, you can view the songs in the current queue. The Feedback button pops up a simple prompt to fill in your feedback to the shop owner. The "Get the List" button takes you to the second page of the app which displays the songs in the shop's database.
second page accessible to customer
Here you can see the list and you can add your choice of song(limited to 1 song per person) and if by any chance your song isn't in the current database, you can request the song by clicking on "Write to Us" below. This takes you to the third page accessible to customer.
Song Request page to submit song request
Note that since customers just need to add song and request songs so they wouldn't be amused to go through all the registration process and so we login the customer when they visit our first page and use the same token to request in other pages.

Shopkeeper:

To have access to the requests and play songs in the shop, the shopkeeper needs to first login to the server using our login page, available at "/adminlogin" endpoint:
Shopkeeper login page
The current credentials for testing purpose is "username:shopkeeper, password:shopkeeper123". After logging in, the admin console is available for the shopkeeper which displays the customer feedback on one side while the song addition requests in the other side. The admin has the rights to delete the feedbacks and requests.
The admin console
Also, after logging in as the owner, the shopkeeper can play the queue songs via the endpoint "/player". It is just an empty page(no UI) because all it needs to do is play songs from the queue or if the queue is empty, play a random song from the database. For some obvious copyright issues, we have not included the actual songs in the webapp, but there is a demo song that plays for every request. If you still need to verify if the songs are played from queue or at random, you can open the console and see which song is currently playing. This way you can see the actual functioning of the app in real time.
So, I hope that you go through this app and kindly test the app for any bugs or issues and I request you to either comment below your feedback or you can PM me on slack at @akashagrawal if you are a Hasura Intern.

Comments

  1. Siddharth Jain19 July 2017 at 21:31

    I think admin page need a logout button. Also how will admin add a song to queue
    ?

    ReplyDelete

Post a Comment

Popular posts from this blog

3.2 Hasura Data API + Postman Collection

The previous blog covered the data modelling of our app. Now it is the time to test the working of our database using some sample queries to the data endpoint of the database. Some of the sample queries made through Postman are: Insert to Song Queue Select all songs in the song database Select all songs in the songs queue The link to the API query collection is here .
Post a Comment
Read more

4.1 App Screen 1 (UI + Backend integration)

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 s...
Post a Comment
Read more

1.1 The Three Screen App Idea

The beginning of a new project is always tough, especially if you don't have a clue on what app you are going to build. We need to come up with an idea that is helpful in real life and something that people are interested in using. So, my friend and teammate for our internship project, Mayank Padhi, and I started thinking and researching on the internet ideas that we can develop into apps with our skill set. After a week or so, we had our own list of 3-5 ideas each that we thought were good. We shortlisted our ideas and ranked them according to our preferences and at the top of the list was a " Blood Donation App ".     We both loved the idea of making a blood donation app where people would register themselves along with their location details and when a needy person requested for blood, our app would send requests to the registered people if they would be free to donate and help another person in need. But after some research online, it turned out that the idea was a...
Post a Comment
Read more