01
Expo migration
Moving a legacy React Native app to Expo without blocking releases: native surface, libraries, builds and store path.
Missions
React Native, Expo and the web around them
I join product teams for a given mission: migrating an app to Expo, taking over an existing codebase, or reinforcing the team on mobile and full-stack work.
What I take on
02
Taking over an existing app
Understanding a codebase quickly, clearing technical priorities, putting structure back where the project needs it.
03
Team reinforcement
Shipping the next features with the team: mobile, web and API, from the build to the store release.
What I secure during a migration
- 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 fit the project to streamline deployments.
- Tailored choices
- Trade-offs matched to your stack, store constraints, and product cadence.
- We pick the useful Expo options together instead of a generic workflow.
- Team ownership
- Decisions, playbooks, and trade-offs are written for the internal team.
- The migration ends with a workflow your team can run without me.
How a mission runs
map
Understand the existing app
Code, native dependencies, CI and critical flows reviewed before changing anything.
Priorities and treatment order
migrate
Modernise without blocking
Expo migration when it serves the need, incompatible libraries replaced, builds secured.
An app that builds cleanly
release
Ship for real
Regular test builds, flows checked on iOS and Android, store release.
A proven release path
hand over
Leave the team in control
Commands, decisions and fallback options documented for maintenance.
A team ready for the next releases
What I delivered
CAMPING-CAR PARK
03.2024 – 09.2025
React Native · mobile lead
Expo · CI/CD · maps
- context ›
- Booking app in production, built on an ageing React Native codebase.
- action ›
- Migration to Expo: unmaintained libraries replaced, build and release pipeline configured. Then a redesign in 2025, booking and maps, with the product and back-end teams.
- result ›
- An up-to-date Expo codebase, more reliable releases and a team supported over time.
MOBIAPPS
10.2025
React Native · Expo migration
Expo · config plugins
- context ›
- Legacy React Native app to modernise.
- action ›
- Migration to Expo: native configuration, Expo plugins, dependencies and React Navigation.
VAERDICT
since 2024
Full-stack · tech lead
React · Node.js · TypeScript
- context ›
- Business web app to evolve, with an internal team.
- action ›
- Re-architecture to make it scale, tech lead of the team.
- result ›
- A more scalable codebase, a supported team.
LiNote
2023
React Native · new app
Expo · iOS · Android
- context ›
- Web communication platform with no mobile app.
- action ›
- App built from scratch: messaging, photo sharing, video calls, notifications and alerts.
- result ›
- Key features shipped on iOS and Android.
Silbo
2020 – 2022 · employee
Full-stack
Node.js · TypeScript · React · React Native
- context ›
- Web and field apps for healthcare.
- action ›
- Full-stack development, real time, production operations.
- result ›
- Apps shipped and used every day.
They talk about it
#01
“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.”
Eric
#02
“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.”
Julie
#03
“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.”
Matthieu
#04
“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.”
Thomas
#05
“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.”
Romuald
#06
“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.”
Antoine
Frequent questions
How long does an Expo migration take?
It depends on the native dependencies, the CI and the release setup. The initial review estimates the scope before any change.
Do releases have to stop during the migration?
No. The goal is to migrate while the product keeps moving, then prove the new release path on a version the team can inspect.
Can you stay after the migration?
Yes. I can keep supporting the team on new features, releases and technical follow-up.
Do you work remotely?
Yes, remotely from Nantes, with teams in France and abroad.
Contact
I enjoy joining an existing product, understanding its constraints and moving it forward with the team in place. If your app needs that kind of eye, I would be glad to talk.
- email:
- [email protected]
- linkedin:
- in/simon-boisset
- github:
- simonboisset