League of Legends Stat Modules
Automated Content
"I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do it."
- Bill Gates
- Bill Gates
The League of Legends Stat Module System was my first project at Azubu. The goal was to develop an esports focused platform differentiator that would drive viewing engagement. Having worked on similar projects at MLG, I identified two parameters that needed to be fullfilled in order for the project to be a practical addition to our platform.
1 - It needed to live directly on the channel pages next to the video player. If it lived anywhere else on a small subset of users would continue down the acquisition funnel to a page that had the video player.
2 - The process needed to be automated. Websites like Liquipedia and Esportspedia rely on a massive amount of manual work to keep their information up to date. It would be impossible to scale a volunteer force to service our growing user base.
1 - It needed to live directly on the channel pages next to the video player. If it lived anywhere else on a small subset of users would continue down the acquisition funnel to a page that had the video player.
2 - The process needed to be automated. Websites like Liquipedia and Esportspedia rely on a massive amount of manual work to keep their information up to date. It would be impossible to scale a volunteer force to service our growing user base.
The Solution:
Utilize the Azubu Module System and the Riot API to create Statistic Modules that would automatically update whenever the data changed.
Users would pull data from the Riot Database by entering their Summoner ID & Region and the app would do the rest of the work.
The solution was built in Angular and leveraged a MySQL database to store the data. An Akamai layer insured that information would be delivered in a timely manner.
Utilize the Azubu Module System and the Riot API to create Statistic Modules that would automatically update whenever the data changed.
Users would pull data from the Riot Database by entering their Summoner ID & Region and the app would do the rest of the work.
The solution was built in Angular and leveraged a MySQL database to store the data. An Akamai layer insured that information would be delivered in a timely manner.
Initial Concept
The Result
The final release included four unique modules that allowed users to view the data around most played champions, individual games, in game achievements, multi-kills and ranked game results.
Azubu League of Legends Explanation Video
The Recent Games History Module was an interactive app that allowed Users to get in depth information about the last 15 games of a Summoner.
It showed the individual statistics for every Champion in the game, a timeline that showed when key objectives were taken, the amount of key objectives each team took, and a timeline chart that compared the performance of the two teams.
The time line chart had 10 customizable views including GPM, CSPM, KAPM, WPM, XPM, and their totals.
It showed the individual statistics for every Champion in the game, a timeline that showed when key objectives were taken, the amount of key objectives each team took, and a timeline chart that compared the performance of the two teams.
The time line chart had 10 customizable views including GPM, CSPM, KAPM, WPM, XPM, and their totals.
The Summoner History Module showed a Users Most Played Champion and Multi-Kill History from the past 30 days.
We limited the window to 30 days in order to show what the Users Current Meta was, as opposed to having the data skewed my historical outliers.
The App also pulled Champion Portraits to add more flavor.
The metrics for the modules were tracked using Google Analytics Event Function. During the first month they resulted in several million interactions and held steady in the following months.
