Digital Experiences
Mobile apps for field teams and customers, online or off
Brihat Infotech builds apps for two groups of people: staff who work where the signal drops, and customers who expect a clean app on their own phone. The first kind keeps working offline and syncs when the network returns.
What we build
- Offline-first apps
records are stored on the phone and synced when a connection is back.
- Field-force apps
work orders, and proof of work captured with the photo and the location.
- Customer apps
onboarding, account views and requests, as in IRFC Invest, the bond holdings app we built.
- Cross-platform builds
one codebase for Android and iOS, with native code where the hardware or the design needs it.
- Device and release management
staged releases, and versions you can retire.
- Push messages and deep links
a notification that opens the right screen.
- Distribution
the app stores, or mobile device management (MDM) for staff phones.
Releases and devices
Staff phones are managed differently from customer phones. For staff, we plan the rollout through mobile device management, with a minimum version and a way to retire old builds. For customers, we plan app store releases in stages, with push messages and deep links tested before launch.
Tools we use
React Native or Flutter for cross-platform work. Flutter is also what we used for Brihat's own EHS app.
How a build runs
- 01Discovery sprint, on site or in Noida. We ride along with your future users.
- 02Design and prototype. Users tap through the prototype before engineers start.
- 03Build in releases. Each release is installable on real phones.
- 04Store release or MDM rollout.
An app typically takes 10 to 20 weeks. The team is one designer and two to four mobile engineers. Releases are staged as set out in How we engage.
What you hold afterwards
- App source code, in your own repository from the first commit
- A release runbook
- The design files and component library
Apps in use
State power distribution utility, field operations. Technicians used paper job cards. We built field apps that work offline. Jobs are routed to technicians, closure is confirmed by location, assets carry QR trails and dispatchers have their own console. See the utility field operations case study
IRFC Invest. An investor app showing bond holdings. See the IRFC Invest case study
Also see: hiring Flutter and mobile developers
Questions buyers ask
The range is under "How a build runs" above. Where a build lands in it depends on the number of screens, how many other systems the app connects to and how much must work offline.
More in Digital Experiences
Describe the job your team still does on paper or WhatsApp.
Tell us what you want to build.
The first call is 45 minutes with an architect, usually the founder. It is free, and we will sign an NDA first if you ask.