State of the microfrontend architecture

I read about it and honestly I am totally against it. Having different teams handle different parts of the UI is a bad idea because over time, the design and approaches will diverge and you'll end up having a bunch of components that look similar but are different, and it will make the whole frontend a pain to work with.

AWS has separate teams per product, and each product team implements their own UI. To do anything, you usually have to go through different services and configure stuff. Even though they are all using the same style, the experience is awful and everybody is hating their UI.

Until you have an established product, my suggestion is to just go with the usual monolithic approach and start to split things out only when needed. Going form the start with a microservice architecture is painful and wastes a lot of time that can instead be invested in feature development (each microservice needs its own build/deployment process, and you still need one big project that combines them all in something usable. With frontend handling styling will become more complicated because you implement each microservice in isolation and style it accordingly, but then when combining, you have hierarchies of styles which will cascade to the isolated components).

Just my 2 cents.