I Stopped Building for Trends and Started Building for Students in Malawi

I Stopped Building for Trends and Started Building for Students in Malawi

Most startup advice tells developers to focus on the latest frameworks, build for global audiences, and move as fast as possible.

I decided to start somewhere much closer to home.

I’m building Educate MW, a learning platform designed around the needs of students in Malawi.

The idea is simple: make useful learning resources easier for students to access from their phones.

I’m building Educate MW as a solo developer, but I’m also working with the MSCE Preparation Team, whose work is focused on helping students prepare for their examinations.

You can find the team on Facebook here:

Why Educate MW?

For many students, finding organised study materials is not always simple. Resources can be scattered across different places, and students may have to search through multiple platforms to find what they need.

Educate MW brings different learning resources and study tools into one platform.

The platform includes:

• MSCE and JCE study materials
• Syllabuses and past papers
• Notes and learning resources
• Quizzes and flashcards
• An educational dictionary
• Career guidance
• Student profiles and learning progress
• XP, streaks and a leaderboard
• Community and group discussions
• Voice messages in community groups
• Emi, an AI study assistant that helps students understand questions and topics

The goal isn't simply to add as many features as possible. Each feature should have a reason to exist and make studying more useful or accessible.

Why React?

The current version of Educate MW is built with React.

I previously experimented with Angular for the application, but that implementation didn't work out the way I wanted. Instead of continuing to force a technical direction that wasn't working, I decided to rebuild the application with React.

That experience taught me something important about development:

Sometimes changing your technology is better than trying to save a decision simply because you've already invested time in it.

The technology should serve the product, not the other way around.

Building as a Solo Developer

One of the most interesting parts of this project is building it as a solo developer.

That means I'm not only writing code.

I'm thinking about the product, designing interfaces, implementing features, testing them, fixing bugs, managing the project and deciding what should be built next.

AI has also become part of my development workflow.

I use AI tools to help with development, debugging, implementation and organising ideas. But AI doesn't decide what Educate MW should become.

The product decisions still come from understanding the problem, testing the application and listening to the people the platform is meant to serve.

Building for the Environment Users Actually Have

Educate MW is designed with mobile users in mind.

That matters because a product built for students in Malawi cannot simply assume that everyone has a powerful phone, unlimited data or a fast internet connection.

The experience needs to be simple, responsive and practical.

That influences many of the decisions I make while developing the platform.

What I'm Learning

Educate MW has taught me that building a useful product is very different from simply building an application.

You can have good code and still build the wrong thing.

You can have an impressive interface and still fail to solve the actual problem.

And you can use powerful AI tools and still need to make hundreds of product decisions yourself.

For me, the most important part is continuing to improve the product based on what students actually need.

Educate MW is still being developed, and there is a lot more I want to improve.

But the direction is clear:

Build useful technology for students in Malawi, make it accessible from the devices they already use, and keep improving it one feature at a time.

You can try Educate MW here:

This is what building from Malawi looks like for me.

Not waiting for the perfect team.

Not waiting for the perfect technology.

Just starting with a real problem and building.