Google authentication for React Native and Expo apps using the legacy Google Sign-In SDK.
@react-native-google-signin/google-signin is a React Native library that provides Google authentication for mobile apps on Android and iOS. It integrates the legacy Google Sign-In SDK to handle user sign-in, allowing developers to add Google-based login functionality to their React Native or Expo applications.
React Native and Expo developers building mobile apps for Android and iOS who need to implement Google Sign-In authentication.
It offers a free, open-source solution under the MIT license, simplifying the integration of Google authentication without requiring deep native code knowledge, though it uses deprecated APIs on Android.
Google Sign-in for your React Native applications
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Released under the MIT license, it provides Google authentication at no cost, making it accessible for hobbyists and budget-conscious projects, as highlighted in the README.
Specifically designed for React Native and Expo, it abstracts native SDK complexities, allowing developers to implement Google Sign-In with minimal native code, as stated in the key features.
Supports both Android and iOS platforms, ensuring consistent authentication flows across major mobile operating systems, which is a core feature mentioned.
With over 1 million npm downloads and trusted by indie hackers and large teams, it's a widely used solution with community backing, as noted in the README.
Relies on the legacy Google Sign-In SDK for Android, which is deprecated and may not receive future updates or support, a limitation openly acknowledged in the README.
Limited to Android and iOS; for web or desktop authentication, developers must use the premium version or other solutions, as the README promotes Universal Sign In for cross-platform needs.
Lacks features like configuration error diagnosis (Config Doctor), auto-detect, and advanced security options, which are only available in the paid premium version, creating a feature gap.
Common errors like DEVELOPER_ERROR can be time-consuming to debug without tools like the Config Doctor, as hinted in the premium version's features, making setup more complex.