cells-app-architecture

A Cells feature package requires a standard directory layout organizing pages, data managers, shared components, mixins, configs, utils, and styles. This structure enforces clear component boundaries and defines data manager placement for maintainability.

The best way to manage routing and bridge communication in a Cells app is using publish/subscribe channels for internal navigation and external bridge routing patterns. This ensures decoupled communication between feature packages and the app shell.

Data managers in BBVA Cells architecture handle API logic and state separation within feature packages. They define specific data duties, isolating API integration from UI components to maintain clear component responsibilities.

Cells architecture supports micro-frontends and feature flags by providing advanced structural patterns. It addresses feature toggling, performance optimization, and browser testing checkpoints within the overall application composition.

Plan app shell versus feature responsibilities when designing new features like a payment dashboard. This separation clarifies where API logic, routing, and UI components belong, ensuring proper integration patterns and component boundaries.

Organizing feature architecture in Cells requires strict adherence to official documentation to avoid boundary violations. Complex features may introduce routing conflicts if publish/subscribe channels and bridge communication patterns are not carefully mapped.