Loading
We have no favourite technology. We have criteria: what can be hired for in Bamako, what will still be maintainable in five years, and what holds up on your users' networks.
What your users see, served fast and legible on a modest phone.
One shared codebase across iOS and Android, publishable without starting over.
The business rules, written once and called by every surface.
Where information lives, with constraints that rule out impossible states.
Models integrated into a process, with human validation on anything irreversible.
Reproducible environments and a release that depends on no single person.
Knowing an incident is happening before the customer calls.
The third-party systems your flows actually cross.
A tool nobody else can operate turns a technical choice into a dependency. We favour what can be hired for and documented.
An architecture that assumes a permanent link fails in the field. Behaviour on a degraded network is a selection criterion, not a later fix.
We look at maintenance history and the cost of leaving before adopting a technology, not only at what it promises today.
A first conversation is enough to clarify the context, priorities and the right place to begin.