FDSG — one design language across a fintech platform
When I joined FYERS, design didn't have one language — it had several dialects. Style guides were scattered, half-finished, or duplicated, so the same element existed in different ways across web, iOS, and Android. That cost the business twice: designers rebuilt instead of designed, and users met a product that felt subtly inconsistent — costly in a product built on trust.
I became one of the louder voices for a single, versioned source of truth rather than more scattered guides. After v1.0, I took over and drove FDSG 2.0 and 2.1 across web and mobile — a visual reset from gradient-heavy to clean and minimal, then a pass that tightened spacing and density. The deeper change was organizational: I helped move FYERS from a split UX/UI relay to end-to-end Product Designers, which made adoption fast because the people using the system understood it top to bottom.
When engineering built it into code, we were honest that design-to-code was never a 100% match — naming the gap is what kept the system improving instead of quietly rotting.
Read the full case study