About the client
The client runs a chain of bakeries and cafés with several outlets and uses a mobile app for customer engagement. In April 2025 it asked FiftyFive Technologies to stabilise the existing React Native app and add the digital services it was missing, starting with loyalty rewards and bookings.
An app that would not build reliably
- An outdated SDK. The app was on Expo SDK 48, several breaking migrations behind.
- Firebase conflicts. Configuration clashes caused build failures on both iOS and Android.
- Unstable pipelines. EAS builds failed and manifest errors crashed the app.
- Slow screens. Weak caching and image handling made load times long.
- Missing features. There was no loyalty or rewards programme, and authentication and user management were limited.
What FiftyFive built
A dedicated team of four FiftyFive engineers: migrated the app from Expo SDK 48 to 53, resolving more than 15 build issues; modularised Firebase services and integrated native iOS and Android push notifications; delivered a loyalty and rewards programme with a digital card and campaign banners; built an in-app booking system, secure authentication and an improved order flow; redesigned the home screen with carousels, subscriptions, shimmer loading states and faster image caching; added a store locator with map clustering; set up Jest unit testing, EAS CI/CD and Mixpanel analytics.
How the solution works
Platform upgrade
- The app now runs on React Native 0.79.5 and Expo SDK 53, reached through five consecutive SDK upgrades with releases on both platforms along the way.
- EAS CI/CD builds and ships each release, and Jest unit tests guard against regressions.
Data and services
- TanStack Query v4 manages server state over GraphQL and REST APIs, with caching that cuts repeat requests.
- Firebase services were split into modules, removing the conflicts behind earlier build failures, and native push notifications run on iOS and Android.
Customer features
- The loyalty programme gives customers a digital card and shows campaign banners.
- Customers can make bookings, sign in securely, place orders through an improved flow and find outlets on a clustered map.
Performance and tracking
- The home screen uses shimmer placeholders while content loads and caches images more efficiently.
- Mixpanel records usage so the client can track how features are used.
Technology stack
What the solution enabled
- Custom mobile app development a React Native app upgraded across five Expo SDK versions while new features shipped.
- UI/UX design a redesigned home screen with faster perceived loading.
- DevOps and cloud a stabilised EAS build and release pipeline.
- Software testing and QA Jest unit tests and release monitoring.
Business transformation
Faster load time
Build issues resolved during the move from Expo SDK 48 to 53
Expo SDK upgrades, with releases on iOS and Android
60% faster load time
After the caching, image-handling and home-screen work.
Stable builds again
More than 15 build issues resolved during the move from Expo SDK 48 to 53.
Releases continued across five SDK upgrades
On iOS and Android.
New services live
Loyalty and rewards, bookings, stronger authentication and a store locator.
FiftyFive Technologies stabilised and extended the React Native app of a European bakery and café chain whose iOS and Android builds were failing on an outdated Expo SDK and conflicting Firebase configuration. A four-engineer team migrated the app from Expo SDK 48 to 53, resolving more than 15 build issues, modularised Firebase with native push notifications, and added a loyalty and rewards programme, in-app bookings, stronger authentication, a store locator and a redesigned home screen. The modernised app loads 60% faster.
Technical questions
How do you upgrade an old Expo app without breaking releases?
For a European café chain, FiftyFive Technologies moved a React Native app from Expo SDK 48 to 53 through five consecutive upgrades, releasing on iOS and Android along the way. The team resolved more than 15 build issues, modularised conflicting Firebase services and added EAS CI/CD and Jest tests to keep builds stable.