The Problem
The client ran an English education business and needed a complete digital product — not just an app, but a full ecosystem. Students needed a mobile app they could use anywhere. Learners who preferred desktop needed a web platform. The client needed an admin panel to manage content, track user progress, and update the curriculum without touching code. They had no technical team. They had one developer: me.
How I Built It
Designing One Backend to Power Three Frontends
The first decision was the most important: build a single Node.js API with a MySQL database and Prisma ORM that all three platforms — Flutter mobile, React web, and the admin dashboard — would connect to. This meant one source of truth for user accounts, learning progress, quiz results, and content. No duplicated logic, no data drift between platforms. When a user completed a quiz on mobile, their progress updated instantly on web. When the client added a new vocabulary module in the admin panel, it appeared everywhere simultaneously.
Building Three Products in Parallel
I built the Flutter mobile app first — it was the primary surface where users would spend most of their time. Then the React web platform, sharing business logic and API contracts already established. Finally the admin dashboard, which gave the client full control: adding vocabulary sets, organizing exam-prep modules (IELTS, Cambridge, GRE, GMAT, job exams), reviewing user analytics, and managing content without any developer involvement. Three codebases, one consistent experience.
The Part Most Developers Skip — Staying
Most freelance projects end at launch. This one didn't. After the initial release, I stayed. For three years. Every few weeks there were updates: new vocabulary modules, improved quiz mechanics, better analytics, UI improvements based on how users were actually using the product. This continuous iteration is what turned a good app into a platform users kept coming back to. Each update gave users a reason not to leave. Retention isn't magic — it's maintenance.
The Outcome
News Lexica grew to over 10,000 active users with a 5.0-star rating. The client didn't need to hire a technical team or manage multiple vendors — one long-term partnership covered everything. Three years in, the platform is still being actively improved. This project taught me that the best technical work isn't just building something that works on day one — it's building something that keeps working, keeps growing, and keeps earning user trust over time.
Interested in working together?
I'm open to long-term partnerships, freelance projects, and full-time roles.