In some embodiments, the media application may be in communication with a service that maintains information about the user's fantasy sports league. For example, the media application may be in communication with a server maintained by a service such as DraftKings, Yahoo!, ESPN, or Fan Duel. The media application may access the information using a service API, remote procedure call, or by, for example, scraping data. The media application may obtain a username, password, or other login credentials unique to the user to allow the media application to retrieve information particularized to the user. In some embodiments, the media application may obtain a username or team name that allows the media application to identify the user's roster information from among a league of users. In some embodiments, the information also contains the performance of the user's fantasy team during a given period of time, e.g., during a week, and/or includes information about the real life sporting events that indicates the points in the fantasy sports league.
In some embodiments, the media application may retrieve, from a memory, current status data of a fantasy sports event in which a user is participating. For example, the user may be in a fantasy football league, and the media application may retrieve the current status of the user's weekly matchup (e.g., the user's active roster, the user's opponent's active roster, the current score for each user in the matchupfantasy matchup, etc.). In some embodiments, the media application may identify players participating in the live sporting event that are from a roster maintained by the user for the fantasy sports event. For example, the media application may identify players from the user's fantasy team roster that play on either the San Francisco 49ers or the San Diego Chargers and that are active on the user's roster.