Skip to evidence →
tanyasingh
← Back to evidence index
Exhibit C · Open

Evidence folder

CapitalIQ Pro Offline PWA

Client
S&P Global · via EPAM
Role
Senior Frontend Engineer
Timeline
EPAM · product extension
28%Mobile engagement liftMeasured increase after offline-capable journeys shipped.
95%Test coverageOn owned component and PWA surfaces.

Objective

Extend CapitalIQ Pro with an offline-first PWA experience — service workers, sync, and embedded Tableau analytics that still felt native to the corporate design system.

Decision log

Choices under review — why they stuck, and what they cost.

  1. Decision 01

    Service-worker offline shell before feature sprawl

    WhyMobile engagement hinged on reliability in constrained networks, not more widgets.

    TradeoffSync edge cases needed careful product negotiation.

  2. Decision 02

    Design-system components as the delivery unit

    Why40+ production components kept the PWA visually and behaviorally consistent with the broader S&P surface.

    TradeoffSlower first paint of new ideas — higher long-term coherence.

What we built

  • Offline-first PWA shell with sync
  • 40+ design-system components
  • Tableau embedded analytics integrations

Filed stack · React · Service Workers · PWA · Tableau · Tailwind CSS

Panel observations · people

  • Obs. A

    Documented offline patterns for subsequent contributors

  • Obs. B

    Raised the quality bar on component tests toward 95% coverage on owned surfaces

Discuss this kind of engagement → Contact