... | ... | @@ -6,14 +6,15 @@ |
|
|
* Bring competitive athletes together to have more games and enable them to track their performance.
|
|
|
|
|
|
## Product Description
|
|
|
* Our product is an Android app that allows individuals to create and join sports leagues, create and join teams within leagues, search for leagues and team to join, schedule games with other teams in a league, record game scores, and see statistics in the form of user win/tie/loss graph, team win/tie/loss graph, and team win: loss ratio over time.
|
|
|
* Essential features of this team management app include:
|
|
|
* Our product is an Android app that allows individuals to create and join sports leagues, create and join teams within leagues, search for leagues and team to join, schedule games with other teams in a league, record game scores, and see statistics in the form of user win/tie/loss graph, team win/tie/loss graph, and team win:loss ratio over time.
|
|
|
* Key features of this team management app include:
|
|
|
* Creating and joining leagues
|
|
|
* Creating and joining teams
|
|
|
* Users can search for a league, and then see all available teams within the league
|
|
|
* Users can see players (members) on a team and access their information (Name, Email, Phone Number)
|
|
|
* Scheduling games between teams
|
|
|
* Recording game scores for each game
|
|
|
* Showing historical team performance through win:tie: loss bar graphs, win-loss ratio line chart, and team rankings in a league.
|
|
|
* Showing historical team performance through win:tie:loss bar graphs, win-loss ratio line chart, and team rankings in a league.
|
|
|
* Our app was recently released on Google Play: [GamePlan](https://play.google.com/store/apps/details?id=com.zizzle.cmpt370)
|
|
|
|
|
|
## Need and Value
|
... | ... | @@ -36,9 +37,9 @@ |
|
|
> "The recreational leagues I've been involved in are always on different sites and many times only the captain has access. Having an app would make it easier for everyone to stay connected to what's happening with the team and the league. People that are involved in multiple sports or teams will also benefit from having everything in one place." - Connor Doka-Moore (Student)
|
|
|
|
|
|
## Quality Assurance
|
|
|
* Quality was ensured by keeping in mind our initial target market (people interested in sports who are U of S Students) and making sure that each feature is built to be used easily by them. We sis this by progressively developing and testing our app repeatedly and after each portion of a feature was added. With the final product, we focused not only on the features, but also user experience by adding in visual appeals (such as graphs), smooth animations between pages, and custom graphics that were not built-in to Android Studio (the official Android IDE).
|
|
|
* Continued communication at each stage of development to our stakeholders allowed us to understand what users want and guide us in creating a better product.
|
|
|
* Quality was ensured by keeping in mind our initial target market (people interested in sports who are U of S Students) and making sure that each feature is built to be used easily by them. We achieved this by progressively developing and testing our app repeatedly and after each portion of a feature was added. With the final product, we focused not only on the features, but also user experience by adding in visual appeals (such as graphs), smooth animations between pages, and custom graphics that were not built-in to Android Studio (the official Android IDE).
|
|
|
* Continued communication at each stage of development to our stakeholders allowed us to understand what users want and guided us in creating a better product.
|
|
|
|
|
|
## Technology Requirements
|
|
|
* We used Android Studio and made an app using Java. We chose this because our group was most experienced in Java and wanted to create a product that can be used by everyday consumers. Our app will be compatible with Android 5.0 (Lollipop) and up, which covers more than 85% of the Android market.
|
|
|
* Our app also used a realtime database and authentication database/server to store the login information and data of each user, team, and league. To do this, we used Google Firebase because it was created by the same company as Android Studio (Google), and therefore integration between both products was smoother. We also wanted to create an app that is useful after this class. Since we now have our own database and Android Studio project, we can keep this project running even after the class has ended. |
|
|
\ No newline at end of file |
|
|
* We used Android Studio and made an app using Java. We chose this because our group was most experienced in Java and wanted to create a product that can be used by everyday consumers. Our app is compatible with Android 5.0 (Lollipop) and up, which covers more than 85% of the Android market. Restricting this app to be used by only Android 5.0 and up enabled us to use more advanced features that were available in Android Studio for newer operating systems.
|
|
|
* Our app also used a realtime database and authentication database/server to store the login information and data of each user, team, and league. To do this, we used Google Firebase because it was created by the same company as Android Studio (Google), and therefore integration between both products was smoother. We also wanted to create an app that is useful after this class. Since we now have our own database and Android Studio project (and the app is published), we can keep this project running even after the class has ended. |
|
|
\ No newline at end of file |