sanchezjjose / sportify

web application for managing schedules, scores, rosters, statistics, news and notifications for teams and games.

SPORTIFY

A RESTful, Reactive API written in Scala with Mongo and Play!

The API supports scheduling games, managing player RSVP's to games, communicating upcoming games, and much more.

Stay tuned...

sportify's Issues

Emails should overwrite the previous in Mongo when creating a new one.

Player numbers should be unique

update README on how to run

Make reactive!

Create a login cookie with 1 year expiration

Redesign and remove bootstrap

Twilio to send upcoming game text message reminders, with image of google maps location

Live game streaming

Update model structure

Use Cases

• A Season should contain a list of Team ID's
  e.g, The 'Fall 2015' season contains 'Knicks', 'Lakers', and 'Bucks'
• Each new Season will contain new Team ID's. The same teams from the previous Season can exist with the same name and roster if it hasn't changed, BUT the 'id' must always be unique. This will allow to keep track of how a team changes over time
  e.g, each new Season the teams Roster is likely to change
• A Team has a list of Player ID's
• A User can be a player on multiple teams, thus should contain a list of Player ID's.
• A UserContext should be passed alone with every request

Example Models

UserContext

• selected_team
• other_teams
• current_season
• next_game
• user
• player
• sport

Season

• _id
• name
• team_ids
• game_ids

Team

• _id
• name
• player_ids
• sport

Game

• _id
• team_ids // usually 2 teams playing each other
• number
• start_time
• address
• gym
• location_details (optional)
• opponent
• result (optional)
• players_in
• players_out
• is_playoff_game

Validate on registration if user already exists

Change default landing page to most recently viewed

Standings and scores page

Restful API

Create endpoints that return JSON.