Acronis Cyber Protect

Acronis Cyber Protect combined backup, antivirus, and patch management into a single product — but the frontend told a different story. Three separate teams had built three standalone dashboards, each with its own tech stack, design patterns, and deployment pipeline. Users had to context-switch between different UIs to manage their cyber protection, and feature releases were constantly blocked by cross-team dependencies.

Unify the three product dashboards into a single cohesive console without stopping feature development. The core challenge was architectural: how do you let three independent teams continue shipping features at their own pace while converging toward a unified user experience? The tradeoffs were between integration speed (faster with tight coupling) and team autonomy (requires loose coupling).

I designed a micro-frontend architecture using Module Federation, where each product team owned a self-contained frontend application that plugged into a shared shell. The shell handled authentication, navigation, theming, and cross-product notifications. I established a shared component library (built on Material-UI) with strict API contracts — teams could use the components but couldn't modify them without going through a design review. One key decision I reconsidered: I initially proposed a shared Redux store for cross-product state, but after modeling the data flows, I realized each product's state was largely independent. I switched to an event bus pattern for the few cross-product interactions (e.g., backup status affecting the security dashboard), which dramatically simplified debugging.

Page load time decreased by 40%, trial sign-ups increased 22%, and task completion rates improved 18%. Each team went from bi-weekly coordinated releases to independent daily deployments. The shared component library reduced UI inconsistencies by 85% across products.