Hybrid Design Strategy

JPMorgan Chase

Introducing a groundbreaking approach to digital service design, enabling rapid development for the native app, all while enhancing user experiences.

Role

Design Lead for Strategy, UX, UI

The situation

Problems made public

Upon the release of the inaugural J.D. Power Banking App Satisfaction report, it became evident that Chase, despite having the world's top-rated banking app, still had essential feature gaps. Notably, the inability to change one's email address stood out.


In response to this revelation, the leadership team swiftly engaged with the mobile team to determine the timeline for achieving feature parity. These gaps posed a growing risk of eroding the trust and business of Chase's most valued customers.

Bandwidth limitations

It became evident that the Chase Mobile® app team, although highly capable, was operating at full capacity and had become a persistent bottleneck for any additional requests outside the existing roadmap within Chase's app ecosystem.

Solutions with staying power

As a lead on the team, my mission had two core objectives:


  1. To unblock teams and business lines, enabling them to swiftly launch these essential capabilities.


  2. To establish a system that would permanently alleviate the bottleneck, all while upholding the exceptional user experience our customers had come to cherish and anticipate.

How might we...

Bring existing web features into the Chase Mobile® app without building them from scratch?

Bring existing web features into the Chase Mobile® app without building them from scratch?

Bring existing web features into the Chase Mobile® app without building them from scratch?

Bring existing web features into the Chase Mobile® app without building them from scratch?

Build

once

Deploy everywhere

Deploy everywhere

Deploy everywhere

Challenges

Navigation

Framed Chase online experiences presented potential challenges. Specifically, web pages had a unique method of going back or closing out, known as the modal header. Framing this modal header would lead to redundancy with the native header. If a customer tapped the back arrow on the web modal header, they would navigate to web experiences instead of the native ones.


In simpler terms, customers could access the entire chase.com from within their native app.


Visual

Mobile web and native experiences employed similar but slightly distinct design languages, which posed a risk of customers recognizing that they were viewing a webpage within their native app. Mobile web pages also featured higher information density and complexity compared to native pages.

Above—Using native header back navigation will take the customer back to their native menu. Upon tapping back again, it will guide the customer to their native dashboard.

Above—Using native header back navigation will take the customer back to their native menu. Upon tapping back again, it will guide the customer to their native dashboard.

Above—Using web modal header back navigation will take the customer back to a web view of Profile & settings. Upon tapping back again, it will guide the customer to their web dashboard. The native header is unaware that the customer has performed any navigation, showing "Profile & settings" incorrectly.

Above—Using web modal header back navigation will take the customer back to a web view of Profile & settings. Upon tapping back again, it will guide the customer to their web dashboard. The native header is unaware that the customer has performed any navigation, showing "Profile & settings" incorrectly.

Above—Using web modal header back navigation will take the customer back to a web view of Profile & settings. Upon tapping back again, it will guide the customer to their web dashboard.


The native header is unaware that the customer has performed any navigation, showing "Profile & settings" incorrectly.

Experience framework

Recognizing the potential for a negative impact on the overall native experience, we undertook the challenge of framing in existing web pages with great care. To ensure that all teams maintained or exceeded Chase's established high-quality standards for its native app, we established and wholeheartedly committed to the following strategic framework.


Unified

Our designs for hybrid pages were required to maintain visual consistency with Chase Mobile® app pages.


Usable

Customers using the native app should seamlessly interact with framed-in web pages, without realizing they are viewing web content.


Simple

Our commitment was to ensure that all experiences within the Chase Mobile app remained straightforward, eliminating unnecessary complexity.


Fast

Performance was a priority, with the goal of matching the speed and responsiveness of a native experience.

We recognized that framing in existing web pages had the potential to significantly degrade the overall native experience if not done well. In order to ensure all teams delivered at or above the high quality bar already set by Chase’s existing native app we established and committed to the following strategic framework.


Unified

Designs for hybrid pages should be visually consistent with Chase Mobile® app pages.


Usable

When in the native app, customers shouldn’t be able to tell they are viewing a framed-in web page.


Simple

All experiences within the Chase Mobile app should be simple, with no unnecessary complexity.


Fast

Performance should be on par with a native experience.

New feature playbook

We categorized experiences into three types and established identifying characteristics to guide our decisions on whether to build them in native, as hybrids, or as web-only experiences:


Hero product (full native)

Ex: Send money, Zelle, Pay card, view and search transactions.


Core features (hybrid JavaScript + CSS)

Ex: Edit email address, change phone number, update password, view credit score, FAQs.


Long-tail experiences (fully web)

Ex: Terms and conditions, MVP experiments, temporary partnership promotions.

We recognized that framing in existing web pages had the potential to significantly degrade the overall native experience if not done well. In order to ensure all teams delivered at or above the high quality bar already set by Chase’s existing native app we established and committed to the following strategic framework.


Unified

Designs for hybrid pages should be visually consistent with Chase Mobile® app pages.


Usable

When in the native app, customers shouldn’t be able to tell they are viewing a framed-in web page.


Simple

All experiences within the Chase Mobile app should be simple, with no unnecessary complexity.


Fast

Performance should be on par with a native experience.

Alignment of design patterns

To ensure a seamless integration of web pages into the Chase Mobile® app, it was imperative to harmonize the pattern differences between the two systems. Achieving pattern parity was essential to make web pages indistinguishable from native ones.


Audit and update

To bridge the gap, a comprehensive audit of both design systems was conducted. This audit identified the elements in each system that required updates to facilitate effective hybrid solutions. The key areas we identified for alignment were:


Typography

Typography for mobile web experiences needed to adhere to Chase Mobile app patterns.


Input fields

Input fields in mobile web experiences were aligned with the Chase Mobile app patterns.


Color palette

Ensuring visual consistency and compliance, all buttons within the Chase Mobile app conformed to Chase Online patterns.

I created guideline documentation on Confluence to allow for easy access by all of Chase's digital product teams and stakeholders.

Integrating hybrid into native IA

Native build

Native build

Hybrid (framed-in) build

Hybrid (framed-in) build

Legacy

before

Legacy

before

Hybrid

Hybrid

after

Get the full story

Learn more about the process, how we deployed, provided guidance, reduced feature gap, and exceeded business goals multiple times over.

Learn more about the process, how we deployed, provided guidance, reduced feature gap, and exceeded business goals multiple times over.

Design language alignment

Design language alignment

The Chase mobile web and Chase Mobile® app experiences had pattern differences that needed to be aligned. If web pages were to be framed into the mobile app, they needed to be in pattern parity in order for them to be indistinguishable from native pages.


To align the two systems, I performed a full audit of both design systems, and identified what elements in each system would need to be updated for hybrid solutioning to be affective.


Typography

Typography for mobile web experiences should follow the Chase Mobile app patterns.


Input fields

Input fields for mobile web experiences should follow the Chase Mobile app patterns.


Color palette

Colors should be visually consistent and compliant. All buttons on the Chase Mobile app should follow Chase Online patterns.

I created guideline documentation on Confluence to allow for easy access by all of Chase's digital product teams and stakeholders.