iOS - Configure
This guide provides a high-level understanding of how to configure a swift based module for the Q2 Mobile Application. Learn how to integrate third-party SDKs, include resources, and configure your module for use within the Q2DevApp.
📦 How to Include Third-Party SDKs
Need external libraries in your module? You can integrate third-party libraries as follows:
👉 Learn more in Configure Third-Party SDKs
🖼 How to Include Resources in Module
To include images, JSON files, storyboards, or any other assets as follows:
👉 See detailed steps in Configure Resources
⚙️ How to Configure Your Module in settings.json
For your module to be recognized and loaded by the Q2DevApp, it must be declared in
settings.json. This file defines one or more configuration values as follows:
👉 Start here: Module Settings
🔐 How to Configure Authentication
By default, Q2DevApp renders a web-based login screen (WKWebView) for user authentication. Partners can replace this with a native authentication experience by configuring one of the following authentication modules:
| Authentication Option | Use Case |
|---|---|
| Web Login (default) | No additional module configuration needed — DevApp authenticates via the standard web-based login screen |
| Native Login | Password-based authentication with a fully native SwiftUI UI, biometric support, and multi-user selection |
| InboundSSO | OAuth 2.0 / OIDC authentication via an external identity provider (Okta) |
Only one authentication module should be enabled at a time. If neither Native Login nor InboundSSO is configured, DevApp uses web login by default.
👉 For password authentication with a native UI: Native Login Module
👉 For SSO/OIDC authentication: InboundSSO Module