11 articles tagged react.
Decouple the storefront from Odoo and you get a faster, safer, upgrade-proof shop. DragonflyDB caching, island architecture, GitHub version control, PR previews, VPN-isolated ERP, PWA mobile UX — everything we ship on every headless e-commerce project.
In an internal tool, the same order is on screen in five places at once, and every mutation has to remember all five. What a client-side store fixes that a cache can't — collections, live queries, optimistic writes that roll back on their own, and the working set that has to fit in a browser.
A home-screen icon, instant repeat visits and a notification when the order ships — you can have all three without two codebases and a review queue. What a PWA storefront genuinely delivers in 2026, where the service worker earns its place and where it quietly lies to your customers, the iOS caveats that decide your push reach, and the parts that still need a real native app.
You don't have to replatform to get a fast shop. Keep WooCommerce as the order engine and wp-admin your team knows, put React in front of it, and be honest about the one hard part: checkout.
Thirteen services across four groups need more than a hover dropdown. The roles a navigation menu must not use, what a portalled panel does to your tab order, and why the mobile menu is a different component rather than a smaller one.
Prefetch-everything wastes bandwidth, prefetch-on-hover fires too late, and neither exists on a phone. Cursor trajectory, tab distance and scroll direction are better signals — and this site already runs them.
When your primitive library changes direction, you migrate deliberately. Mapping Radix patterns onto Base UI, the accessibility differences that surprised us, and the codemod that did the boring three quarters.
React Server Components moved the data question out of the client bundle and into the render. For pages backed by an ERP, that's not a trend to adopt blindly — it's a boundary worth drawing precisely.
Every custom build ships two frontends — the one your customers see and the one only your client's own staff opens. The first earns Next.js. The second is usually paying a tax for machinery it never uses.
Language in the URL, slugs in a translation map, detection demoted to a suggestion — plus the tooling question: when we reach for next-intl vs Paraglide JS, and why Tolgee runs the translations from our own clusters.
Your ERP answers in 800 ms and no amount of React tuning changes that. What does: not asking twice. The query-key, staleTime and invalidation patterns we use in front of Odoo.