Mobile app foundation in Expo and React Native with Face ID, push and store publishing
A client app in Expo and React Native, ready to connect to your API: password and Face ID or fingerprint login, a secure session, push notifications that open the right screen, notices, finger-drawn signatures, document upload and build profiles for the app stores.
Every client app needs the same things before its first business screen: a secure session, biometrics, notifications, documents, signatures and builds for the app stores. This Expo React Native app starter covers that part for iPhone and Android and connects to your API, so your team can start with the screens that make your product different.
Who it is for
Agencies and teams that build end-customer apps, service companies that want their own app connected to their system, and web developers who want to take their product to mobile.
What an Expo React Native app starter solves
- Repeated work. Login, biometrics, notifications and builds are the same in almost every app.
- App store requirements. The production build and the encryption declaration are already set up.
- Weak sessions. The session is kept in the phone's secure storage and ends if the server invalidates it.
What it does
- Signs users in against your API, with first-time access and password recovery by six-digit code.
- Locks the app with Face ID or fingerprint, tied to the session: the lock is turned off when the session ends and offered again at the next sign-in.
- Sends push notifications to iPhone and Android through Expo's service, without storing Apple or Google keys on your server.
- Opens the right screen when a notification is tapped, and shows notifications while the app is open too.
- Registers the device at sign-in and removes it at sign-out.
- Shows service notices without repeating the ones already seen.
- Captures a signature drawn with a finger, uploads documents from the gallery or the files app and copies data to the clipboard.
- Includes tab navigation, build profiles with automatic versioning and automatic submission to App Store Connect.
Benefits
- Your team spends its time on the business screens.
- You publish under your own name, with your own accounts.
Industry context
General industry data with its public source. These are not results of this product.
- 99.4% of Spanish households had a mobile phone in 2026. Source: INE (Spain's National Statistics Institute), "Survey on Equipment and Use of Information and Communication Technologies in Households, 2026", 2026.
What you get with each license
Price upon request, depending on license type and scope. Integration support and maintenance are contracted separately.
- The code of the app foundation, as the starting point for your product's app, with sample screens you can keep or replace.
- Documentation to connect it to your API and build it with your accounts.
- A warranty against defects for the agreed period.
- Everything above, with the right to adapt it and maintain it with your team.
- The right to integrate the asset into a commercial product of your own, identified in the contract.
- The right to distribute it to your customers as part of that product, without requesting authorization for each installation and with no limit on end customers, unless otherwise agreed.
- It does not include reselling or sublicensing the asset on its own.
- It is not exclusive, unless otherwise agreed.
- Maintenance, support and adaptations are contracted separately.
Technical specifications
Language and runtime: TypeScript 6.0 on React Native 0.88.
Frameworks: Expo SDK 58 with Expo Router, React Native 0.88 and React 19.3.
Database: No database of its own. The session is kept in the phone's secure storage and the data comes from your API.
Operating systems: iPhone with iOS 16.4 or later and Android 7.0 (API 24) or later, the minimum versions declared by Expo SDK 58 and React Native 0.88.
Interface languages: Spanish.
Required infrastructure:
- An HTTP API with token authentication.
- Expo, with EAS Build, EAS Submit and its push notification service (requires your own account).
- Firebase Cloud Messaging for notifications on Android (requires your own account).
- Apple Developer Program and Google Play Console (require your own accounts).
Private deployment: The app only connects to your API. Push notifications go through Expo's service and through Apple's and Google's, and builds and app store submissions use Expo's services.
Main libraries:
| Library | Version | License |
|---|---|---|
| expo | 58.0.21 | MIT |
| react-native | 0.88.1 | MIT |
| react | 19.3.0 | MIT |
| expo-router | 58.0.28 | MIT |
| expo-local-authentication | 58.0.2 | MIT |
| expo-notifications | 58.1.8 | MIT |
| expo-secure-store | 58.0.2 | MIT |
| expo-image-picker | 58.0.10 | MIT |
| expo-document-picker | 58.0.5 | MIT |
| react-native-svg | 15.16.0 | MIT |
| react-native-view-shot | 6.1.1 | MIT |
Dependencies with specific license terms:
- lightningcss 1.33 (and its platform binaries): MPL-2.0, build-time only.
- node-forge 1.4: BSD-3-Clause OR GPL-2.0, build-time only.
Compatibility and integrations: Expo's push notification service (APNs and FCM), EAS Build and EAS Submit, App Store Connect and REST APIs with token authentication.
Redistribution terms
The asset's own code can be integrated into the licensee's commercial products under the embeddable module, source code and OEM licenses, on the terms of the contract. lightningcss (MPL-2.0) and node-forge (BSD-3-Clause OR GPL-2.0) have specific terms, and both are used at build time only; see the list under Technical specifications.
Installation requirements
An HTTP API with token authentication, an Expo account, Apple and Google developer accounts in your name and your own Firebase project for notifications on Android.
Frequently asked questions
Can it connect to any back end?
Yes, as long as the back end exposes an HTTP API with token authentication.
Who publishes the app?
You do, with your accounts. Submission to App Store Connect is automated. On Android, the builds are generated and publishing on Google Play is set up with your account.
Does it work on tablets?
On iOS it is configured for iPhone. Enabling iPad is a project setting plus a review of the layout.
Is maintenance included?
No. Maintenance (updates, including those for each new Expo release, and bug fixes) and integration support are contracted separately.
Request
Request information on M-APP-01
Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.