Design for Billions: Building for Users Who Can't Read
Design for Billions: Building for Users Who Can't Read
773 million adults worldwide cannot read or write. Most ed-tech platforms design for university graduates. We designed for everyone.
The Literacy Assumption Problem
Every button label, every instruction, every error message — standard software assumes literacy. This silently excludes more than 10% of the world's adult population from digital education tools.
At GetSmart, we asked: what if we designed for the hardest use case first?
Our Design Principles
1. Visual-First Navigation
Icons and images carry meaning before words. Every action in GetSmart has a visual equivalent that communicates without text.
2. Voice-Guided Flows
Audio instructions guide users through complex processes. No reading required to complete enrollment, earn an award, or receive credentials.
3. Progressive Complexity
Users start with the simplest possible interaction. Complexity is introduced only as familiarity grows.
4. Peer-Based Verification
Community members can verify each other's skills without written documentation — using video, demonstration, and vouching.
Why This Matters for the Token Economy
When you design for non-literate users, you build something more accessible for everyone. The same design that works for a rural agricultural worker in Kenya works beautifully for a busy professional in New York who doesn't want to read long instructions.
Inclusion isn't charity — it's good design.
GetSmart is hiring designers passionate about inclusive technology. Get involved.