Yup, that's the overhead I'm referring to. With a platform team at play, you now have an extra dependency for all other teams - both technical and communication-wise - and that adds some friction.
The question is, are the efficiencies gained more than the added friction/overhead. In our case, the answer was no. So we moved away from micro-frontends.
How do you handle important libraries (common functionality) for your teams in the backend?
Sure, it's possible to remove all dependencies from a teams project by copy and pasting the code or by reinventing the wheel, but I'm not sure if these options are better than carefully chosen dependencies (including some maintained by other teams).
The question is, are the efficiencies gained more than the added friction/overhead. In our case, the answer was no. So we moved away from micro-frontends.