At a company
Frello
A complete rebuild of the learning-module viewer and its backend, for better performance and code that's easier to maintain.
- My role
- Web & mobile product developer, mission led autonomously
- Period
- Since December 2025
- Context
- Frello, EdTech (learning French as a foreign language)
Stack
- React 19
- Apollo Client
- GraphQL
- Lambda
- Prisma
- Node.js
- React Native
The context
Frello is a SaaS and mobile product for learning French as a foreign language. At the core of the product is the module viewer: the building block that displays the learning modules and handles the learner’s journey, on web and on mobile.
The problem
This viewer lived in an older Next.js application, separate from the rest of the product’s code (outside the monorepo), and talked to a REST backend. The mission had two goals: improve performance and make the code easier to maintain and evolve.
What I did
- I took the viewer out of the old Next.js / REST application and rebuilt it on a modern stack: React 19 and Apollo Client on the front end.
- I set up the backend in GraphQL, on Lambda functions, with Prisma for data access.
- I moved the grading computation and the learning history (the LRS, which records what each learner does) to the server side.
- I then extended the same backend to the mobile app (React Native).
My role
I led this mission autonomously, from the web viewer all the way to its extension to the mobile app.
What it means for you
At Frello, I took over an existing product, chose the architecture and led the migration all the way to mobile. That’s the same reflex I’ll bring if your prototype or product starts to crack. And a single backend for web and mobile means less duplicated code to maintain.