Rigel
AI video app
Bare React Native; subscriptions through RevenueCat, auth and notifications through React Native Firebase.
See the productAll of them are live; store pages and details are on the Products page.
AI video app
Bare React Native; subscriptions through RevenueCat, auth and notifications through React Native Firebase.
See the productAI budgeting coach
Bare React Native; RevenueCat, React Native Firebase, and Reanimated for smooth chart transitions.
See the productCampus Q&A and community app
Expo and Expo Router; data and authentication on Firebase, interface in two languages.
See the productReact Native lets you write the iOS and Android app from one TypeScript codebase, while the screens are drawn with the phone’s own native components. For most business apps (accounts, content, forms, payments, notifications, camera) it moves faster than two separate native teams, and one team maintains it.
We use both. SoruVerse is built with Expo and Expo Router; for Rigel and LydiaVault we chose bare React Native because they needed deeper access to native modules. We decide during discovery, based on the device features and third-party SDKs the app will use.
| Expo | Bare React Native | |
|---|---|---|
| Getting started | Fast; builds and signing run in the cloud with EAS | Needs Xcode and Android Studio set up |
| Native modules | Most SDKs are added through config plugins | Direct access to native code |
| Good fit for | New products, MVPs, content and community apps | Apps that need custom native integration |
| Our example | SoruVerse | Rigel, LydiaVault |
The mobile app, web dashboard and server are written in one language, and type errors are caught at build time.
Authentication, database and notifications. We use it in SoruVerse, Rigel and LydiaVault.
One place to manage App Store and Google Play subscriptions and in-app purchases. We use it in Rigel and LydiaVault.
To ship the app in more than one language. We use it in Rigel and SoruVerse.
Animations and transitions that stay smooth on the phone. We use it in LydiaVault and SoruVerse.
File-based navigation and deep links. We use it in SoruVerse.
We talk about who the app is for, which device features it needs and the budget you have in mind.
We write down the screens, the acceptance criteria and the choice between Expo and bare React Native.
Every week you install the new build on your own phone and try it; your feedback sets the next week’s priorities.
A senior QA tests the build before release. We go through App Store and Google Play review and updates with our own apps too.
We fix the bugs that surface in this period free of charge; after that you can continue with monthly maintenance.
Timelines and budget ranges are published on our mobile app development and pricing pages; everything on this page follows the same figures.
The screens are drawn with the phone’s own components, so in most business apps users notice no difference. React Native’s new architecture has also sped up communication between JavaScript and native code. For edge cases such as heavy 3D graphics or games we recommend native development.
Yes. React Native and React share a language and a way of thinking. On Hippotenus, for example, the same team builds the web dashboard with React and the mobile app with Expo.
Yes. In Rigel and LydiaVault we manage subscriptions with RevenueCat, through the App Store’s and Google Play’s own billing.
A perpetual licence to use the software and user documentation. If you want the source code transferred to you, that is possible for an extra fee, stated separately in the quote.
In a free 30-minute scoping call we work out the app’s scope and the choice between Expo and bare React Native together.