Experience and journeys
Onboarding, authentication, local app lock, permissions, navigation, forms, empty states and touch behaviour.
Mobile applications
Mobile applications designed for real devices.
For consumer products, companion applications and operational tools that need to behave predictably across iOS and Android.
Real application behaviour
Mobile quality is decided by situations that do not appear in a static screen design: cold start, background recovery, session restoration, biometrics, permissions, loss of connectivity, keyboards, different screen sizes and store publication.
I account for those conditions from the start. React Native and Expo provide a shared product foundation while platform differences remain deliberate, testable and visible.
Scope
Scope of work
Cross-platform implementation
Shared screen foundations, state management, local data, API integration, localisation and layouts adapted to different devices.
Device integration and publication
Native configuration, iOS and Android capabilities, signing, TestFlight, build automation and production-only diagnostics.
Project fit
A strong fit when…
The product uses device capabilities
It relies on sessions, local state, notifications, biometrics, camera, files or other operating-system features.
The same product needs to work on two platforms
The experience should remain coherent without pretending that iOS and Android are identical.
Build and publication issues are blocking progress
Native configuration, signing, capabilities or production-only failures need systematic ownership.
The application must connect to an existing system
Authentication, API contracts, legal consent gates and backend state need to form one predictable journey.
Process
Clear direction. Working increments. A controlled release.
The cadence changes with the product, but the sequence does not: reduce risk first, then build and prepare the system for real use.
Direction
Define the user, problem, business rules, constraints and the smallest scope that creates real value.
Solution design
Design the product structure, key states, interaction model, data flow and technical boundaries.
Working increments
Build complete slices of the product — from interface and data to integrations — instead of postponing system integration until the end.
Validation and release
Verify critical journeys, failure handling, performance, security, environments and the actual publication path.