... | ... | @@ -20,7 +20,6 @@ Before we began writing the code we discussed how we were going to handle keepin |
|
|
* The user should be able to join a team
|
|
|
* The user should be able to see members on their team
|
|
|
* The user should be able to see and add scores for games played by their team
|
|
|
* Team owners should be able to accept user requests to join their team
|
|
|
* The user should be able to edit their info in the app
|
|
|
* Usability
|
|
|
* Our app should be easily downloadable, which we will ensure by publishing on the Google play store
|
... | ... | @@ -28,7 +27,6 @@ Before we began writing the code we discussed how we were going to handle keepin |
|
|
* App layout should be consistent for the user (i.e. navigation menu placed at the same location on all pages, etc.)
|
|
|
* Reliability
|
|
|
* Our app should be available 24/7 with minimal downtime (ideally 0 seconds)
|
|
|
* Since our app relies on the main point of storage being a server (firebase database), our app will be affected if any outages occur on this server. However, we will try to also store data locally on the phone, so that the user can use the app without being connected to the server (and then the app auto-syncs when connected to the server).
|
|
|
* Performance
|
|
|
* The app should look and feel smooth in terms of loading data, rendering the UI, and displaying animations (i.e. switching between screens). The user should not be able to notice the time between frames in an animation.
|
|
|
* Our app should also load within 3 seconds max. if we compare this time to a website, it will be faster than 50% of the web and corresponds with the time that the average user leaves a website if it has not loaded yet (https://www.bluecorona.com/blog/how-fast-should-website-be/). We will aim for 1-2 seconds load time, but 3 seconds will be our max.
|
... | ... | |