Orda Africa / 2023 - 2025
One codebase. Many devices.
Device-integrated Android across multiple environmentsRestaurant merchants needed one coherent app even when the underlying hardware, device SDKs, certification requirements, and behaviour changed from one terminal to the next.
03
RoleSenior Android Developer
DomainHospitality merchant app
PlatformAndroid, multi-device
AssuranceCompliance delivery support
ABOUT THIS CASE STUDYThis account stays at the product and system level to respect customer, employer, and platform confidentiality.
01
THE CONSTRAINTHardware differences should not become product differences.
I led Android development across multiple terminal environments. Reusable device-integration and transaction modules gave the merchant application a consistent way to represent state while keeping the details of each device SDK isolated.
02
THE TRANSACTIONHardware is part of the product.
Device-integrated work involves more than invoking an SDK. The experience has to account for device behaviour, physical interaction, errors, recovery, operational support, and the certification expectations around secure transactions, including EMV-capable flows.
03
THE EXPERIENCELet the real-world context shape the feature.
I delivered a tipping flow with clerk attribution so gratuity could be added during payment and associated with the person providing service. The feature required coordination across Android, backend, QA, and operations through rollout.
ENGINEERING PRINCIPLES
What guided the work.
- 01Abstract device behaviour, not product meaning.
- 02Design recovery paths with the same care as the happy path.
- 03Treat compliance and operational readiness as product requirements.
OUTCOMEA more maintainable Android codebase that supported multiple terminal environments, compliance delivery work, and restaurant-specific features from one product surface.