Microfrontends are extremely popuplar right now, but here’s the uncomfortable truth: most of us are doing them wrong. The majority of materials, blog posts, and tutorials frame microfrontends as a purely technical solution: split your UI into smaller chunks, add some tooling magic, and voilà—problem solved. Except… it isn’t.
Microfrontends are not about making your fragments smaller; they’re about making your teams faster. They’re an organizational strategy disguised as an architectural pattern. When misapplied, they add overhead, slow you down, and leave you wondering why everything feels harder instead of easier.
In this talk, I’ll challenge the dominant narrative around microfrontends, expose the misconceptions that current resources perpetuate, and reframe the pattern for what it really is: a way to align software boundaries with team boundaries to maximize productivity and autonomy. You’ll leave with a sharper lens for evaluating whether microfrontends are the right fit for your context, and a practical understanding of how to avoid the traps that lead to a false sense of progress.
I've been developing microfrontends since 2012, and I'll share all my learnings with you. It’s time to stop slicing for the sake of slicing—and start using microfrontends the way they were meant to be used.