Schools in Laos were running competitions, class assignments, lesson prep and parent communication on paper and in scattered files. MOHA Software built them a single online learning platform with online exams, an electronic library, and a contact book that reaches parents by SMS. A team of 10 delivered it in six months.
This write-up covers what the schools needed, what we shipped, and the engineering questions that come with a school platform in a Lao-language market. If you are planning something similar, the last section is a checklist you can use before you talk to any vendor, including us.
| Client sector | Schools |
| Country | Laos |
| Product | Web app with a React Native mobile client |
| Team size | 10 |
| Duration | 6 months |
| Stack | Angular, Java Spring Boot, MySQL, React Native, SMS integration |
What the schools were dealing with
The problems fed into each other.
Admin work was expensive. Organizing competitions, assigning teachers and students to classes, and keeping contact books current took a lot of staff time and money.
Records lived in too many places. Management documents were spread out, so compiling a report or finding a student's history meant searching several sources by hand.
Teachers lost hours to prep. Writing lessons and building exams for each class ate into teaching time.
The brief was one platform that school staff, teachers, students and parents could all use, with the data held centrally instead of in each school's filing cabinet.
What we built
The platform has four parts.
- Online learning. Teachers publish lessons and course material, and students study online.
- Online testing. Teachers build exams and run them in the system instead of on paper. The same module handles school competitions.
- E-library. An electronic library that teachers and students can search, so materials are no longer tied to a shelf or a shared drive.
- Electronic contact book. School management data sits in one cloud database. An SMS integration sends updates to parents and students and replaces the paper contact book.
The interface is in Lao throughout. The published screens show student profile pages (photo, student ID, class) and a message inbox with search, which is where the contact book lives on a phone.
Engineering for a Lao-language school system
A lot of EdTech write-ups skip the local details. For Laos, three of them shape the build.
Lao script changes how text behaves
Lao has its own Unicode block, and it breaks an assumption most web stacks make. The W3C's Lao gap analysis puts it plainly: Lao doesn't use spaces between words, but it does wrap text at word boundaries, so inter-word spaces can't be used for line breaking.
That affects the UI, because long labels and lesson text need proper line breaking rather than browser defaults. It also affects search. The MySQL reference manual notes that the built-in full-text parser uses white space to find where words begin and end, and that its ngram parser targets Chinese, Japanese and Korean. So for an e-library in Lao, you can't assume the database's default full-text search will find words correctly. Search has to be designed and tested with real Lao content from the start.
Not every parent has a smartphone with data
World Bank figures for Laos show internet users at about 66% of the population in 2024. Put the other way, roughly a third of people were not online. A contact book that only works inside an app would miss many of the parents it exists for.
SMS reaches any phone, needs no install and no data plan, and parents already know how to read it. The trade-offs are real: a per-message cost that grows with the number of families, plain text only, and delivery that depends on local carriers. For a school contact book, reach usually wins that argument.
Many roles, one database
A school platform has at least four kinds of users (administrators, teachers, students, parents), and each sees different data. The Laos Edu solution centralizes management data in the cloud so staff can organize teachers and students in one place.
School data is relational by nature: schools, classes, teachers, students, enrollments, exams and results. MySQL fits that shape well, and strict schemas make reporting across classes and terms straightforward.
What the stack gives a platform like this
The published stack is Angular on the web, Java Spring Boot on the backend, MySQL for data and React Native for mobile. Each piece carries trade-offs worth knowing if you are scoping your own build.
Angular is opinionated about structure, with modules, services, dependency injection and a built-in forms library (see the Angular overview). Back-office screens full of forms and role-based views benefit from that consistency when several developers work in parallel. The cost is more boilerplate than a lighter framework.
Spring Boot is a common choice for systems with many permission rules, and Spring Security covers authentication and role-based authorization. It uses more memory than a Node.js or PHP service, which matters if hosting budgets are tight.
React Native gives one codebase for Android and iOS (React Native docs). Pairing it with Angular on the web means two front-end frameworks, so web and mobile UI code is not shared. That is a common and reasonable split, as long as you staff for it.
The team
Ten people over six months. Two of our other published education projects ran with smaller teams. Hachi:um, an online teaching and cloud data platform, took a team of 6 about five months. The COMY language learning LMS ran with 1 PM, 2 backend developers, 1 frontend developer, 1 QA engineer and 1 UI/UX designer. Laos Edu had a wider scope than either, with a mobile client and an SMS integration on top of the web system, and the team was sized to match.
Results
The published case study describes what the platform replaced: paper contact books, scattered management documents, and manual lesson and exam prep. It does not report measured results such as time saved or adoption figures, so we don't quote any here.
What we can describe is the change in workflow. Exams and competitions moved from paper into the system. Teaching materials moved into a searchable library. Student and teacher records moved into one database. Parents started getting school updates by SMS instead of through a paper book carried home.
If you're planning a similar platform
These are the questions we would want answered before writing code for a school platform in an emerging market. Use them with any vendor.
- Which languages must the UI, content and search support? Test line breaking and search with real content, not placeholder text.
- How many parents and students have smartphones with data? If the answer is "not all", plan an SMS or voice channel and budget for per-message costs.
- Have you listed every user type and what each may see? Get this signed off early, because changing a permission model late is expensive.
- What must an online exam prevent (answer sharing, time overruns, lost submissions on a weak connection), and what is acceptable?
- Who owns the student data, where is it hosted, and who can export it if you change vendors?
- Who maintains the system after launch, and how do new school years, classes and teachers get loaded each term?
Related work
More of our education work is on the education industry page, and our post on EdTech software development outsourcing, from LMS to AI tutors covers how buyers scope these projects.
A platform like this rarely stops at version one. New school years, new modules and new integrations keep coming, and that is where a long-running offshore development center in Vietnam makes sense.
Building an education platform?
Contact us to discuss your project. Tell us about your users, languages and constraints.
