Skip to main content

2 posts tagged with "mobile"

View All Tags

Mobile Integration Guidance for Widgets and Age Verification

We've updated the documentation to clarify how k-ID is best integrated on mobile: for the age gate and consent steps, a natively built UX gives players the most seamless experience, and web embeds such as the age verification and age assurance URLs are displayed through system browser surfaces.

What's New​

Mobile Guidance for Age Gate and End-to-End Widgets​

The age gate and end-to-end widgets are fully supported on mobile. For the age gate and consent steps, we encourage building the UX natively with the custom workflow, following the CDK UX guidelines, for the most brand-integrated experience.

The age verification and age assurance URLs returned by the k-ID API are displayed the same way. See the mobile apps guide for the specific endpoints and challenge types.

Reworked Mobile Apps Guide​

The Mobile apps guide has been re-centered on age verification, the most common web embed on mobile:

Default Browser Method​

A default external browser method has been documented under the mobile implementation methods. It works on both Android (Intent.ACTION_VIEW) and iOS (UIApplication.open), fully supports AgeKeys, and returns focus to your app through the redirectUrl callback.

Device Orientation Guidance​

Age verification works best in portrait orientation. Because in-app browser surfaces inherit your app's orientation lock, apps with a locked landscape orientation should open the verification URL in the default external browser. The browser manages its own orientation, so users can rotate to portrait, and the redirectUrl callback returns them to your app when the flow completes.

Updated Documentation​

Next Steps​

  • If you're integrating on mobile, consider building your age gate and consent UX natively using the custom workflow and CDK UX guidelines for the most seamless experience
  • Use the default browser method for landscape-locked apps when displaying verification URLs

Mobile App Integration Guide and ConnectID Testing Updates

We've added comprehensive mobile app integration documentation and enhanced ConnectID testing resources to help you integrate k-ID widgets into mobile applications.

What's New​

Mobile App Integration Guide​

A new Mobile Apps quick start guide provides comprehensive documentation for integrating k-ID widgets into mobile applications. The guide covers:

  • Platform-specific implementation methods: Detailed guidance for Android (Custom Tabs, WebView, Trusted Web Activity) and iOS (ASWebAuthenticationSession, SFSafariViewController, WKWebView)
  • AgeKeys support: Clear documentation on which implementation methods support AgeKeys and WebAuthn
  • Result communication: Two approaches for receiving widget results—callback URLs (recommended) and DOM messages
  • Third-party app verification flows: Complete documentation on how verification methods like ConnectID redirect through third-party apps
  • Complete code examples: Step-by-step implementation examples for both iOS (Swift) and Android (Kotlin) with full code samples

ConnectID Testing Enhancements​

Enhanced ConnectID testing documentation with mobile app testing resources:

  • Mobile app test apps: Added links to ConnectID Mock Bank C test apps for iOS (TestFlight) and Android (Google Play) to validate the complete redirect flow in mobile applications
  • Testing section updates: Expanded the ConnectID testing section with a dedicated subsection for mobile app redirect flow testing

Updated Documentation​