CSE 134B: Jeff Evans Fan Club

HW 4

It is time to implement the soccer team management application we speced in HW1 and prototyped in HW3. Traditionally as coding focused computing professionals we would spend a great deal of time building data structures and models first, but so far in this class we have designed from the interface down. In this step we should work upwards from the data and join the two halves. In this assignment we will build a partially functioning application and when finished all that be missing will be a few server-side pieces of the application.

Planning Document

Our group fleshed out a decent amount of features in this iteration of the homework. Using local storage, we were able to implement CRUD with the players, games, and game events. We were also able to handle log in, supporting multiple accounts, with the use of state management. In addition, we also added the capability to upload and view images, which were used for the team logo and the players' image.

Moving forward, we still have several features we would like to add. As it is required, we would like to actually hook up our site to an actual online backend, such as Firebase, and not have to use local storage. We would also like to add the ability to manage one's account. In addition, users can currently only sign up as coaches who manage teams. In the future, we would like to add the ability for players/parents/spectators to be able to view the team data, but not have the ability to modify it. Lastly, we would like to add some sort of mechanism for linking teams together in a league. Currently, users must manually add the other teams, which they cannot edit at the moment. This is just a temporary fix, in which we will fix fully later.

Load Time and Size Analysis:

Page Load Time Page Size
Login 6.55 s 48.5 KB
Sign Up 6.85 s 47.5 KB
Coach Sign Up 7.05 s 72.7 KB
Player Sign Up 6.86s 71.4 KB
Home Page 7.10 s 55.7 KB
Schedule 7.05 s 53.8 KB
Game Detail 7.18 s 56.8 KB
Add Game 7.13 s 55.0KB
Edit Game 7.12 s 55.0 KB
Add Event 6.96 s 51.9 KB
Players 7.06 s 53.1 KB
Add Player 7.12 s 56.8 KB
Edit Player 7.17 s 58.0 KB
Player Details 7.10 s 56.4 KB

We ran our performance analysis on a device running Android 5.1.1. We used the Chrome DevTools to emulate the device running on a Slow 3G network.

On average, pages took about 7.00 seconds to fulfill all the requests on the page. What we found was that the majority of that time was from the stall before the download of our webfonts.