Practice
Mobile app development with React Native and Flutter
Applications built on the same API as the web platform, so a rule that changes is changed once and both clients agree.
A mobile application is rarely the whole product. It is one client of a system that also has a web dashboard, an API and often a device reporting into it. NextWR builds the app against that same API, with a shared client layer, so the phone and the browser cannot drift apart.
The decisions that matter get taken in the first week, because they shape the data model rather than the screens. What the app must do when the network drops. Which records are cached and for how long. Whether a notification is a message or a state change the app has to reconcile. Getting those wrong is expensive; getting them right early is not.
Typical scope is authentication, a catalogue, orders, a wallet, notifications and a profile, in several languages including Arabic with right-to-left layout. Store submission and the review cycle are handled by us, published under accounts the client owns.
Both React Native and Flutter are in use. React Native when the team also owns a React web front end and the shared types are worth more than anything else; Flutter when the interface is heavy and consistent rendering across devices matters more.
What is included
- React Native or Flutter application for iOS and Android
- Shared API client with the web platform
- Token-based authentication, including mobile-number sign-in
- Offline behaviour, push notifications and deep links decided in the first week
- Multi-language interface including Arabic right-to-left
- Store submission and release management under the client's accounts
Not included
- Applications with no back end behind them
- Games and heavy real-time graphics
- Store marketing, screenshots and listing optimisation
Common questions
React Native or Flutter?
React Native when the same team owns a React web front end, because the shared types and shared API client remove a whole class of drift. Flutter when the interface is dense and identical rendering across devices matters more than sharing code with the web.
Can you publish under our developer accounts?
Yes, and we prefer it. The accounts stay with the client, which means the application does too.
Projects that use this
React Native
E-commerce mobile application
A React Native application against a Laravel API: accounts, products, categories, orders, wallets, vouchers and several stores, in four languages including Arabic.
IoT attendance platform
BassmaPro
An attendance and access platform for schools, companies, hospitals and organisations. A terminal reads a fingerprint or a card, the platform records the event, and a parent or an administrator sees it.
Interfaces
Right-to-left has to be designed in, not added
Arabic support added at the end is a rewrite. Built in from the first component it costs almost nothing, because the layout mirrors on its own.
Tell us what you are building.
Write in English, French, Romanian or Arabic. Every message gets a written answer within one business day.