Corporate Portal Mobile App Development with SSO, Offline & MDM

Corporate Portal Mobile App Development

Corporate Wi-Fi drops, VPN disconnects, and employees need access to documents and tasks anytime. We develop corporate portal mobile apps that work offline, sync when the connection is restored, and comply with all security policies. Our solutions integrate with your existing environment: Azure AD, Active Directory, SharePoint, Jira, Confluence, and on-premise systems with NTLM and SAML. We provide single sign-on (SSO), MDM policy support, offline mode, and push notifications. All apps undergo internal security audits and comply with App Store Review Guidelines.

How We Implement Authentication in a Corporate Environment

The most common requirement is login via corporate SSO. If the company uses Microsoft 365, it's Azure AD with OAuth 2.0 / OIDC. If on-premise, it's ADFS with SAML. For mixed infrastructure, Okta or PingFederate as IdP. For mobile OIDC flows, we use the AppAuth library — standard for iOS and Android. Example for Android:

// Android — OIDC via AppAuth val serviceConfig = AuthorizationServiceConfiguration( Uri.parse("https://login.microsoftonline.com/$tenantId/oauth2/v2.0/authorize"), Uri.parse("https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token") ) val authRequest = AuthorizationRequest.Builder( serviceConfig, clientId, ResponseTypeValues.CODE, Uri.parse("com.company.app://auth/callback") ) .setScope("openid profile email offline_access") .build() authService.performAuthorizationRequest(authRequest, pendingIntent) 

After obtaining the authorization_code, we exchange it for access_token + refresh_token. Tokens are stored in EncryptedSharedPreferences. Refresh is automatic via an interceptor in OkHttp.

Integration with Corporate Systems

A typical corporate portal data stack: SharePoint / Confluence for documents, Jira / ServiceNow for tasks and tickets, AD for org structure and contacts, Exchange / Google Workspace for calendar. Microsoft Graph API covers most needs for Microsoft stack:

suspend fun getMyDocuments(): List<DriveItem> { return graphClient .me() .drive() .root() .children() .buildRequest() .select("id,name,lastModifiedDateTime,webUrl") .top(50) .get() .currentPage } 

For Exchange calendar — MS Graph /me/calendarView with date range. For org structure — /users/{id}/directReports and /users/{id}/manager. If the portal is on-premise without Microsoft 365 — REST API SharePoint (2016/2019). NTLM authentication for on-premise is a separate challenge on mobile: OkHttp supports NTLM via authenticator(), but requires careful setup.

MDM and Corporate Restrictions

MDM enforces policies on the device or the application. For corporate apps, there are two scenarios:

• MAM — policies are applied to the specific app without managing the whole device. Microsoft Intune MAM SDK allows applying policies: disable copy/paste, disable screenshots, enforce PIN before launch.
• MDM-enrolled devices — IT manages the device fully. The app is distributed via managed distribution (Apple Business Manager / Google Enterprise).

Intune MAM SDK for Android is added as a dependency and initialized via MAMApplication:

class MyApp : MAMApplication() { override fun onCreate() { super.onCreate() // MAM automatically applies policies } } 

Without this integration, the app may be blocked by corporate policy on enrolled devices.

How to Ensure Offline Mode and Synchronization

Corporate networks are unstable — VPN drops, corporate Wi-Fi is lost. Critical functionality must work offline: viewing documents, contacts, tasks.

On Android — Room for cache + WorkManager for background sync. On iOS — Core Data + BGAppRefreshTask. Sync conflicts are resolved by last-modified timestamp: server data wins if the user hasn't edited locally. Push notifications for new tasks and documents via FCM / APNs. In corporate networks, FCM may be blocked by firewall — need fallback to polling or WebSocket.

Tech Stack and Timelines

Flutter or React Native are optimal for corporate portals: single codebase for iOS and Android, fast development. Native development is justified if there are strict requirements for Intune SDK or specific native integration.

Architecture: Clean Architecture + BLoC (Flutter) or Redux Toolkit (React Native). Modular structure: auth, documents, tasks, contacts, calendar — independent modules with their own repositories.

MVP (SSO + org structure + documents): 2-3 months. Full portal with tasks, calendar, notifications, offline — 4-6 months. Cost is calculated individually after an audit of the corporate infrastructure.

Comparison of approaches:

What's Included in the Work

Within the project, we provide:

• Audit of corporate IT infrastructure and existing systems.
• Architecture design and interface prototype.
• Development following Clean Architecture with modular structure.
• Integration with corporate systems (SSO, SharePoint, Jira, AD, calendar).
• Configuration of MDM policies via Intune MAM or MDM enrollment.
• Implementation of offline mode and synchronization.
• Push notifications (FCM/APNs) with fallback mechanisms.
• Testing on real devices and on the corporate network.
• Preparation of documentation and administrator training.
• Technical support for 3 months after launch.

Our Work Process

Our team has 10+ years of experience in corporate mobile app development. We have delivered over 50 projects for large companies, including banks, government, and industrial sectors. Certified Microsoft Intune and Apple engineers ensure compliance with all corporate policies and App Store Review Guidelines. We provide a code warranty and post-launch support.

Want a consultation? Contact us for an audit of your infrastructure and we will prepare an accurate commercial proposal. Order solution design right now.