Enterprise apps

Enterprise Mobile Apps: Security, SSO, Device Management, Offline Use

Enterprise Mobile Apps: Security, SSO, Device Management, Offline Use: MeraSEO article cover
Key takeaways
  • An enterprise app is judged on four things a consumer app barely touches: sign-in through the company identity system, controlled distribution, behavior without network, and protection of business data.
  • Use OpenID Connect (or SAML where the identity provider demands it) through the system browser, never a custom username and password screen for staff.
  • Decide offline rules per data type before building: what is cached, who wins a conflict, and what happens to unsynced work when a device is wiped.
  • If the app handles personal data of individuals, plan for the Digital Personal Data Protection Act, 2023 from the start: purpose limits, safeguards, retention and breach handling.

You have decided that field staff, branch teams or distributors need a mobile app: order entry, inspections, approvals, attendance, delivery proof. Building the screens is the easy half. The hard half is making the app something your IT team will allow on company and personal phones, that signs in with existing accounts, that survives a basement warehouse with no signal, and that does not leak customer data when a phone is lost.

This post covers those four areas for internal and partner-facing apps. It does not repeat the question of native versus cross-platform, which we cover in choosing how to build your app. The points below apply whichever approach you pick.

Single sign-on: use the identity system you already have

Most companies already run an identity provider (IdP) such as Microsoft Entra ID, Google Workspace or Okta. Staff expect to sign in once, with multi-factor authentication, and to lose access the day they leave. A separate password database inside your app breaks all three expectations.

OIDC versus SAML

  • OpenID Connect (OIDC) is built on OAuth 2.0 and suits mobile apps well. The app opens the IdP login page, the user signs in, and the app receives tokens. Use the authorization code flow with PKCE.
  • SAML is older and XML based. Some enterprises still require it. For a mobile app it is usually handled by a backend or by the IdP exposing an OIDC bridge, rather than by parsing SAML on the phone.

Implementation rules that avoid trouble

  • Sign in through the system browser sheet (ASWebAuthenticationSession on iOS, Custom Tabs on Android), not an embedded web view. This allows shared sessions, password managers and passkeys, and keeps the app from seeing the password.
  • Keep access tokens short lived and refresh tokens in the iOS Keychain or Android Keystore-backed storage, never in plain preferences or logs.
  • Authorize on the server for every request. Hiding a button in the app is not access control.
  • Map IdP groups to app roles (for example “Branch manager” can approve, “Field agent” can only submit) and define what happens when a role changes mid-session.
  • Plan sign-out and offboarding: disabling the user in the IdP should end access by the time the current token expires, and ideally revoke refresh tokens at once.

Device management and distribution

Two terms get mixed up. MDM (mobile device management) controls the whole device: enrollment, passcode policy, remote wipe, installing apps. MAM (mobile application management) controls only the work app and its data, which is how companies handle staff using their own phones (BYOD) without taking over the device.

SituationiOS routeAndroid route
Company-owned phones, full controlEnroll in an MDM through Apple Business Manager, push the app silentlyAndroid Enterprise fully managed device, app from managed Google Play
Staff using their own phonesUser enrollment or app-level policies; app from Custom Apps or the App StoreWork profile keeps the work app and data separate from personal apps
Distributors or vendors outside your companyCustom app assigned to their organization in Apple Business Manager, or an unlisted App Store app shared by direct linkPrivate app published to specific organizations in managed Google Play
Pilot with a few testersTestFlightInternal or closed testing track on Google Play

Do not plan to hand out APK files or enterprise-signed iOS builds as a long-term answer. Apple restricts in-house enterprise certificates to a company’s own employees, and sideloading APKs gives you no update control. Private distribution through Apple Business Manager custom apps and managed Google Play is the supported route. Ask the client’s IT team early which MDM they run (Intune, Workspace ONE, Jamf, Knox and so on), since it decides how configuration such as server URLs and certificates is delivered. Android’s enterprise documentation is at developer.android.com/work.

Many MDMs support managed app configuration, a standard way to pass settings (server address, tenant ID) to the app. Build for it, so a single app binary can serve multiple environments without separate builds.

Offline use and sync

Warehouses, plants, farms, lifts and trains all have dead zones. An app that shows a spinner when the signal drops will be abandoned for paper or WhatsApp. “Offline” is not a switch; it is a set of decisions.

Decide per data type

  • Reference data (product lists, customer lists, price books): download and cache, with a “last updated” time visible and a refresh on reconnect.
  • Records the user creates (visit reports, orders, inspection forms): save to a local database first, mark them “pending”, and upload from a queue.
  • Actions that must be live (credit approval, stock reservation): require a connection and say so clearly, rather than pretending to succeed.

Conflict handling

Two people edit the same customer record offline. When both sync, something has to win. Pick a rule for each entity: last write wins for low-risk notes, field-level merge for records with many independent fields, and an explicit “needs review” state for money or stock. Give uploaded records a client-generated unique ID so a retry after a dropped connection does not create duplicates, and make the server endpoints safe to call twice.

Also decide the security side: encrypt the local database, clear it on sign-out, and decide how long unsynced data may live on a device. If a phone is remotely wiped, the unsynced work goes with it, so show a clear pending-items warning and sync as early as possible.

Data security and the DPDP Act

Treat the app as an untrusted client talking to a trusted server. A practical baseline:

  • HTTPS everywhere, with certificate pinning only if your team can manage certificate rotation.
  • No secrets, API keys or admin credentials compiled into the app; they can be extracted.
  • Screenshots and the app switcher preview can be blocked on screens showing sensitive data, if policy requires it.
  • Jailbreak or root detection is a signal for your MDM policy, not a guarantee.
  • Logs and crash reports must not contain customer details or tokens.
  • Keep an audit trail of who viewed or changed sensitive records.

If your app handles personal data about customers, patients, students or employees, plan for India’s Digital Personal Data Protection Act, 2023, under which your organization is the data fiduciary. The DPDP Rules were notified in November 2025 with a phased start, and most fiduciary duties take effect about 18 months after notification, so an app you build now will be live when they apply. In plain terms the law expects a clear notice and valid consent for the stated purpose (or another lawful ground), collecting only what you need, reasonable security safeguards, correction and erasure on request, and a process for reporting breaches. Check the current text and commencement dates on the MeitY website and take legal advice for your sector. From the app side, the usual practical steps are data minimization, role-based access, retention limits and a deletion process that also covers backups.

Integrations: the app is the thin part

The app rarely owns the data. Orders live in the ERP, customers in the CRM, attendance in HR software. Do not let the phone talk directly to those systems. Put an API layer between them that handles authentication, validation, throttling and mapping, so a change in the ERP does not force every user to update the app. This is the same work described in our API and third-party integration service. Ask early for sandbox access, field mappings and an owner on the client side for each system, since waiting on a vendor is the most common cause of delay.

A worked example: field-sales order app

  1. Sales reps sign in with the company Google Workspace or Microsoft account via OIDC; the backend maps their group to the “Field agent” role.
  2. The app syncs the price book and assigned customers when on Wi-Fi in the morning, and shows the sync time.
  3. In a shop with no signal, the rep creates an order. It is saved locally as “pending” with a unique ID.
  4. On reconnect the queue uploads. The API checks credit limits and stock; rejected orders return to the rep with a reason, not silently.
  5. The app is delivered to company phones through the MDM and to personal phones through an Android work profile or iOS user enrollment.
  6. When a rep leaves, disabling the account in the IdP stops access, and the MDM removes the managed app data.

Rollout and support

  • Pilot with one team for a few weeks and watch the sync failures, not just the opinions.
  • Write a one-page guide and a short walkthrough video for staff, since training cost is part of the project.
  • Version the API so older app versions keep working, and use a minimum-version check that nudges users to update.
  • Budget for operating system updates each year; a new iOS or Android release can change permissions and background behavior.

The app is live software, not a one-time delivery. Our app maintenance and support covers updates, monitoring and fixes, and business app development is where new internal apps start.

Frequently asked questions

What is the difference between MDM and MAM for an enterprise app?

MDM manages the entire device: passcode rules, enrollment, remote wipe and app installation. MAM manages only the work app and its data, leaving the personal side of the phone alone. Companies usually use MDM for company-owned devices and a work profile or MAM policies for staff-owned phones.

Should an enterprise app use SAML or OpenID Connect?

OpenID Connect is usually the better fit for mobile apps, using the authorization code flow with PKCE through the system browser. Use SAML when the organization’s identity provider or policy requires it, typically through a backend or bridge rather than parsing SAML on the device.

How do we distribute an internal app without publishing it publicly?

On iOS, use custom apps through Apple Business Manager, assigned to your organization. On Android, publish a private app to your organization in managed Google Play. TestFlight and Play testing tracks suit pilots, not permanent distribution. Ask the client’s IT team which MDM they use, since it decides how settings reach the app.

How should an app handle conflicts when offline edits sync?

Choose a rule for each type of data. Last write wins works for simple notes, field-level merging suits records with many independent fields, and anything involving money or stock should go to a review state. Give each offline record a unique ID so retries never create duplicates.

Planning an internal app for your team?

Share which systems it must connect to and how your staff sign in today. We will outline the architecture, rollout route and support plan.

Discuss your business app →

Related Post

Call Now Button