Device diversity
Keep controls generous, layouts linear, text scannable, assets lean, and essential actions independent of hover, animation, or a large screen.
Mobile brief / evidence before assumptions
Communications Authority reporting describes a fast-moving, mobile-led environment that still includes different devices and access conditions. Use regulator evidence to challenge assumptions, then test the actual audience instead of treating national statistics as a persona.
Operating lanes
Keep controls generous, layouts linear, text scannable, assets lean, and essential actions independent of hover, animation, or a large screen.
Save meaningful progress, make duplicate submissions harmless, display server-confirmed state, and tell the user what is safe to do after interruption.
Confirm +254 phone handling, names, delivery or service-area needs, address structure, and whether precise location is necessary before collecting it.
BRS/eCitizen, payment, identity, messaging, hosting, and other integrations require client-owned accounts, current documentation, and a support path.
Runbook
Name the user group, task, likely devices, language responsibility, access constraints, and assistance available.
Attach current CA, ODPC, BRS, ministry, and provider material to the decisions it informs.
Include small screens, feature-limited browsers where relevant, slow responses, realistic phone data, empty balances, and support escalation.
Reopen the brief when the audience, service area, provider, payment method, data path, or release scope changes.
Coverage, smartphone use, mobile money, and digital services are planning context. The target customers, provider contracts, devices, and network behavior still need direct evidence.