iOS Support

Understand how Clever login works on iOS and which iOS implementation guide to read next.

Use this page to understand how Clever login works on iOS and which iOS implementation guide to read next.

How users reach your app on iOS

On iOS, students and teachers can reach your app through Clever in a few different ways depending on whether they are using the Clever app, the Clever Portal, or Clever Badge login.

Universal Links

Universal Links are the recommended way to connect Clever login to your native iOS app.

When a user selects your app from the Clever Portal in Safari or from the Clever app, iOS can recognize the link as one your app handles and open your native application directly.

  • User experience: a direct transition from Clever to your native app
  • Setup requirement: host an Apple App Site Association (AASA) file on your domain and configure Associated Domains in Xcode

Clever app-to-app behavior

Many students use the Clever iOS app as their starting point. When a user taps your app inside the Clever app:

  • if your native app is installed, Clever can hand the user off to that app
  • if your native app is not installed, Clever can send the user to the App Store or open your web experience in an embedded browser

Clever Badge secondary login

For students who use Clever Badges, the Clever iOS app can act as the authentication entry point. A student scans their Clever Badge with the iPad camera and signs in to the Clever app.

After the student is authenticated in the Clever app, they can launch integrated learning apps on that device without entering another username and password.

Key integration principles

No matter how users arrive at your app, your iOS integration should follow these principles:

  • Use ASWebAuthenticationSession
    Apple recommends this framework for OAuth and OIDC login flows. It helps share the user’s session securely between Safari and your app.

  • Support the "Back to Clever" breadcrumb
    iOS provides a system navigation link in the top-left corner so users can return to the Clever app. Make sure your UI does not block or hide it.

  • Provide a web fallback
    If a user does not have your native app installed, route them to a mobile-friendly web experience when possible.

Read the right iOS guide next