Services · Mobile app development · School apps
Codeeo provides school app development in Saudi Arabia for private school groups, international school networks and education companies running campuses across several regions. We build one parent app, one staff app and one group admin portal covering attendance, transport, fees, report cards and staff communication, designed around Ministry of Education reporting, the Personal Data Protection Law and Saudi payment methods. Each campus keeps its local rules while the group sees everything in one place.
Learning content, online classes and tutoring belong to other platforms. This app handles the operational side of a school: who is present, who is on which bus, what each family owes and what parents need to know today. For a group, it is also the one place where leadership can see how every campus is doing on those basics.
200+ companies servedFrom a first store to an ADX listed developer
Platform capabilities
Private education in the Kingdom is licensed and supervised by the Ministry of Education, with regional education administrations overseeing schools in each area, and school quality evaluated by the Education and Training Evaluation Commission. A school group operating in Riyadh, Jeddah, the Eastern Province and smaller cities has to satisfy the same national rules everywhere while dealing with very different parents, buses and fee structures in each place.
The capabilities below are designed for that structure. They separate what the group sets once, such as data policies, branding, payment providers and report card templates, from what each campus controls, such as timetables, routes and announcements. That split lets a new campus go live by configuration rather than by another development project, and lets the group compare attendance, collections and parent engagement across every site without asking principals for spreadsheets.
The platform models group, region, campus, section and class, with permissions at each level. A regional director sees the campuses in their region, a principal sees one campus, and a teacher sees only their classes. New campuses inherit group settings and add their own local details in an afternoon of setup.
New campuses launch on the existing platform, not a new build.
Schools affiliated with the Ministry of Education submit pupil records, attendance and results through Noor. We found no public Ministry API for third party software, so the platform produces validated exports in the Noor template formats for each campus registrar, and we will build to an official integration if the Ministry grants your group one.
Registrars across every campus report from the same clean data.
Children's and parents' records are personal data under the Personal Data Protection Law, supervised by SDAIA. The platform records the purpose of each data field, consent where needed, retention periods and access logs, and supports requests from parents to see or correct their data. Hosting inside the Kingdom is planned from the start.
Privacy obligations built into the platform, not a policy document.
Families pay tuition, transport and other charges with mada, Apple Pay, cards or STC Bank through a licensed gateway, and SADAD bill numbers can be issued where your finance team prefers them. Each campus collects into the right account, and group finance sees collections and arrears across the Kingdom.
Fee collection comparable across every campus.
Fee invoices and receipts are generated in a structure that can feed ZATCA compliant e-invoicing through your accounting system or a certified provider. VAT treatment of school fees depends on the family and the service, so your tax adviser sets the rules and the platform applies them consistently.
Invoices that finance and the tax adviser can stand behind.
Parents sign in with a mobile number and one time code, and the school links them to their children after checking documents at admission. Where your group qualifies for Nafath access through an approved provider, verified national identity sign in can be added for sensitive actions such as changing authorised collectors.
The right parent sees the right child, every time.
Private schools run their own buses or contract operators in each city. The transport module handles routes, stops, driver and supervisor assignments, live tracking and boarding records per campus, with a group view of fleet use and punctuality. It suits schools that run buses outside the Ministry's public school transport arrangements. Driver and supervisor records sit with each campus.
Every campus fleet visible to group operations.
Groups often teach the national curriculum on some campuses and British, American, IB or community board programmes on others. Report card templates are set per curriculum in Arabic and English, and every campus publishes on its own date with the same parent experience.
One parent app whatever the curriculum.
Group leadership can send policy updates to every campus, regional teams to their schools, and principals to their own staff, with read tracking. Emergency notices about closures or remote study days announced by the authorities reach staff, drivers and parents in each affected region only.
Messages reach the right region without noise everywhere else.
Owners and boards see attendance, collections, enrolment, parent app activation and open support requests by campus and region. The figures come straight from daily operations rather than monthly reports, so problems at one campus show up early.
Decisions based on live data from every campus.
Who this is for
Saudi private education is expanding under Vision 2030, with groups opening new campuses, investors buying existing schools and international brands entering the Kingdom. Each needs a school app that works the same in Riyadh as it does in Jeddah, Dammam, Makkah or Madinah, while respecting regional differences in parents, transport and curriculum. These are the four operators we design the platform around. Many operators fit more than one profile, and the platform is planned so that is never a problem later.
A group that started in one city and now runs campuses in three regions often has three different ways of doing everything. We consolidate them into one platform with shared policies and local control, migrate each campus in turn, and leave the group with a template for every campus it opens next.
Consolidate first, then grow on the same platform.
When an investor acquires schools with different systems, the first need is visibility: attendance, collections and enrolment in one view. We can start with a group dashboard fed by each school's existing data, then move schools onto the full parent and staff apps over the following terms.
Visibility across acquired schools comes before full migration.
An international brand opening Saudi campuses needs an app that matches its global standards while meeting local requirements on data, payments, Arabic and Ministry reporting. We build the Saudi platform to sit alongside group systems abroad, with data for Saudi pupils kept in the Kingdom.
Global brand, Saudi rules.
Some groups teach the national curriculum on one campus and a community board on another, with different parents, languages and calendars. The platform handles both under one group, with curriculum specific report cards, calendars and notice templates, so each parent body gets an app that feels made for them.
Two curricula, one group, one app.
How we work together
Groups usually begin with a fixed scope platform and pilot campus, then move to a rollout phase priced per wave of campuses. Larger operators keep a dedicated team for the long term, working with their own IT and academic leadership. Our team of more than 80 people across Riyadh, Dubai and Karachi has delivered more than 200 projects in the UAE and the US. In-person workshops happen in Riyadh; campuses in other cities join by video. Every phase has its own written scope, and the group can pause between waves to absorb change before the next set of campuses moves over.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
We build the apps in Flutter or React Native with a web admin portal and a multi-tenant backend designed for many campuses. Hosting, security controls aligned with NCA guidance, payment gateways and integrations with your finance and student systems are chosen with your IT team. Each tenant is isolated, so one campus's data never appears in another's view, and backups, monitoring and release processes are documented for your own team to inspect and, if you choose, to run.
01Mobile
02Data and cloud
03Marketing and tracking
The platform has to separate group rules from campus control.
A single school can live with a simple app. A group needs regions, campuses and roles, shared policies, per campus payments and reporting, and a way to open new campuses by configuration. We design that structure first, then build features into it, so the tenth campus is as easy to launch as the second. We also plan for campuses that join through acquisition with their own legacy data, so the structure copes with imperfect records as well as clean ones.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
Swift
Kotlin
Flutter
React Native
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio