Mobile apps
Cross‑platform iOS & Android on React Native — one codebase, native feel. Offline‑first data, push, payments, biometrics, and store releases automated with Fastlane.
Mobile and web product engineering led by a senior tech lead with 6+ years shipping high‑load platforms for e‑commerce, healthcare, edtech and IoT. Architecture, delivery and CI/CD — one team, end to end.
Whether you need a product built from zero, a legacy app rescued, or a senior lead to steady an existing team — the engagement is shaped around the outcome, not around billable hours.
Cross‑platform iOS & Android on React Native — one codebase, native feel. Offline‑first data, push, payments, biometrics, and store releases automated with Fastlane.
Dashboards, storefronts and admin systems that stay fast as they grow. Real‑time data over WebSockets, design systems that scale, Core Web Vitals treated as a requirement.
The part that decides whether year two hurts. Domain modelling, module boundaries, state strategy, API contracts and a performance budget written down before the first sprint.
Embedded tech lead for your team: code review culture, mentoring, delivery cadence, and pipelines with ArgoCD and Fastlane so shipping stops being an event.
Eight products across five industries — from a high‑performance e‑commerce platform in London to clinical safety tooling used inside hospitals.
A high‑performance e‑commerce platform. Owned the technical direction end to end: architecture decisions, front‑end performance optimisation, and CI/CD pipelines with ArgoCD and Fastlane, while leading a cross‑functional team and keeping delivery aligned with the product roadmap.
A habit and goal‑tracking app for people set on improving their quality of life, with personalised self‑improvement recommendations. Built core features with a focus on a seamless user experience, performance optimisation and cross‑platform parity.
Lets healthcare facilities evaluate how hazardous drugs are handled at every point of interaction and benchmark practice against international safety and quality standards — then turn the recommendations into action plans that reduce exposure for staff and patients.
A patient app for a French hospital: keeping medical history in one place, managing prescribed treatment, and booking appointments with a doctor without a phone call.
A web application built so maths teachers could run lessons more effectively. Any lesson in the app can be downloaded or customised to make the material easier for children to understand.
An online learning platform of curated materials for professional education, serving learners at IBM scale.
IBM's social‑impact platform. Built out real‑time, form‑heavy interfaces on a shared component library with strict accessibility and code‑quality requirements.
Technical lead across a stream of outsourced mobile and web products. Ran direct client communication, translated vision into actionable delivery plans, and led a team of four front‑end engineers — balancing client constraints against solutions that would still hold up a year later.
Nothing in that category yet — try another filter.
No black boxes. You see working software early and often, and you always know what the next two weeks cost.
30 minutes on the problem, users and constraints. You leave with an honest read on scope and risk — free.
A written technical plan: stack, module boundaries, integrations, milestones and a fixed price per milestone.
Demo every two weeks on a real build. Code reviewed, tested and merged continuously — never a big‑bang integration.
Store submission, CI/CD pipelines, monitoring and documentation. Your repo, your accounts, your keys.
Retainer for iteration, performance work and new features — or a clean exit with a team that can carry it.
Most agencies sell you a lead and staff the work with juniors. Here the person who designs the architecture is the person who writes the hard parts and reviews every pull request.
“Scalability, performance and maintainability aren't features you add at the end. They're decisions you make in week one — and they're the difference between a product that grows and one you rewrite.”
Own strategic technology decisions for a high‑performance e‑commerce platform: lead a cross‑functional team, drive architecture for scalability and maintainability, run CI/CD with ArgoCD and Fastlane, review code and mentor, and work with product to keep the roadmap technically feasible.
Technical lead over mobile and web delivery in an outsourcing setting. Daily client communication, strategic decision‑making across projects, and a team of four front‑end engineers held to a high delivery standard.
Core feature work on Habio, a habit‑tracking consumer app — user experience, performance optimisation and cross‑platform compatibility.
Delivery on IBM programmes: IBM.org, Teacher Advisor with Watson, SkillsBuild and ChemoSafe — enterprise codebases, shared design systems, strict review.
Built the Malakoff app for a French hospital — medical history, treatment plans and doctor appointments on mobile.
Discovery calls happen within two working days. Depending on scope, engineering usually starts within one to two weeks of a signed plan — audits and architecture reviews can start immediately.
Milestone‑based fixed pricing after the architecture phase, or a monthly rate for embedded lead / team work. Either way you get the number before work starts, and it doesn't move unless the scope does.
Yes — that's a large part of the work. It starts with an architecture and performance audit: what's salvageable, what's costing you velocity, and the shortest path to a codebase your team can move in again.
Completely. Your repository, your cloud accounts, your store credentials, from the first commit. Handover includes pipelines, documentation and a walkthrough.
One. React Native gives you a shared codebase with native modules where they genuinely matter, so both platforms ship on the same release train instead of one trailing the other.
Yes. Embedded tech lead is a standard engagement: architecture, code review, delivery cadence and mentoring inside your process — including the CI/CD work most teams postpone.
A 30‑minute call, no pitch deck. You describe the product and the constraints; you leave with an honest read on scope, stack and risk — whether or not we work together.