Esports & Education · Esports Education
Squid Academy LMS
An esports academy's learning platform: Riot Games data, single sign-on, and an AI-generated front end taken to production against the existing backend.
- Focus
- SAAS, CUSTOM-WEB-APP
- Delivered
- 10 Mar 2026
Outcome
AI-generated front end mapped onto the existing LMS in stages, with the platform live for every student throughout.
What Squid Academy is
Squid Academy teaches competitive gaming to students and reports progress back to parents. That makes it an integration problem rather than a content site: player statistics pulled from the Riot Games API for Valorant, single sign-on so students arrive with the account they already play on, and a learning platform underneath holding courses and progress.
The same engagement covers the tournament platform, published separately, and the mobile app that took the academy onto Android and iOS from one codebase.
The work
Riot Games exposes a lot through their API, including tournament structures, and the useful engineering is deciding which of it a parent should actually see in a progress report. Single sign-on removes the account-creation step that loses students before the first lesson.
The learning platform holds the courses and the progress data, and stayed live throughout the front-end transition.
A decision worth recording
They arrived with a new front end generated in Lovable. Teams in that position usually do one of two things: throw the generated code away, or rebuild everything else around it. Both are expensive and neither is obviously right.
The generated interface was worth keeping. What it assumed underneath was not, because it had invented its own data model. We recommended leaving the working LMS backend alone and mapping the generated model onto the existing API instead, hiding the parts of the interface that assumed data the backend did not hold yet, and moving the remainder across in stages.
The tool wrote the interface. The engineering was in deciding what it was allowed to change underneath.
Technologies
What we built it with
- Integrations
- Riot Games API
How we built it
Mapped a Lovable-generated front end onto the existing LMS, with the platform live throughout. The new front end had been produced in Lovable and was worth keeping, but it arrived with its own data model that the existing LMS did not match. Rather than rebuild a working system to satisfy generated code, we mapped Lovable's model onto the current LMS API, hid the parts of the interface that assumed data the backend did not hold yet, and moved the rest across in stages. The platform stayed up for every student on it.
Have a project like this in mind?
Tell us what you're building. We'll show you how we'd approach it and what it would take to ship.