1. Configuration
  2. Mobile app configuration in the platform

Rownd supports React-native, Flutter, and native iOS and Android apps. After integrating Rownd’s simple SDKs, you just need a few pieces of information to create powerful, universal sign-in links.

Rownd’s universal Sign-in Links provide a seamless and user-friendly authentication solution for mobile apps by allowing users to be directed to the app and signed in automatically. This innovative feature streamlines the authentication process, eliminating the need for users to remember passwords or manually enter credentials within the app.

By utilizing universal Sign-in Links, users receive a unique, one-time-use link via their preferred communication method, such as email or SMS. Upon clicking the link, users are automatically directed to the mobile app and are signed into their account, providing a frictionless user experience.

Integrating Rownd’s universal Sign-in Links into your mobile app simplifies the authentication process for your users, reduces the barriers to entry, and promotes higher user engagement. By offering an efficient and secure authentication method, you can foster trust in your app, enhance user satisfaction, and ultimately, achieve greater success with your mobile app.

A Rownd Mobile SDK must be installed in your app to use this feature.

Universal links are a powerful technology that enables deep linking to specific content within a mobile app or, if the app is not installed, directs the user to their mobile device’s specific app store. This versatile feature provides a seamless user experience by bridging the gap between web content and native app content.

When a user clicks on a universal link, the operating system checks whether the app associated with the link is installed on the device. If the app is installed, the user is directed to the specified content within the app. If the app is not installed, the user is redirected to the appropriate app store (the Apple App Store for iOS devices or the Google Play Store for Android devices) to download the app.

Universal links offer several benefits for both users and developers:

  • Simplified user experience - By directing users to the relevant content or app store, universal links create a more streamlined and intuitive user journey, which can lead to increased user engagement and retention.
  • Improved conversion rates** - By reducing friction in the user experience and lowering the barriers to entry, universal links can help boost conversion rates for app installations that lead to user sign-ups.
  • Enhanced security - Universal links are more secure than legacy custom URL schemes, as they rely on the app’s domain and can only be used by the associated app, thus reducing the risk of phishing attacks or unauthorized access.


To enable mobile app authentication, you must first configure your mobile app details in the Rownd dashboard.

  1. Select Sign-in methods from the left navigation menu.
  2. In the Sign-in preferences section, locate Mobile app sign-in
  3. Press Enable.

Configuring mobile apps only takes a few minutes.

If this is your first time configuring mobile app sign-in, you will be prompted to provide some details about your app.

Set mobile subdomain

Rownd provides a customizable, unique subdomain for each mobile-enabled app. This subdomain is used to steer users to the correct app when they click on a link in an email or SMS message. If your app is already installed on the user’s device, the subdomain will cause the app to open automatically when users click on the link.

  1. Enter a subdomain name in the Subdomain field. (e.g., myapp for myapp.rownd.link - the .rownd.link portion is added automatically).

Provide app details

Configuration information is needed for your app on a per-platform basis. Press the toggle next to the platforms your app supports (e.g., iOS and Android).

For each platform, provide the requested information in the available fields.

iOS apps
  • App store URL - The direct link to your app in the Apple App Store
  • Bundle IDs - A comma-separated list of bundle IDs for your app (e.g., com.example.myapp)
  • Team ID - The team ID for your app as shown in the Apple Developer Portal (e.g., 15GKOXA3H6)
Android apps
  • Play store URL - The direct link to your app in the Google Play Store
  • Package name - The package name for your app as shown in the Google Play Console (e.g., com.example.myapp)
  • SHA256 certificate fingerprints - For dev/test apps signed locally or manually, obtain the SHA256 hash from your keystore. For apps distributed through the Google Play Store that use automatic signing, obtain the SHA256 hash from the Google Play Console.