# Develop with Orchestration SDK: Android

This guide describes how to quickly integrate Journeys into your Android application.

See SDK reference 

## Introduction

The Orchestration SDK enables client-side developers to build user experiences that interact with journeys.

Each journey contains a business workflow, such as login or secure user onboarding. It consists of backend steps, such as data processing or invoking external systems, and client-facing steps, such as a login form or identity verification. The SDK allows the client application to present screens and prompt for user input, and then send this information back to the journey for further processing.

Whenever the client-side interaction requires additional Mosaic platform capabilities, such as passkeys or risk detection, the developer needs to activate the appropriate SDK module to perform the step and collect the required input. This allows separation of concerns between the journey workflow handling, and the specific capability used.

## SDK lifecycle

Regardless of journey logic, the SDK lifecycle consists of the following:

div
𝟷
. 
 Perform a one-time initialization before SDK first use by invoking either 
code
initialize()
 or 
code
initializeSDK()
 (using strings.xml file).
br
𝟸
. 
 Activate 
code
startJourney()
 and wait for the server response.
br
𝟹
. 
 Check 
code
TSIdoServiceResponse
 and present the appropriate UX. If needed, operate additional Mosaic SDKs.
br
𝟺
. 
 Return client input via 
code
submitClientResponse()
 (allows selecting a journey branch if supported by journey step).
br
𝟻
. 
 Repeat 3 and 4 until receiving 
code
Success
 or 
code
Rejection
.

The above is reflected in the following workflow diagram:


```mermaid
sequenceDiagram
  participant user as User
  participant app as Client Application
  participant sdk as Orchestration SDK
 participant server as Mosaic

  user ->> app: click login
  opt If not initialized
  app ->> sdk: initialize()
  end
  app ->> sdk: startJourney(journey-id, optional parameters)
  sdk ->> server: forward start-journey parameters
  server ->> server: process server-side<br>journey steps
  server -->> sdk: journey service response
  sdk -->> app: idoServiceResponse object<br>describes required client step<br>or journey completion
  loop while the response is not "success" or "rejection"
  app ->> app: present UI per idoServiceResponse.journeyStepId<br>use additional SDK modules if needed (eg passkey)
  user ->> app: interact as needed
  app ->> sdk: submitClientResponse(selected-option, data)<br>selected-option affects journey branch<br>if multiple options are available
  sdk ->> server: forward client response
  server ->> server: process incoming data<br>and further steps
  server ->> sdk: journey service response
  sdk -->> app: idoServiceResponse object<br>describes required client step<br>or journey completion
  end
  app ->> app: post journey UX, if completed
```

## Requirements

- Android 5+ (API level 21+)
- Device with registered biometrics, e.g., Face or Fingerprint (needed for passkey authentication used as example in this guide)
- Device support for Google Play Services (needed for passkey authentication used as example in this guide)


## Before you start

Before the SDK can start running journeys, make sure to:
☐   Coordinate with the journey developer (regarding journey ID, steps, expected data, etc).
☐    Obtain the Client ID that identifies the app, from the app settings in the Admin Portal
☐    Allow Mosaic IPs and [domains](/guides/quick_start/enable_communication) on your network

## Step 1: Installation

Add the following lines in the shared build.gradle file ("allprojects" scope):


```groovy
dependencyResolutionManagement {
    repositories {
        maven {
            url('https://transmit.jfrog.io/artifactory/transmit-security-gradle-release-local/')
        }
        mavenCentral()
        google()
    }
}
```

Add the following in the module build.gradle file (project scope):


```groovy
dependencies {
    implementation("com.ts.sdk:identityorchestration:1.0.+")
}
```

## Step 2: Initialize SDK

Initializing the SDK configures it to work with your client ID, which is the context under which the entire journey is executed. It also allows setting the base URL for the SDK to use, whether a Mosaic-provided path or your own proxy.

details
summary
b
Initialize using strings.xml configuration (recommended)
To do this, update the strings.xml file in your Application with the following content.


```xml
<resources>
    <!-- Mosaic Credentials -->
    <string name="transmit_security_client_id" translatable="false">[YOUR_CLIENT_ID]</string >
    <string name="transmit_security_base_url">[YOUR_BASE_URL]</string>  <!-- Default is https://api.transmitsecurity.io-->
</resources>
```

Add this code to initialize the SDK:


```kotlin
// Initializes SDK where application_context is an object inheriting from Application class
try {
    TSIdo.initializeSDK(application_context)
} catch (exception: TSIdoInitializeException) {
    // log error…
}
```

Note
If you're using a [custom domain](/guides/deployment/custom_domains) for your application, set `transmit_security_base_url` to your custom domain instead of the default Transmit domain.

details
summary
b
Initialize using SDK parameters
Configure the SDK using the snippet below:


```kotlin
// Initializes SDK where application_context is an object inheriting from Application class
TSIdo.initializeSDK(application_context,
    clientId,
    TSIdoInitOptions(baseUrl))  // Default is https://api.transmitsecurity.io
```

Note
If you're using a [custom domain](/guides/deployment/custom_domains) for your application, use your custom domain as the `baseUrl` instead of the default Transmit domain.

## Step 3: Start journey

Starting a journey is usually a response to some user interaction, such as clicking a login or sign-up button.  The start parameters indicate which journey to start, and optionally pass additional parameters if the journey expects them.

For example, if the client app uses email as the user identifier and caches it locally after sign-up, it can pass it to the journey as `userEmail`. The journey can reference it using this expression `@policy.request().params.userEmail`


```kotlin
// Starts a journey identified by journeyId
TSIdo.startJourney(journeyId,  // Journey ID
    TSIdoStartJourneyOptions(additionalParams,  // Optional additional params
        flowId), idoCallback)
```

Note
The `idoCallback` object should implement the [TSIdoCallback](https://transmitsecurity.github.io/ido-android-api-reference/-identity%20-orchestration%20-s-d-k/com.transmit.idosdk/-t-s-ido-callback/index.html) interface.

## Step 4: Handle service response

After starting the journey, the client app waits for the `TSIdoServiceResponse`. It will contains all the information the client needs in order to determine what to do next.

To handle the service response, the client app needs to:

1. [Select a handler based on the step](#1-select-handler)
2. [Use the data provided by the journey](#2-use-data-sent-from-journey)
3. [Respond to the journey with requested input](#3-respond-with-collected-data)


### 1. Select handler

Upon receiving the `TSIdoServiceResponse`, launch a handler that executes the relevant step by switching/selecting on the `TSIdoServiceResponse.journeyStepId` parameter. It will either contain one of these [enums](https://transmitsecurity.github.io/ido-android-api-reference/-identity%20-orchestration%20-s-d-k/com.transmit.idosdk/-t-s-ido-journey-action-type/index.html) or the **Step ID** configured in the [Login Form](/guides/orchestration/journeys/login_form) or [Collect information](/guides/orchestration/journeys/get_info_from_client) step. Each handler should process the data, display whatever UI is needed, and call `submitClientResponse()` when the interaction is concluded.

This is how the app code would dispatch handlers based on this property:


```kotlin
when(idoResponse.journeyStepId) {
    TSIdoJourneyActionType.Information.type -> handleInformationAction(idoResponse)
    TSIdoJourneyActionType.EmailOTPAuthentication.type -> handleOtpInput(idoResponse)
    "main_login_form" -> handleMainLoginForm(idoResponse)
    "user_info_form"e -> handleUserInfoForm(idoResponse)
    ...
}
```

### 2. Use data sent from journey

Inside the handler function, the app code should render a UI that fits the specific step, and use information from the `data` property if it was provided in the `TSIdoServiceResponse` object. This data is described in each [step guide](/guides/journeys_intro).

Let's see an example for a [Register Passkeys](/guides/orchestration/journeys/register_webauthn) step. `TSIdoServiceResponse` will include `journeyStepId` set to `WebAuthnRegistration` and a `data` object containing the user identifier and other WebAuthn configuration. This data can be used for calling the webauthn (passkey) registration module, as shown below:


```kotlin
val userName = (result.data as JSONObject).optString("username")
val displayName = (result.data as JSONObject).optString("display_name")

if (!userName.isNullOrEmpty()) {
    activity?.let {
        TSAuthentication.registerWebAuthn(it, userName, if (displayName.isNullOrEmpty()) null else displayName, object:
            TSAuthCallback<RegistrationResult, TSWebAuthnRegistrationError> {
            override fun error(error: TSWebAuthnRegistrationError) {
                //handle error
            }

            override fun success(registrationResult: RegistrationResult) {
                //submit registration result
                val encodedResult = registrationResult.result()
                TSIdo.submitClientResponse(TSIdoClientResponseOptionType.ClientInput.type, WebAuthnRegisterResult(encodedResult))
            }
        })
    }
}
```

### 3. Respond with collected data

Once the user interaction is concluded, the handler should collect the response data and submit it using `submitClientResponse()`. This call yields control back to the journey, and returns with a new `TSIdoServiceResponse` once the journey reaches the next client-facing step.

The call parameters are the collected data, and a response option identifier. We’ll talk more about these below. For now, let's follow the [Register Passkeys](/guides/orchestration/journeys/register_webauthn) example of making this call.


```kotlin
data class WebAuthnRegisterResult(val webauthn_encoded_result: String)
...
val encodedResult = registrationResult.result()
TSIdo.submitClientResponse(TSIdoClientResponseOptionType.ClientInput.type, WebAuthnRegisterResult(encodedResult))
```

details
summary
b
About response data schema
Each journey step expects specific fields to be sent back in the data object. The details of the expected fields are described in the relevant [step guide](/guides/journeys_intro). As seen above, when we use the example of the [Register Passkeys](/guides/orchestration/journeys/register_webauthn) step, the expected data is a field called `webauthn_encoded_result` which is the output of the Passkey registration SDK.

For most journey steps, the client response schema is fixed. However, there are two steps that expect a dynamic schema. The [Login Form](/guides/orchestration/journeys/login_form) step allows presenting multiple authentication options and collects input for one of them. The [Collect information](/guides/orchestration/journeys/get_info_from_client) step allows presenting an arbitrary data collection form to the end user. For both steps, the expected data schema is configured in the step. The client developer must coordinate with the journey author for the expected schema for each Step ID.

details
summary
b
About alternate branches and response options
Certain steps support multiple response options. These options are passed in the `TSIdoServiceResponse` object in the `clientResponseOptions` property. These represents possible replies that the client can provide as a response to a journey step, and affect the branch that is taken when the step is completed.

Three of these replies have a standard type (per SDK):

- `ClientInput` represents a typical reply to a step that has a main or single output path. See above the example for [Register Passkeys](/guides/orchestration/journeys/register_webauthn) is using this reply option. This would be the common reply option to most steps.
- `Cancel` chooses the cancel branch in actions that support it
- `Fail` chooses the failure branch in actions that support it


Apart from those, some journey steps support alternate (custom) branches. The **Branch ID** is configured by the journey author, and should be used to identify the branch when calling `submitClientResponse()`. The example below submits a response to the [Login Form](/guides/orchestration/journeys/login_form) step, where one of the alternate branches proceeds to passkey authentication. This branch also expects a specific schema (that can be customized by the journey author) - the default is getting the encoded result after activating the authentication SDK.


```kotlin
data class WebAuthnAuthenticationResult(val webauthn_encoded_result: String)
...
val encodedResult = registrationResult.result()
TSIdo.submitClientResponse("passkey", WebAuthnAuthenticationResult(encodedResult))
```

## Step 5: Complete journey

Mosaic signals journey completion by setting the `journeyStepId` property to `Rejection` or `Success`. The specific enum for each SDK is described in the [Step 3.1](#1-select-handler) above. If successful, the `token` property contains a token as a proof of journey completion.

## Next steps

The SDK also supports the features below. For more info, talk to your Transmit Security representative.

- Generating a debug pin for the journey debugger
- Local console logs
- Resources URIs as part of SDK initialization


style

    section article ol li {
      margin-top: 6px !important;
    }
    .lifecycleSteps {
      line-height: 30px !important;
    }