Design
/
October 2025 – December 2025
Ojire Anywhere — PIN & Biometric Login
Improving return login for mobile merchants through PIN access, optional biometrics, clearer feedback, and recovery flows.
(Project details)
Company
Ojire
Role
UI/UX Designer intern
Year
October 2025 – December 2025
Helping merchants get back to work
I designed PIN and biometric login flows for Ojire Anywhere, a mobile POS app used by merchants.
The project responded to merchant difficulties shared through Ojire’s Sales team. My work covered first-time setup, returning-user login, input feedback, authentication errors, account recovery, and security settings.
Before: password-based login
The original login required a phone number or email address plus a password. PIN and biometric authentication were not available as returning-user login options.
Sales reported that frequent automatic logouts required merchants to sign in again, sometimes while serving customers. Forgotten or mistyped passwords added friction and increased the risk of account lockout.

The original experience required password entry through either phone-number or email login.
Understanding the problem through Sales feedback
Ojire’s Sales team relayed several recurring concerns: repeated login interrupted work, passwords were difficult to remember, and users lacked clear warnings about remaining attempts.
They also reported that PIN access would better suit many merchants’ preferences and device capabilities. Some devices did not support biometrics, so biometric login needed to remain optional.
The feedback also raised concerns about unclear PIN-entry indicators and suggested saved-credential support. These inputs helped define the proposed login experience; they were feedback relayed through Sales rather than findings from direct user interviews.
Defining the design priorities
I focused the design on five priorities:
Provide six-digit PIN access for returning users.
Offer optional biometrics on supported devices.
Make PIN-entry progress visible.
Explain login errors and remaining attempts.
Provide fallback and recovery paths.
The work addressed how users regain access after logout. Changing the app’s session timeout behavior was outside the confirmed design scope.
Setting up PIN access
After signing in with their credentials, users could create and confirm a six-digit PIN for future access.
The proposed setup then offered biometric activation on supported devices. Users could activate it or skip, keeping PIN access available without requiring biometric enrollment.
Create PIN → Confirm PIN → Biometric activation invitation.

PIN setup establishes a return-login option, followed by optional biometric activation.
Making PIN entry easier to follow
The feedback highlighted uncertainty around PIN input when indicators did not visibly change as digits were entered.
I designed active PIN indicators and pressed-key feedback to show progress. These states help users recognize how many digits they have entered and whether each tap has registered.

Changing indicators and pressed-key feedback make PIN-entry progress visible.
Offering optional biometric login
For users who enable biometrics, the flow provides another way to access the app using the device’s supported authentication method.
The design includes an activation invitation, permission step, and returning-user authentication state. PIN remains available for users who prefer it or cannot complete biometric authentication.


Biometric login adds another access option while retaining PIN as an alternative.
Providing a clear fallback
The flow accounts for unsuccessful recognition, unavailable biometrics, and exceeded biometric attempts.
When biometric authentication cannot be completed, users can return to PIN entry. If they select biometric login before activating it, a message directs them to Settings.

After failed biometrics attempts, users can log in by PIN Number

After failed PIN attempts, users can log in with a password or biometrics, with clear warnings before a temporary lockout.

If they select biometric login before activating it, a message directs them to Settings.

Fallback states explain what happened and how users can continue.
Explaining errors before access is restricted
Sales feedback highlighted that users did not have enough warning before their accounts were locked.
I designed progressive messages for incorrect entries and remaining attempts. Separate states explain when users need to switch to password login or wait before trying again.
The proposed messages make the next action explicit instead of showing the same generic error throughout the flow.

Progressive feedback communicates errors, remaining attempts, and available next steps.
Supporting PIN recovery
The Forgot PIN flow asks users to verify their password before creating and confirming a replacement PIN.
A completion message confirms that the PIN has been updated. Password recovery remains accessible for users who cannot complete the verification step.

A guided reset flow connects password verification with PIN recovery.
Giving users control in Settings
The security settings include biometric activation and deactivation, alongside options to change the PIN and password.
Confirmation messages communicate when biometric login has been enabled or disabled. This gives users a place to manage access preferences after their initial setup.

Users can manage biometric access from the app’s security settings.
Refining the flow for development
I explored references and several flow directions before refining the proposed experience through Sales and product-team feedback.
What I learned
The project reinforced the value of understanding users’ working conditions and device capabilities before choosing a login approach.
Sales feedback helped prioritize PIN access while keeping biometrics optional. Designing the unsuccessful paths also showed that clear feedback and recovery are essential parts of the login experience.
Next project

