docs: small updates (#64)

vonovak · web-flow · commit d92a0095da18 · 2025-03-24T08:47:34.000Z
diff --git a/docs/install.mdx b/docs/install.mdx
@@ -4,7 +4,9 @@ sidebar_position: 1
 
 # Installation
 
-There are two ways to consume the package: [premium](https://universal-sign-in.com) and free.
+There are two ways to consume the package: [paid](https://universal-sign-in.com) and free.
+
+Why paid? According to the [State of React Native Survey](https://results.2024.stateofreactnative.com/en-US/opinions/#opinions_pain_points_multiple), unmaintained packages are **the #1 pain point** of the React Native ecosystem. Your purchase enables the module reliability, and contributions to upstream SDKs such as [1](https://github.com/openid/AppAuth-iOS/pull/788), [2](https://github.com/google/GoogleSignIn-iOS/pull/402), [3](https://github.com/googlesamples/google-services/issues/426).
 
 [//]: # '🌟'
 
@@ -19,7 +21,7 @@ There are two ways to consume the package: [premium](https://universal-sign-in.c
   - iOS & macOS: Powered by the [Google Sign-In SDK](https://developers.google.com/identity/sign-in/ios/start)
 
 - **Licensed:** see [pricing](https://universal-sign-in.com/#pricing) and [license](https://universal-sign-in.com/license).
-- **Trusted**: A total of over 160k npm package downloads.
+- **Trusted**: A total of over 170k npm package downloads.
 - **Faster Sign-Ups**: Reduce sign-up and sign-in times on Android by up to 50%, according to [Google](https://developer.android.com/identity/sign-in/legacy-gsi-migration#authentication).
 - **See the UI**: [screenshots](screenshots) of the features.
 
@@ -29,23 +31,23 @@ There are two ways to consume the package: [premium](https://universal-sign-in.c
 
 [//]: # '🖥️ **Unified API** - Write code once, deploy everywhere.'
 
-📱 **An example app** - to showcase all Universal sign in features
-
-_Your purchase enables improvements in the module and upstream SDKs (such as [1](https://github.com/openid/AppAuth-iOS/pull/788), [2](https://github.com/google/GoogleSignIn-iOS/pull/402), [3](https://github.com/googlesamples/google-services/issues/426))._
+📱 **An example app** - to showcase all features on native and web
 
 ### Public version (free)
 
 Available on the public npm registry under MIT license, this version:
 
-- Uses the functional, but deprecated [legacy Android Google Sign-In](https://web.archive.org/web/20240308064911/https://developers.google.com/identity/sign-in/android/start-integrating) which will be removed from the Google Play Services Auth SDK (`com.google.android.gms:play-services-auth`) later in 2025. The free version will continue to use a version where the deprecated SDK is present.
+- Uses the functional, but deprecated [legacy Android Google Sign-In](https://web.archive.org/web/20240308064911/https://developers.google.com/identity/sign-in/android/start-integrating) which will be removed from the Google Play Services Auth SDK (`com.google.android.gms:play-services-auth`) later in 2025. The free package will continue to use a version where the deprecated SDK is present.
 - Has platform support limited to Android and iOS.
 - Contains none of the extra features listed above.
 
 > If you want to migrate from the public version to the Universal version, follow the [migration guide](migrating#migrating-from-original-to-universal-sign-in).
 
 ## Obtaining Universal Sign In {#obtaining-access}
 
-Universal sign in requires [purchasing a license](https://universal-sign-in.com/#pricing), after which you will be able to configure your (or your colleagues') access to the private npm package and to the private repo with the sources and examples. Alternatively, as an Expo customer, obtain access through this [form](https://forms.gle/tpP7TfUGW1CwgaEZ8).
+Universal sign in requires [purchasing a license](https://universal-sign-in.com/#pricing), after which you will be able to configure your (or your colleagues') access to the private npm package and to the private repo with the sources and examples.
+
+> Are you an EAS customer? You may be able to access the premium version for free, [learn more](https://forms.gle/tpP7TfUGW1CwgaEZ8).
 
 [//]: # 'Note that this version is distributed under a [custom license](license).'
 
diff --git a/docs/license.md b/docs/license.md
@@ -6,4 +6,4 @@ sidebar_position: 80
 
 The Original module is licensed as MIT, the Universal sign in module has [this license](https://universal-sign-in.com/license).
 
-Please do get in touch if you have any questions or concerns about the license!
+Please [get in touch](mailto:hello@universal-sign-in.com) if you have any questions or concerns about the license!
diff --git a/docs/setting-up/get-config-file.mdx b/docs/setting-up/get-config-file.mdx
@@ -1,5 +1,6 @@
 ---
 sidebar_position: 15
+sidebar_label: Configuration
 ---
 
 # Obtaining configuration information
@@ -29,35 +30,43 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 <Tabs>
-  <TabItem value="eas" label="When using Expo EAS">
-    If you use [Expo EAS](https://expo.dev/eas), run `eas credentials` to obtain the Keystore information, which includes the SHA-1 fingerprint. See [EAS credentials docs](https://docs.expo.dev/app-signing/managed-credentials/#inspecting-credentials-configuration) to learn more.
-  </TabItem>
-<TabItem value="local" label="When developing locally">
-  1. From your project root, `cd android && ./gradlew signingReport`.
-  2. Scroll to the top of output, see the fingerprints. Debug fingerprint is used for debug apk,
-  release fingerprint is used for release APK.
-</TabItem>
-
   <TabItem value="playStore" label="When releasing via Google Play Store">
-    Check if "Google Play App Signing" is enabled for your app [in the console](https://play.google.com/console/u/0/).
+    Check if "Google Play App Signing" is enabled for your app [in the console](https://play.google.com/console/).
     If it is enabled, you need to take the following steps:
 
-1. In Google Play Console, navigate to: \<Your App\> -> Release section (in the left sidebar) -> Setup -> App Signing.
-2. Under the "App signing key certificate" _and also_ "Upload key certificate", take note of `SHA-1 certificate fingerprint`. That's a total of two or more fingerprints (Play Store sometimes has more than one "App signing key certificate"!).
+    1. In Google Play Console, navigate to: \<Your App\> -> Release section (in the left sidebar) -> Setup -> App Signing.
+    2. Under the "App signing key certificate" _and also_ "Upload key certificate", take note of `SHA-1 certificate fingerprint`. That's a total of two or more fingerprints (Play Store sometimes has more than one "App signing key certificate"!).
 
   </TabItem>
+
+<TabItem value="eas" label="When using Expo EAS">
+  If you use [Expo EAS](https://expo.dev/eas), run `eas credentials` to obtain
+  the Keystore information, which includes the SHA-1 fingerprint. See [EAS
+  credentials
+  docs](https://docs.expo.dev/app-signing/managed-credentials/#inspecting-credentials-configuration)
+  to learn more.
+</TabItem>
+
+  <TabItem value="local" label="When developing locally">
+    1. From your project root, `cd android && ./gradlew signingReport`.
+    2. Scroll to the top of output, see the fingerprints. Debug fingerprint is used for debug apk,
+    release fingerprint is used for release APK.
+  </TabItem>
 </Tabs>
 
+<br />
+<br />
+
 ### Step 2: Add SHA-1 hashes to Firebase or Google Cloud Console {#step-2}
 
 Using _all_ of the SHA-1 fingerprints obtained in the previous step, follow the instructions below.
 
 <Tabs queryString="firebase-or-not">
   <TabItem value="firebase" label="When using Firebase">
-1. Sign in to Firebase and open your project.
+1. Sign in to [Firebase Console](https://console.firebase.google.com/) and open your project.
 2. Ensure that in the "Authentication" menu, "Google" is enabled as "Sign-in method".
-3. Click the Settings icon and select Project settings.
-4. In the "Your apps" card, select the app you need to add SHA-1 to.
+3. Click the settings icon and go to "Project settings".
+4. Scroll down to "Your apps" section, and select the app.
 5. Click "Add fingerprint".
 6. Check that "Package name" is correct.
 7. Download the `google-services.json` file.
@@ -67,8 +76,9 @@ Using _all_ of the SHA-1 fingerprints obtained in the previous step, follow the
   </TabItem>
 
 <TabItem value="cloud-console" label="When not using Firebase">
-  Follow the "Create authorization credentials" instructions
-  [here](https://developers.google.com/identity/protocols/oauth2/native-app#android) to create an "OAuth client ID" of type Android for each of the SHA-1 fingerprints you obtained - see the screenshot below.
+  Create an OAuth Client ID of type Android in [Google Cloud Console](https://console.cloud.google.com/apis/credentials?project=_) for each of the SHA-1 fingerprints you obtained - see the screenshot below.
+
+Alternatively, use <a href="https://console.developers.google.com/henhouse/?pb=%5B%22hh-0%22%2Cnull%2Cnull%2Cnull%2C%22https%3A%2F%2Fdevelopers.google.com%22%2Cnull%2Cnull%2Cnull%2C%22Configure%20a%20project%20for%20Google%20Sign-In%22%2C1%2Cnull%2Cnull%2C0%2C1%2Cnull%2Cnull%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2Cnull%2C0%5D" target="_blank">this wizard</a>.
 
 You will _NOT_ need the created IDs later - the only goal here is for them to be created in the Google Cloud Console.
 
@@ -88,18 +98,19 @@ Read below on how to set up Google Sign In for your iOS app.
   <TabItem value="firebase" label="When using Firebase">
 
 1. Sign in to [Firebase Console](https://console.firebase.google.com/) and open your project.
-2. Click the settings icon and go to "Project settings".
-3. Scroll down to "Your apps" section, and select the app.
-4. Check that "Bundle ID" is correct.
-5. Download the `GoogleService-Info.plist` file.
+2. Ensure that in the "Authentication" menu, "Google" is enabled as "Sign-in method".
+3. Click the settings icon and go to "Project settings".
+4. Scroll down to "Your apps" section, and select the app.
+5. Check that "Bundle ID" is correct.
+6. Download the `GoogleService-Info.plist` file.
 
   </TabItem>
 
   <TabItem value="cloud-console" label="When not using Firebase">
 
     Remember that _all_ created client IDs can be found in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials?project=_).
 
-    Obtain the "iOS OAuth Client ID" _and_ "iOS URL scheme" (also known as `reversed client id`): Create or use an existing OAuth Client ID of type iOS in [Google Cloud Console](https://console.cloud.google.com/apis/credentials?project=_). Alternatively, use <a href="https://console.developers.google.com/henhouse/?pb=%5B%22hh-0%22%2Cnull%2Cnull%2Cnull%2C%22https%3A%2F%2Fdevelopers.google.com%22%2Cnull%2Cnull%2Cnull%2C%22Configure%20a%20project%20for%20Google%20Sign-In%22%2C1%2Cnull%2Cnull%2C0%2C1%2Cnull%2Cnull%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2Cnull%2C0%5D" target="_blank">this wizard</a>.
+    Obtain the "iOS OAuth Client ID" _and_ "iOS URL scheme" (also known as `reversed client id`): Create an OAuth Client ID of type iOS in [Google Cloud Console](https://console.cloud.google.com/apis/credentials?project=_). Alternatively, use <a href="https://console.developers.google.com/henhouse/?pb=%5B%22hh-0%22%2Cnull%2Cnull%2Cnull%2C%22https%3A%2F%2Fdevelopers.google.com%22%2Cnull%2Cnull%2Cnull%2C%22Configure%20a%20project%20for%20Google%20Sign-In%22%2C1%2Cnull%2Cnull%2C0%2C1%2Cnull%2Cnull%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%2C0%2Cnull%2Cnull%2Cnull%2C0%5D" target="_blank">this wizard</a>.
 
     You will need the iOS Client ID and iOS URL scheme later.
 

Original file line number	Diff line number	Diff line change
`@@ -6,4 +6,4 @@ sidebar_position: 80`
`6`	`6`
`7`	`7`	`The Original module is licensed as MIT, the Universal sign in module has [this license](https://universal-sign-in.com/license).`
`8`	`8`
`9`		`-Please do get in touch if you have any questions or concerns about the license!`
	`9`	`+Please [get in touch](mailto:[email protected]) if you have any questions or concerns about the license!`