|
|
[**<- return to homepage**](Home)
|
|
|
|
|
|
|
|
|
# Product Vision
|
|
|
|
|
|
## Vision Statement
|
|
|
* 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:
|
|
|
* Creating and joining leagues
|
|
|
* Creating and joining teams
|
|
|
* Users can search for a league, and then see all available teams within the league
|
|
|
* 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.
|
|
|
* Our app was recently released on Google Play: [GamePlan](https://play.google.com/store/apps/details?id=com.zizzle.cmpt370)
|
|
|
|
|
|
## Need and Value
|
|
|
* There is a great opportunity for our product because the target market is quite large. Our product appeals to people that are interested in playing team sports. *According to [Stats Canada](https://www150.statcan.gc.ca/t1/tbl1/en/tv.action?pid=1310060201), around 27% of Canadians regularly play sports. We aim to target people that want to participate in organized sports and track games against other teams. Initially, we will focus on students at the University of Saskatchewan.
|
|
|
* Our app aims to reduce the load of managing a sports team, allow players and teams to connect, and allow team members to keep track of stats.
|
|
|
* While other sports management software exists, our app has a unique focus on individual players of a team instead of coaches or league organizers. By focusing on sports players instead of coaches we appeal to a broader user audience and can offer a more intimate user experience. By giving tools to the users, it is easy to create small leagues for friends to have a more structured approach to playing sports outside of formal organizations.
|
|
|
* Since we focus on individual users, we additionally offer support for non-team games and sports played individually such as squash. For example, a squash league can be made with each individual player making their own team. Then, each game against other players can be recorded with scores to see standings and user performance over time.
|
|
|
|
|
|
## Stakeholders
|
|
|
|
|
|
| | |
|
|
|
| ---------------- | --------------------------- |
|
|
|
| Connor Doka-Moore| connordokamoore@icloud.com |
|
|
|
| Sam Loran | loransamuela@gmail.com |
|
|
|
|
|
|
* Our stakeholders are both students at the University of Saskatchewan.
|
|
|
* Before our product was created, we asked each of them for their thoughts on this idea, market possibility, and their personal opinion on the usefulness of this product.
|
|
|
> "As an app for casual sports players it allows for easy tracking and competition with friends. It is marketable for tournament organizers or sports organizations, such as the U of S, to easily distribute standings and scores. It is also marketable for competitive athletes who want to track their progress or past results." - Sam Loran (Student / Squash Player)
|
|
|
|
|
|
> "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 on 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.
|
|
|
|
|
|
## 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 |