> 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/further-reading/faqs/using-the-demo-app-and-scanning-qr-codes.md).

# Using the Demo App and Scanning QR codes

**1. Download the latest version**

Download the latest version of the demo apps on the [Google Play store](https://play.google.com/store/apps/details?id=com.smileidentity.sample\&pcampaignid=docs_share) and the [Apple App store](https://apps.apple.com/us/app/smile-id/id6448359701).

**2. Link your partner account**

You need your application config to link your partner account. You can do this by scanning the QR code or manually entering the config details in the field provided in the mobile app. Get a partner account [here](https://usesmileid.com/talk-to-an-expert) if you don't have one.

On the Smile Portal, go to the `developers` section and click on `Security Settings` or visit [Smile Identity Portal](https://portal.smileidentity.com/security-settings). In the `API Key Management` section, go to your desired API key in the table and download the configuration file by clicking `config` or you can open the QR code `QR` for scanning .

<figure><img src="/files/8yvYKy07qS0RXQk8PS7T" alt=""><figcaption><p>API Keys with Config and QR selection</p></figcaption></figure>

* Once the QR code is open, click on `Scan Configuration QR` and then point the camera view to the QR code you have opened up on the portal page (See previous step). Or click `Add Config Manually`, copy the config information from the downloaded config file, and paste it into the text area.

<div><figure><img src="/files/3f3fOUPAQd4ryAapB6hH" alt="welcome config screen" width="143"><figcaption><p>The Config screen on the app</p></figcaption></figure> <figure><img src="/files/qcSi7dpsRBQc7mPI7ra5" alt="QR pop-up" width="375"><figcaption><p>QR popup and api key page</p></figcaption></figure></div>

* That's it! Your account is now linked to this config file. To change config, go to the `settings` tab of the demo app and click `Update Config` and follow the prompts.

{% hint style="info" %}
Note: Ensure that you have a callback URL setup to be able to run jobs successful on the mobile sdk. [See here on how to set one up](/further-reading/faqs/how-do-i-setup-a-callback.md)
{% endhint %}

<figure><img src="/files/RQbk6RIqt7e3UFPPTucA" alt=""><figcaption><p>Demo app interface</p></figcaption></figure>

**3. Using the Demo app**

You can use the demo app to test different biometric verification flows and features of the Smile ID SDKs. In the `home` tab, Click on you desired product and follow the instructions to go through the flow.

**4. Viewing Job Results on the demo app**

Click on the `jobs` tab to see the outcome of the job. This tells you whether a job was successful or not and gives you the appropriate [result code](/further-reading/result-codes.md). The full results details are available on the `jobs` section of the portal


---

# 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/further-reading/faqs/using-the-demo-app-and-scanning-qr-codes.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.