React Native to Expo migration.

Type: homepage
Language: en-US
Canonical URL: https://simonboisset.com/en

I help your team migrate to Expo/EAS without blocking releases or losing ownership.

What I secure during an Expo migration.

Most migrations get stuck in the same places: native compatibility and EAS/store deployments. I handle both in the same diagnosis.

Native surface: Dependencies, permissions, config plugins, prebuild, and modules that can block Expo. You get a compatibility map and clear replacement or fallback options.
EAS and QA deployments: EAS Build, Submit, Update, channels, CI, and QA distribution. I advise your team on the options that actually fit the project to optimize deployment phases.
Tailored guidance: Tradeoffs matched to your stack, store constraints, and product cadence. I choose the useful Expo options with you instead of applying a generic workflow.
Team ownership: Decisions, playbooks, and tradeoffs are written for the internal team. The migration ends with a workflow your team can operate without me.

Mission feedback

Concrete notes from React Native, Expo, and legacy mobile missions.

Eric: We started from a fairly complex legacy codebase. Simon took over the project, brought structure back to the whole stack, and still supports us day to day.
Julie: Simon built our React Native app from scratch while keeping it aligned with the existing web app. In a few weeks, we had reminders, messaging, photo sharing, and video calls.
Matthieu: We had been dragging this Expo migration for more than a year. Simon reassured us, delivered it in two weeks, and we were able to publish a clean version afterwards.
Thomas: Simon joined a project where frontend, backend, mobile, and infrastructure were all tied together. He quickly understood how everything fit together, which saved us a lot of back and forth.
Romuald: Simon migrated three of our React Native apps to Expo after more than 9 years of maintenance. The migration went smoothly, and we are already seeing the benefits: much faster upgrades and finally reliable builds.
Antoine: Our mobile codebase had become too complex: too many special cases, too many dependencies, and not much certainty left. Simon helped us regain control and put a clear structure back in place.

From your current app to an Expo release

You keep the product moving. I remove the Expo blockers, prove the release path, then hand the workflow back to your team.

Find what blocks Expo: I review the native modules, app config, CI, and store constraints before changing the code. Outcome: Risk map, treatment order, and service quote
Project migration: I set up the Expo project and config files, replace libraries that conflict with the ecosystem, then secure the builds. Outcome: Expo app that can build cleanly
Run a real release path: I validate EAS, QA channels, versions, and store rules on a release your team can inspect. Outcome: QA to store path ready
Give the team control: I document the commands, decisions, and rollback options used during the migration. Outcome: Team ready for the next releases

Related links
Website: https://simonboisset.com/en
Blog: https://simonboisset.com/en/blog
Legal documents: https://simonboisset.com/en/docs
Schedule a call: https://cal.eu/simon-boisset/meet-simon