Your School or Clinic Doesn't Need a Full App. Here's What You Actually Need.

A secondary school principal in Kericho called us last month. He had seen a competitor's school app and felt pressured. 'Do I need one?' he asked. 'Parents are asking for it.' His budget was tight, maybe KES 200,000 for all his digital needs for the year. A proper native app for Android and iOS would eat that whole budget and then some. But his problem was real: parents needed timely fee reminders, exam timetables, and a way to check balances without calling the office.

We told him about a third option. Not just a basic website, and not a full-blown app. Something in the middle that works perfectly for Kenya's mobile-first reality. It's called a Progressive Web App, or PWA.

The Problem with 'App or Nothing' Thinking

Many Kenyan organizations—schools, clinics, small agribusinesses—get stuck between two expensive choices. On one side, a basic website that sits there like a digital brochure. It doesn't send alerts, doesn't work offline, and feels clunky on a phone. On the other side, a native mobile app. Building one properly means two separate codebases (one for Android, one for iOS), ongoing maintenance, app store fees, and a development bill that starts around KES 500,000 and goes up fast.

But look at how Kenyans actually use the internet. According to the Communications Authority of Kenya's latest sector report, there were 76.7 million active mobile SIM subscriptions by mid-2025. That's a penetration rate of 146%. The internet is in people's pockets. Yet, over half of those devices are still basic feature phones. Even among smartphones, people are counting megabytes and dealing with spotty coverage in places like Loitokitok, Bungoma, or parts of Kisii.

KES 500,000+ — The starting cost for a well-built native mobile app for Android and iOS in Kenya. A full-featured PWA often costs 30-50% less, as it's one codebase for all devices.

A PWA fits right into this gap. Think of it as your website, but upgraded to act like a local app on a user's phone.

What a PWA Actually Does for You

Let's use the Kericho school as an example. With a PWA:

• A parent visits the school website on their phone. A prompt asks: 'Add to Home Screen?' They tap 'Add.' Now an icon for 'Mountain View School' sits right next to their WhatsApp and M-Pesa icons.
• The school can send push notifications directly to that home screen icon. 'Term 2 fees reminder due Friday.' 'Class 8 parents meeting tomorrow at 10 AM.' No SMS costs, no relying on a WhatsApp group where messages get buried.
• If the parent is in an area with poor Safaricom signal, or is trying to save data, key pages—like the fee balance page or the term calendar—can still load. The PWA stores the basics on the phone itself.
• It works on any device. The same PWA runs on an Android phone, an iPhone, a tablet, or a desktop computer in the school office. One project, one codebase to maintain.

For a clinic in Nakuru, this could mean patients adding a 'Health Clinic' icon to book appointments, receive vaccination reminders, or access their medical history forms offline before a visit. The clinic saves on paper, phone calls, and missed appointments.

The Kenyan Budget Reality

Let's talk numbers. A typical informational website for a Kenyan SME might cost between KES 25,000 and KES 150,000, depending on pages and features. A full e-commerce or complex system starts from KES 150,000 and can go to KES 500,000. A PWA sits in the upper range of a complex website project because you're adding significant capability.

But compare that to the native app route. Research on the PWA market shows a strong preference for device-agnostic solutions. Why? Because building and maintaining two separate apps doubles the trouble. An update to your fee structure means pushing an update to two app stores, waiting for approval, and hoping all parents update their apps. With a PWA, you update your website once, and everyone instantly has the latest version the next time they have a connection.

When a PWA Isn't the Right Answer (And That's Okay)

We're not saying PWAs are magic. They have limits. If your organization needs to use a phone's hardware intensely—say, a delivery app that must constantly track a rider's GPS location in the background, or an app that uses the phone's NFC chip for tap-to-pay—a native app is still better.

But for probably 80% of Kenyan SMEs, schools, and NGOs, the needs are about communication, information sharing, simple transactions, and forms. A PWA handles all of that extremely well. It's a practical, budget-aware choice that acknowledges most of your audience is on a phone, often on slow or expensive data.

What to Do Next

Before you commit to any development, ask these questions:

• What is the one core task my users need to do on a phone? (e.g., Pay fees, book appointments, check a calendar)
• Do they need to do it without an internet connection sometimes?
• Would sending instant alerts save me time and money on SMS or phone calls?

If you answered 'yes' to at least two of these, a PWA is likely a smarter investment than either a static website or a native app. It's not about chasing the flashiest tech. It's about picking the tool that solves your specific problem without wasting your limited budget.

The Kericho principal decided on a PWA. For less than the cost of a single native app platform, parents now have a reliable, fast tool on their home screens. And he saved enough money in his budget to also upgrade the school's administrative system. That's the kind of practical digital step that actually makes a difference.