# Mobile application development — Genyra

> Custom mobile app development: native iOS and Android apps for staff and customers that work offline, protect the device and share one record with your systems.

Canonical page: https://genyra.com/software/mobile-applications

Native iOS and Android applications for staff and customers that keep working without a connection, protect what is on the device, and share one record of truth with the rest of the organisation’s systems.

## Native applications for staff and customers.

An application for staff in the field and an application for customers are different products with the same discipline. Both are built natively for iOS and Android, following each platform’s conventions for navigation, input and accessibility, so the application behaves the way the device already taught its user. Native code is used where it matters: the camera, the secure store, background work and anything the user feels as speed.

What the application must do is stated as the task before any screen is designed, and the first prototype tests the most uncertain interaction, not the most comfortable one.

## Work continues without a connection.

State lives on the device first. A visit is recorded, a form is completed and a photograph is attached whether or not there is signal, and the application syncs when a connection returns. Conflicts are handled explicitly: when two people have changed the same record, the application shows both versions and the rule that decides, rather than silently keeping the last one to arrive.

- Local state that survives a closed application and a dead battery
- Sync as a queue with a visible status, not a background guess
- Conflicts surfaced with the rule that resolves them
- The same record identifiers as the server, so nothing is duplicated

## Security on a device that leaves the building.

Credentials and keys are kept in the platform’s protected store, the secure enclave on iOS and the keystore on Android, and never in the application’s files or source. Biometric sign-in is offered as a policy the organisation sets, with a fallback it has chosen. Connections to the organisation’s servers pin the certificates they expect, so a hostile network cannot stand in the middle.

Nothing in the application binary is a secret. Anything that must stay private is held on the server and released to a signed-in, authorised session.

- Secure enclave and keystore for credentials and keys
- Biometric sign-in as a policy decision, with a chosen fallback
- Certificate pinning to the organisation’s servers
- No secrets in the application

## The same contracts as the web and the desktop.

The mobile application is one more client of the organisation’s systems, not a separate copy of them. It reads and writes under the same contracts as the web and desktop applications, so a case, a customer or an order means the same thing on every screen and is held once, with its history, in one record of truth. A change to a rule is made on the server and applies everywhere at once.

## Release and lifecycle.

A customer application goes through store review, with the review timeline planned into the release rather than discovered on the day. A staff application is distributed through enterprise channels and mobile device management, so installation, update and removal are controlled by the organisation. Every release rolls out in stages, can be rolled back, and has a stated support window, so the version in a user’s hand is always one the organisation still maintains.

## How an engagement starts.

Bring the task the application must serve, the people who will use it, the devices they carry and the systems it must reach. We review the existing systems and their contracts, propose the application and its sync and security model, and agree the release channel and the support window. Platform requirements, store policies and device fleets are confirmed for the particular organisation, not assumed.

## Questions we are asked

**Native or cross-platform?** Native for iOS and Android, following each platform’s conventions, sharing one record of truth with the web and desktop clients through the same contracts.

**Does the application work without a connection?** Yes. State lives on the device first and syncs when a connection returns. Conflicts are handled explicitly rather than silently overwritten.

**How is a staff application distributed?** Through enterprise channels and mobile device management rather than the public store. A customer application goes through store review, planned into the release.

## Related work

- [Native application development](https://genyra.com/software/native-applications): Native application development services: what a native app is, when it beats a web app, and how Genyra builds desktop applications for the operating system.
- [Web development](https://genyra.com/software/web-development): Custom web development services: server-rendered websites and web platforms, measured for performance and accessibility, hosted by the company that built them.
- [Systems integration](https://genyra.com/solutions/systems-integration): Systems integration services: contracts between systems, identifiers that mean the same thing everywhere, failure handling and a record of every handoff.

Contact: contact@genyra.com

Genyra LLC and the Dubai business Genyra L.L.C-FZ / Genyra.ai are distinct entities. Project scope and the contracting entity are agreed explicitly.