Hello bricks team,
I kindly request that you add full, native support for the WordPress Interactivity API (introduced in WP 6.5+) to all interactive elements in Bricks — including Tabs, Accordion, Slider/Carousel, Offcanvas, Modal, Forms, Ajax Load More, Product Add to Cart, Filters, and any future interactive components.
Why this is now essential?
- Dramatic performance boost (~10 KB, no hydration, instant reactivity)
- Future-proof alignment with WordPress Core (the official standard since WP 6.5)
- Massive JavaScript reduction (from 200–400 KB → under 50 KB)
- 95–100 PageSpeed Mobile scores become realistic
- Zero conflicts with block themes (Twenty Twenty-Five, Twenty Twenty-Six, etc.)
- Cleaner, standardized developer experience using core directives
Most importantly: even WooCommerce is already doing it
Since WooCommerce 8.9+ (and especially 9.0+), all new cart/checkout blocks, the new Add to Cart block, mini-cart, product gallery, filters, and upcoming features are built exclusively with the Interactivity API. This means that on any serious e-commerce site using Bricks + WooCommerce, we are currently loading two completely different reactive systems side-by-side — which creates unnecessary bloat and potential conflicts. Native support in Bricks would eliminate this duplication overnight and give Bricks sites a huge advantage over every other builder.
Adding full Interactivity API support isn’t just a nice feature anymore — it has become a strategic necessity to stay aligned with WordPress Core and WooCommerce in 2025–2026.
Please consider putting this on the roadmap with high priority. It would make Bricks the undisputed performance + compatibility leader.
Thank you for building an incredible tool — this evolution would make it truly unstoppable.
Best regards