AtlasLingua

AtlasLingua is a real-world translation platform for English and Moroccan Darija. It is the largest project I’ve worked on, involving frontend, backend, data, and ongoing maintenance. Beyond translation itself, it includes many of the same building blocks found in real production systems.

It started as an MVP during my time in the ALX Software Engineering program and later evolved into a public application used by real users. The platform now receives around 100–200 visitors per day and has already processed hundreds of thousands of translations.

After completing the initial MVP, I decided to treat AtlasLingua as a real product rather than a school project. I deployed it publicly, collected feedback from users, and continuously iterated on both the user experience and the translation quality. Over the past year and a half, I’ve actively maintained the platform, improved translations, optimized performance, and refined the overall experience as the user base grew.

The usage data below reflects real engagement and confirms that AtlasLingua is addressing a real need. These numbers continue to guide how I prioritize future app improvements.

*Recent usage data showing consistent daily traffic and long session durations.

Key challenges

Improving translation quality

One of the biggest challenges was translation accuracy. Darija is mainly a spoken language, has many variations, and poorly supported by traditional translation systems.

To improve results, I spent a lot of time testing different language models, refining prompts, and adjusting how context is handled. Real usage data helped me see where translations failed and where they worked well, which made each iteration more effective. (A more detailed explanation of how I tackled this is available in the case study.)

Ownership & responsibility

AtlasLingua has been built and maintained entirely by me. Being a one-person team meant handling everything end to end: product decisions, frontend and backend development, deployment, performance optimization, and ongoing improvements.

This level of ownership pushed me to think beyond features and focus on reliability, scalability, and long-term maintainability.

Performance and scalability

As usage grew, performance became more important. I optimized both the frontend and backend to keep the app fast and responsive.

This included reducing bundle sizes, adding lazy loading where possible, and improving API performance. These changes made the application smoother, even as traffic increased.

What I’ve learned

Project management and discipline:

Working on a project of this size taught me how important focus and consistency are. I had to plan my work, stay disciplined, and keep pushing the project forward over a long period of time.

Skill growth and learning:

This project challenged both my existing skills and my ability to learn new tools. I worked with new technologies under real constraints, which helped me become more confident and adaptable as a developer.

Want to go deeper?

This page focuses on the product and its impact. If you’re interested in the technical decisions, challenges, and how the system evolved internally, I wrote a detailed case study covering the architecture, trade-offs, and lessons learned.

👉 Read the full case study