Designing GoTo Unified Login SDK, unified login & sign-up system for Gojek, Tokopedia, and GoPay.
Year
2023
Responsibilities
Product Design,
Prototyping,
Usability Testing
Company
GoTo Group
Background
In 2021, Gojek and Tokopedia merged to form GoTo Group, bringing together three major consumer-facing apps: Gojek, Tokopedia, and GoPay.
Despite the merger, their login and signup experiences remained separate, forcing users to create multiple accounts and repeat authentication steps across apps.
This caused business friction and inflated OTP costs from repeated verifications via SMS and WhatsApp.
Role and Responsibilities
As the Product Designer in charge of this project, I led the end-to-end design of the unified login and signup SDK for Tokopedia, Gojek, and GoPay.
01
Mapping and analyzing login/signup flows across Tokopedia, Gojek, and GoPay
02
Understanding and designing within three distinct design systems to create outputs that align with each app's visual language
03
Leading weekly design reviews with GoTo product VPs and PMs from all three apps
04
Collaborating closely with engineers from Tokopedia, Gojek, and GoPay to deliver and implement the SDK
05
Collaborated with UX writers and localization team to deliver localized designs in English, Indonesian, and Vietnamese
06
Driving usability testing in collaboration with the GoTo research team: I prepared the research plan, built the Figma prototypes, conducted user interviews, and synthesized findings into a comprehensive usability report
Opportunity
Reducing redundancy for users and costs for business
Users increasingly expect fast and secure authentication experiences. Based on initial findings from the GoTo research team, many users are already familiar with Single Sign-On (SSO) methods through platforms like Google and Facebook, and they value the convenience of logging in without having to remember multiple credentials or repeat the signup process.
How might we simplify GoTo login and signup experience to match user expectations for speed and convenience?
On the business side, GoTo saw an opportunity to reduce rising OTP delivery costs caused by redundant verifications across apps.
Unifying user identity within the GoTo ecosystem also enabled deeper user insights, streamlined account management, and the potential for personalized, cross-platform experiences—allowing users to enjoy seamless access and benefits across Tokopedia, Gojek, and GoPay.
How might we reduce verification costs by unifying login systems across GoTo apps?
Key Strategy
To solve these challenges, we created the GoTo Unified Login SDK—a single software development kit that would power the login and signup experiences across Tokopedia, Gojek, and GoPay.
Our design strategy focused on consistency and modularity. We envisioned a shared user experience that reduced the friction of repeated login and signup processes across apps.
By consolidating user flow and UI patterns into a single SDK, we could streamline login & signup development cost for current and future GoTo apps—all while preserving each brand’s distinct visual identity.
Design Process
Documentation of existing flow across Tokopedia, Gojek, and GoPay.
Understanding existing login and signup experiences across apps
To lay the groundwork for a unified experience, I audited and compared the existing login and signup flows across Tokopedia, Gojek, and GoPay. This deep-dive helped us identify major inconsistencies and user experience gaps that needed to be resolved.
🔎 Key findings
01
Variations in available login methods (phone number, email, Google, etc.)
02
Variations in login page components (country code selection, language selection, help center CTA placement, etc.)
Proposed unified login flow in Tokopedia, Gojek, and GoPay.
Building a consistent user flow pattern across apps
I started by designing a modular login flow that could flexibly support multiple user journeys. Our goal was to ensure users encounter a predictable, familiar flow regardless of which app they use.
Priority
Login method
Steps to login
Preconditions
#1
SSO
1 step
Other GoTo app session available in user's device
#2
Trusted device
1 step
Device has been mark as trusted
#3
Input phone number or e-mail
3 steps
No precondition
#4
Google SSO
3 steps
User must have google account in their device
Login method prioritization table
Unifying and prioritizing login and signup methods
To enhance user experience and reduce unnecessary OTP costs, we prioritized login methods based on efficiency and availability. This prioritization framework guided how the SDK routed users through the authentication flow based on their current session state and device status.
Designing a configurable and scalable UI layout
To accommodate each app's requirements and edge cases, we defined a UI structure that could be configured based on need—without sacrificing consistency.
I led a component audit across all apps to identify common and optional elements, and designed a modular layout model that SDK consumers could toggle via config.
Classification
Component
Gojek
Tokopedia
GoPay
Core components
Welcome message
✅
✅
✅
Credential input field
✅
✅
✅
Main CTA "Continue"
✅
✅
✅
Help center entry point
✅
✅
✅
"From GoTo" branding
✅
✅
✅
Terms of Service agreement
✅
✅
✅
Optional components
Country code selection
✅
❌
✅
Language selection
✅
❌
✅
Login with Google
❌
✅
❌
Comparison between existing design system and new unified design system.
Keeping brand identity in the login page
While working on this project, I was also developing a new design system called GoTo UI—used in other cross-app initiatives like GoTo Profile and GoTo Unified Verification. However, for the login page specifically, I made the strategic decision to stick with each app’s existing design system. This is the first screen users see when opening the app, and preserving visual identity was crucial to avoid confusion.
Instead of introducing a new system, the SDK was built to adapt to each brand’s style guide, including colors, typography, and spacing rules. This allowed us to reduce engineering effort, accelerate rollout, and maintain a familiar look and feel for users across Tokopedia, Gojek, and GoPay.
Design Outcome
Introducing GoTo SSO for seamless login and signup across apps
For our users, Single Sign-On (SSO) enables them to log in with just one click in any GoTo app when system detect an active session in another GoTo app on their device.
Signing up also becomes easier through SSO, as we can utilize existing user credentials that already exist from other GoTo apps. This means users don't need to input as much credential information as in the regular signup flow.
We also unified the login experience using phone number or email credentials.
Previously, each app had different flow patterns and input validation rules. With the SDK, we standardized the user flow, UI structure, and error cases so users always know what to expect—no matter which GoTo app they are using.
Designing building blocks across apps
Our SDK-based approach also enabled us to build a shared set of UI components that work across all three apps. These components—input fields, CTAs, error messages, loading states—were designed to behave consistently while adapting to each brand’s visual identity.
This modular system accelerated development, ensured consistency, and allowed each team to plug the SDK in with minimal customization.
Project Result
🚀 SDK launched in October 2023
The GoTo Unified Login SDK was officially rolled out across Tokopedia, Gojek, and GoPay in October 2023, introducing a faster and more seamless authentication experience.
👤 Users loved the new SSO experience
Usability testing showed that the majority of users were able to easily complete login and signup tasks with the new design. Many praised the Single Sign-On (SSO) feature, which let them access other GoTo apps without having to re-enter their credentials.
"This (SSO Login) feature makes my login experience faster because I don't need to register again in Gojek, as it is already connected with my Tokopedia account."
-Female respondent, Gojek & Tokopedia Active User
⏱️ 30% faster login time
The redesigned login flow is projected to reduce P90 login time by 30%, decreasing the average time from 30 seconds to 20 seconds, thanks to the SSO login feature that removes the need for users to input their credentials and complete OTP verification.
💰 $3M in potential cost savings
If fully implemented across all GoTo consumer, driver, and merchant apps, the SDK could help the company save up to $3 million annually in login costs.
Reflections
Collaborating with cross-app stakeholders
This is my first opportunity at Tokopedia to work with international stakeholders from three distinct applications: Tokopedia, Gojek, and GoPay. Each one has its own unique needs and requirements.
To keep the project on track, I conducted weekly design reviews and design sprints with stakeholders from all three companies. This experience significantly sharpened my communication and collaboration skills.
Throughout the project, I also actively collaborated with software engineers from all three companies. This close collaboration allowed us to tackle engineering challenges, pinpoint and resolve technical issues, and ensure the smooth implementation of GoTo Login SDK across all three apps.
This experience sharpened my ability to navigate requirement uncertainty, negotiate trade-offs, and drive alignment across teams.
Next project
Tokopedia Login Kit