The Sign In With Google action allows users to quickly and securely log in to the Kuika application using their Google accounts. Instead of manual login, users can verify their identity with Google and gain access to all features in the application. This method improves the user experience, especially in end-user-focused applications, and provides secure identity verification.

Technical Features

Google OAuth 2.0 Integration: Users can log in to the system with their Google account.
Alternative to Manual Login: Users can log in with a single click instead of entering their username and password.
Web and Mobile Compatibility: Supported on both mobile and web applications.
SSO (Single Sign-On) Compatible: SSO support is provided through login with a Google account.
Quick Login: Users can quickly log in with their Google account without filling out additional forms.

Log in to the Kuika platform.
Open the project you want to work on from the Apps screen.
Go to the UI Design module.
Open the Properties panel on the right.
Create a button (for example: ‘Google with Sign In’).

Select the button and add the Authorisation > Sign In With Google action from the + ADD ACTION menu according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Use Case: One-Click Login with Google ID

In a social media application, when users click the ‘Google with Sign In’ button, the system performs identity verification using their Google account and redirects the user to the main screen of the application.

Example Application Steps:

Element: Sign in with Google button
Trigger: OnClick
Action: Authorisation → Sign In With Google
Additional Action: After login → Navigation → Navigate

Dynamic Role Assignment: Automatic role assignment can be made based on user information returned from Google (email extension, domain, etc.). For example, the ‘Admin’ role can be assigned to emails with the @kuika.com domain.
Post-Login Redirection: Different screens can be displayed to users based on their roles after login. For example, separate panels for students and teachers.
User Information Matching: Information from Google accounts (name, surname, email) can be matched with user profiles in the system and records can be updated.

Technical Risks and Precautions

Google API Configuration: The Kuika application must be registered on Google Developers Console, and fields such as Client ID, Client Secret, and Redirect URI must be defined correctly.
Unauthorised Access Control: Users who log in via their Google account should be granted access if they have an authorised role in the system. Otherwise, access should be restricted.
Matching Issue on First Login: If the user information returned from Google does not match the user record in the system, synchronisation issues may occur. Email should be the most commonly used field for matching.

Sign In With Google is a user-friendly login method that allows users to access applications in a modern and fast way. It provides secure login with Google authentication, improving the user experience and eliminating problems such as forgotten passwords. Thanks to its web and mobile compatibility, it can be easily used on any platform, offering a powerful solution for accelerating user acquisition and increasing security for applications.

‍