Oracle Mobile Apps.

Does ETHX Softcon build custom Oracle Fusion mobile apps?

ETHX Softcon Oracle Mobile Apps are custom, role-based mobile apps built on Oracle Fusion-native authentication and data for tasks that Oracle's out-of-the-box mobile apps do not cover. Examples include approvals and expenses apps, a shop-floor tablet app for operators, a field technician app, and a manager self-service app for HCM team actions such as performance, time-off, and hire requests.

ETHX Softcon builds most apps in React Native for both iOS and Android, using native code where requirements such as advanced camera or AR demand it, with Oracle Integration Cloud or REST integration. Apps use an offline-first data model with local SQLite, queued writes, and reconciliation on sync. Users sign in through SAML or OIDC against their identity provider, and apps include PII redaction and audit logging. Delivery runs through scope, design, build, test, and ship, with ETHX Softcon handling app store submission and MDM packaging. A focused role-based app typically takes 6–10 weeks.

What should you evaluate before building custom mobile apps on Oracle Fusion?

Check Oracle's own mobile options first, because some roles are already covered. The Oracle Fusion Applications mobile app gives employees and managers access to responsive HCM features, and Oracle Fusion Field Service has a native app for Android and iOS. A custom app earns its cost when a role needs a focused workflow that spans several modules, has to work offline for long periods, uses device hardware such as barcode scanners, or serves users who rarely open the full application.

Security needs to be designed in from the start. The OWASP Mobile Application Security Verification Standard groups controls for data storage, cryptography, authentication and network communication, and it is a practical checklist for reviewing any vendor's app. Users should sign in through your identity provider with single sign-on, and the app should never hold stored passwords or shared integration credentials. API calls should use short-lived OAuth tokens tied to the signed-in user, and routing requests through a controlled backend or Oracle Integration keeps secrets off the device.

Plan for offline use and the full lifecycle as well as the first release. An offline-first app needs clear rules for what is stored locally, how long it is kept, and how conflicting updates are resolved when the device reconnects. Mobile operating systems, app store policies and Oracle's regular updates all change over time; Oracle REST resources can have more than one version, so pin the versions the app calls and retest after each Oracle update. Decide how the app is distributed and remotely wiped, typically through mobile device management, and measure adoption by tasks completed rather than downloads.