The problem.
At FiveRivers Technologies I built React Native apps for international clients, from writing the code to preparing production releases.
Cross-platform apps often need things the shared code can’t do on its own: device features, outside services, local storage, and different release steps for iOS and Android.
How I approached it.
Shared screens
I built and maintained React Native apps from the first screens to production release, on both iOS and Android.
Native modules
I wrote native modules in Kotlin and Swift to give the React Native code access to device features.
Services and offline data
I added Firebase login, cloud functions, analytics and push notifications, and used SQLite so apps worked offline. Not every client app used all of these.
What I built.
- React Native apps for iOS and Android
- Native modules in Kotlin and Swift
- Firebase integrations
- Offline support with SQLite
- Releases and maintenance
I worked on these apps from development through release and later maintenance, including native modules and offline support.
Based on my role at FiveRivers Technologies. Client apps are not named.
What I learned.
Shared code doesn’t remove the platform work. Native modules, local data and each store’s release steps still need their own attention.
If your React Native app needs a native feature, a new integration or offline support, I can scope it and build it into your existing app.