CHIMECARD Web · iOS · Android

    Earlier-career cross-platform UI work for ChimeCard — helping modernize the visual language and align web, iOS, and Android around core banking flows.

    FinTech
    Product Design
    Cross-Platform
    Design Systems
    CHIMECARD Web · iOS · Android

    Context

    This is earlier-career fintech product work included to show cross-platform execution across web, iOS, and Android.

    ChimeCard needed a more cohesive cross-platform experience across web, iOS, and Android. The existing UI language felt dated, the iOS MVP experience was uneven, and the Android strategy needed to be defined.

    Overview of the refreshed ChimeCard UI direction

    My Role

    My role focused on UI/UX design across ChimeCard's early web, iOS, and Android experiences. I helped define cross-platform flows, modernize the visual language, and create a more consistent experience across key banking tasks.

    • Designed web, iOS, and Android interface concepts.
    • Helped define key user flows for early product experiences.
    • Created UI patterns for account funding, offers, and in-app communication.
    • Partnered with engineering and business stakeholders to prepare concepts for implementation.

    Key Screens & Features

    Cross-platform UI

    Refreshed ChimeCard UI across platforms

    Offers

    ChimeCard offers experience on iOS
    ChimeCard offers experience on Android

    Account funding

    Account funding flow on iOS
    Account funding flow on Android

    In-app communication

    In-app messaging and helpdesk on iOS

    What I Learned

    • Cross-platform work goes smoother when flows are agreed on before UI exploration — especially across iOS and Android.
    • Shared patterns help, but each platform still needs intentional adaptation rather than a direct copy.
    • Banking tasks like funding and offers need extra clarity in hierarchy and language — users notice inconsistency quickly in money flows.

    What I'd Do Differently Today

    • Establish shared tokens and component patterns earlier so web, iOS, and Android do not drift during parallel work.
    • Build in more structured usability testing on high-stakes flows before handoff.
    • Align in-app and marketing surfaces sooner so the product feels like one experience end to end.