> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/integration-options/mobile/android/smile-identity-ui/presenting-screens.md).

# Presenting Screens

Step 1 : Call Smile UI

Call the required screen or screens as per the example below

```
new SIDCaptureManager.Builder(<Activity>,<CaptureType>, <REQUEST_CODE>)
The above will call a screen as per the CaptureType specified and you have 4 options to choose from
```

**CaptureType.SELFIE**\
Will show the selfie screen then the review screen before sending the results back to your application

**CaptureType.ID\_CAPTURE**\
Will show the ID card capture screen then send results back to your application

**CaptureType.SELFIE\_AND\_ID\_CAPTURE**\
Will show the selfie screen then the review screen and then the id card capture screen before sending the results back to your application\
\
**CaptureType.ID\_CAPTURE\_AND\_SELFIE**\
Will show the id card capture screen then the selfie screen then the review screen and before sending the results back to your application.

### Step 2: Get Results Using from onActivityResult

The results for the screens are returned in

```
protected void onActivityResult(int requestCode, int resultCode, @Nullable Intent data) {
```

These have

* ```
  data.getStringExtra(SMILE_REQUEST_RESULT_TAG)
  ```

  This is either the tag supplied to the manager or if none was supplied this is an autogenerated tag from the SDK identifying the job
* `data.getStringExtra(SMILE_REQUEST_RESULT_TAG)` This is the result code returned from the capture which can signify a success or failure

### Possible values for `SMILE_REQUEST_RESULT_TAG` are

1. -1 represents a successful capture
2. 777 represents a user cancelled capture
3. 888 represents a failed document capture eror
4. 999 represents a failed selfie capture error
5. 1011 represents a permissions error


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://legacy-docs.usesmileid.com/integration-options/mobile/android/smile-identity-ui/presenting-screens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.