ACB ONE - OPTIMIZING PERCEIVED PERFORMANCE & TRANSACTION FLOW

01 - Startup Delay and the Silent Wait Experience

Context: What happens at launch

When users tap the application icon, the sequence unfolds as follows:

App icon tapped

• → Static brand logo
• → 20-30 seconds of no visual feedback
• → Login screen appears

This delay happens before users can access any features. In a financial product, the entry moment is critical. It sets the tone for reliability, control, and security. When the system remains static for an extended period, uncertainty begins to build before interaction even starts. The issue here is not purely technical - it is experiential.

Expectation vs. reality

In digital products today, speed is not a luxury. It is a baseline expectation. Users generally expect immediate or near-immediate system response when opening an app. When the startup duration extends beyond several seconds - especially without feedback - it disrupts flow and weakens perceived competence.

In this case, the startup state includes:

• No loading indicator is shown
• No animation communicates progress
• No progress feedback
• No confirmation that the system is functioning

This creates a silent wait state. In high-trust environments such as banking, silence can easily be interpreted as instability. And perceived instability directly affects trust.

Public user feedback as evidence

To verify whether this perception was subjective, I collected recent public user reviews regarding startup performance. Below are unedited screenshots of recurring feedback:

Across these reviews, several patterns consistently appear:

Users repeatedly describe the app as:

• "Too slow"
• "Every time I open it, it lags."
• "Have to wait 20–30 seconds before I can access the app."

Some explicitly compare loading speed to other banking applications, noting that competitors reach the login screen significantly faster. Three clear signals emerge:

Recurring frustration

The delay is described as frequent, not occasional.

Competitive comparison

Users are benchmarking speed against other banking apps, which positions the issue as a competitive disadvantage.

Pre-interaction friction

The frustration occurs before login - meaning dissatisfaction forms before any transaction or task begins. Notably, most feedback criticizes speed, not interface design. This distinction is important. The primary issue is performance. However, the absence of feedback during the waiting period likely intensifies perceived slowness.

Defining the scope of intervention

The root cause of prolonged startup time is likely related to system architecture and backend process.

Addressing actual loading speed would require technical optimization beyond the scope of this redesign exploration. This project does not attempt to justify the delay. Nor does it present visual treatment as a substitute for engineering improvement. Instead, it focuses on a narrower but meaningful question: If waiting cannot be eliminated immediately, can its psychological impact be reduced?

This defines the UX intervention boundary. Backend optimization improves real speed. UX intervention improves perceived stability. Both matter - but they operate at different layers.

Reducing the psychological impact of silent waiting

The most critical experiential gap is not just duration. It is silence. During the 20-30 second startup window, users receive no indication that progress is occurring. This increases the likelihood that they:

• Assume the app is frozen
• Force close and reopen
• Restart the waiting cycle
• Experience amplified frustration

To address this, the redesigned introduces a subtle mascot animation immediately upon launch.

The animation includes:

• Gentle motion to indicate system activity
• A short reassurance message "Chờ One 1 chút nhé, mọi thứ đang sẵn sàng"
• Visual continuity with brand identity

Why a mascot animation?

Most apps handle loading with a progress bar — and most users have learned to ignore them. ACB One already has a progress bar, but it only appears in the final seconds before the login screen. The silent stretch before it remains unaddressed.

Introducing "One" during this window serves three purposes.

• First, it creates brand consistency. The mascot already lives inside the app and represents ACB One's identity — bringing it into the launch moment extends that presence naturally, without introducing anything unfamiliar.
• Second, it turns a system state into a conversation. The message "Chờ One 1 chút nhé, mọi thứ đang sẵn sàng" reframes waiting as acknowledgment. The system is no longer silent — it is responding. Users are no longer waiting without reason — they are being spoken to.
• Third, it signals that the app is active. In the absence of any feedback, users reasonably assume something is wrong. A familiar character in motion communicates that the system is working — not frozen — without requiring any technical explanation.

Mascot used for conceptual exploration only. All rights belong to ACB Bank

The objective is not to mask slow performance. The objective is to:

• Provide system feedback
• Reduce uncertainty
• Prevent premature interruption
• Stabilize emotional response during unavoidable delay

The waiting time remains unchanged. But the experience shifts from silence to communication. In financial products, communication during delay is a form of reassurance. And reassurance reinforces trust.

Perceived waiting time vs. actual waiting time

It is important to distinguish between actual waiting time and perceived waiting time. Actual waiting time refers to the measurable duration (20-30 seconds before login appears).

Perceived waiting time, however, is shaped by:

• Visual feedback
• Motion cues
• Progress messaging
• Sense of system responsiveness

When a system remains static, users interpret the delay as longer than it objectively is. Silence increases uncertainty, and uncertainty amplifies frustration.

Conversely, when feedback is present - even if the duration remains unchanged - users experience:

• Greater sense of control
• Reduced anxiety
• Lower likelihood of abandonment
• Increased tolerance toward delays

In other words: The animation does not reduce the actual loading time. It reduces the psychological weight of the loading time. This distinction is critical. The intervention addresses emotional stability during unavoidable delay, while acknowledging that technical optimization remains the long-term priority.