# For Mobile Developers

{% hint style="danger" %}
All Login and Myinfo apps must follow Singpass' [FAPI 2.0-compliant authentication API](https://docs.developer.singpass.gov.sg/docs/technical-specifications/integration-guide) by 31 Dec 2026.

The specifications on this page apply to you only if you are maintaining an existing Login / Myinfo (v5) integration. We encourage you to [migrate](https://docs.developer.singpass.gov.sg/docs/technical-specifications/migration-guides/login-myinfo-v5-apps) early to avoid service disruptions.
{% endhint %}

To facilitate your in-app browser implementation, the following table contains technical resources to help assess, test and implement the changes requested.

|                                                                                                                                            | Android                                                                                                              | iOS                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Sample codes implementing the recommended Proof Key for Code Exchange ([PKCE](https://www.rfc-editor.org/rfc/rfc8252)) for Singpass logins | [Android-Singpass-in-app-browser-login-demo](https://github.com/singpass/Android-Singpass-in-app-browser-login-demo) | [iOS-Singpass-in-app-browser-login-demo](https://github.com/singpass/iOS-Singpass-in-app-browser-login-demo)                                                                                                                                                                                                                                                                                                                                                    |
| In-app browser documentations                                                                                                              | [Chrome Custom Tabs](https://developer.chrome.com/docs/android/custom-tabs)                                          | <p>\[iOS 9 to iOS 10]<br><a href="https://developer.apple.com/documentation/safariservices/sfsafariviewcontroller">SFSafariViewController</a><br><br>\[iOS 11]<br><a href="https://developer.apple.com/documentation/safariservices/sfauthenticationsession">SFAuthenticationSession</a><br><br>\[iOS 12 and above]<br><a href="https://developer.apple.com/documentation/authenticationservices/aswebauthenticationsession">ASWebAuthenticationSession</a></p> |

<br>


---

# Agent Instructions: 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:

```
GET https://docs.developer.singpass.gov.sg/docs/technical-specifications/singpass-authentication-api/1.-authorization-endpoint/for-mobile-developers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.