
Building Technology That Reaches Everyone: The Case for Inclusive Civic Platforms
A civic platform built for recent smartphones, fast data, and English readers quietly serves the people who already have the most access, and leaves out the very people civic participation is meant to include. Real inclusion is not a ramp added at the end but a design decision made at the start: mobile money as a first-class path, lightweight pages for weak networks, USSD for the feature phone, and the languages people actually think in.
There is a quiet assumption built into much of the technology we use every day, and it is worth dragging into the light because so much depends on it. The assumption is that the person on the other end of any digital experience has a recent smartphone, a steady and affordable data connection, and reads comfortably in English. For a very large part of the world, and a very large part of Africa in particular, every piece of that assumption is wrong. And when a civic platform is built on top of it, the platform ends up serving the people who already have the most access while quietly leaving out exactly the people that civic participation is meant to include. This essay is about why that gap exists, why it matters so much more for civic technology than for ordinary apps, and what genuine inclusion actually demands from those of us who build.
Let us state the problem plainly, because vagueness here lets everyone off the hook. A petition that can only be signed on a smartphone with good data is not a petition for everyone. It is a petition for the connected minority, dressed up in the language of universal participation. A donation flow that requires a bank card and reliable bandwidth is not a donation flow for the market trader counting her takings in cash and mobile money, or the rural farmer whose nearest reliable signal is a walk away, or the grandmother who has used mobile money for years but has never owned an app and never will. If the stated goal is genuine civic participation, then the question of who can actually reach the platform is not a secondary feature to be polished later. It is the entire substance of whether the goal is being met at all. A tool for civic good that only the already-advantaged can use is not, in any meaningful sense, a tool for civic good. It is a tool for the advantaged that happens to be pointed at good causes.
Inclusion, understood properly, is not charity and it is not an act of generosity toward an unfortunate minority. It is a design decision, and a fairly demanding one, made at the very beginning of how a thing is built rather than added on at the end. It is tempting to think of accessibility as a ramp built onto a finished building, a modification that makes an existing structure usable by a few more people. But that metaphor undersells what real inclusion requires. Real inclusion changes the shape of the building itself. It changes what you build, not merely how you decorate what you have already built, and pretending otherwise produces platforms that technically have an accessibility feature while remaining, in practice, closed to the people who needed it.
Consider the single most powerful tool for financial inclusion that the African continent has produced: mobile money. Across Africa, vastly more people transact through mobile money than through bank cards, and for an enormous number of them it is not one option among several but their entire financial life, the only formal money system they have ever used or trusted. A platform that treats mobile money as a first-class, frictionless way to give, designed around how it actually works and how people actually use it, rather than bolting it on awkwardly beside card payments as though cards were the real method and mobile money the afterthought, immediately becomes reachable by tens of millions of people who were otherwise locked out. That is not a marginal optimization to be celebrated in a product update. It is the difference between a platform for the connected few and a platform for the many, and the choice between those two is made in the earliest architectural decisions, long before a single user arrives.
The same logic applies to the network itself, and here too the gap between assumption and reality is wide. A great deal of the continent connects over 2G and 3G, on data that is bought carefully and consciously, megabyte by megabyte, by people for whom a wasted load is a wasted cost they can feel. To such a user, a page that is heavy with images and scripts and slow to load is not merely an inconvenience to be endured with a sigh. It is, quite literally, a closed door, because the page may never finish loading at all, or may consume more of their limited and expensive data than the task was worth. A lightweight, text-first experience that loads quickly on a weak signal and respects how precious each megabyte is becomes, for a great many people, the precise difference between participating in civic life and being shut out of it. Building that lightness is not a compromise on quality. It is a recognition of who the platform is actually for, and a refusal to mistake the experience of the well-connected for the experience of everyone.
There is a further piece of this that the most enthusiastic builders of sophisticated apps tend to forget entirely, and it deserves to be said clearly: the feature phone is not the past. It is the present, the current and primary way that millions of people interact with the wider world. And the technology that brings the digital world to those phones, the unglamorous short codes known as USSD that people dial to check a balance, buy airtime, or send money, is one of the most quietly democratic technologies ever deployed. It needs no app, no smartphone, no data bundle, and no literacy in a foreign interface. It works on the cheapest handset ever made, on the weakest network in the most remote village, in the hands of someone who has never touched a touchscreen. To imagine signing a petition by dialing a short code, or making a donation to a cause through a simple USSD menu and a mobile money confirmation, is to imagine civic participation that finally reaches the people who have always been talked about in development conversations but rarely actually included in the tools those conversations produce. A platform that takes USSD seriously is a platform that has decided, concretely, that the farmer and the trader and the grandmother are not edge cases to be served eventually but central users to be served now.
Language belongs in this same conversation, because access is not only about devices and networks but about whether a person can understand what is in front of them in the words they actually think in. A civic platform that exists only in English, on a continent of extraordinary linguistic richness, is asking a great many of its intended users to participate in their second or third language, or to not participate at all. Meeting people in Twi, in Ewe, in Hausa, in Dagbani, in the languages of their daily lives, is not a cosmetic nicety to be added if time allows. It is a recognition that civic dignity includes the right to engage with public life in your own tongue, and that a platform serious about reach must eventually be serious about language too. The work is real and it is gradual, but the direction is not optional for anyone who means what they say about inclusion.
It is worth being honest that building this way is harder than the alternative. It is easier, faster, and cheaper to build for the smartphone-owning, well-connected, English-reading user, because that user tolerates heavy pages, expects app-based flows, and asks for nothing unusual. Building for everyone else means more constraints, more testing across more conditions, more careful thought about every kilobyte and every step, and more patience. But the difficulty is precisely the point. The easy version of a civic platform reproduces, in software, the same exclusions that already exist in the world, handing the most access to the people who already have the most of everything else. The harder version does something genuinely worthwhile: it uses technology to widen the circle of who gets to participate, rather than to draw that circle more tightly around the already-included. One of those is worth a builder's effort. The other is just convenience wearing the costume of progress.
This is the standard we hold ourselves to, imperfectly and as a direction of travel rather than a finished achievement. The measure of a civic platform is not how elegant it looks on the newest phone in the best coverage in the largest city. It is whether the person with the oldest handset, on the weakest signal, in the most overlooked place, reading in the language they grew up speaking, can still take part fully in the civic life the platform exists to enable. Anything less than that aspiration is a platform that has quietly decided some people matter more than others, whatever its mission statement says. We would rather do the harder work and mean it, because the people most often left out by technology are very often the people whose participation in civic life matters most, and building so that they are finally included is the entire reason a civic platform is worth building at all.
