Goodbye presentational and container components?

1 min read

I had been following the Presentational and Container pattern invented by Dan Abramov, although it seems that even Dan has changed his views on the usefulness of this pattern with the introductions of hooks, as mentioned in the “updated:” section at the top of that article.

I found another article useful on freecodecamp when talking about the failings of the Presentational and Container pattern.

The problem with the Container vs Presentational model is that it tries too hard to define component responsibilities in terms of component inner-workings. The key takeaway is to view component design in terms of component interfaces.

Hearing about the switch to focus on Component interfaces (or API design) was a "ah ha" moment for me. When a developer is looking for a component, they are mainly interested in how to use the component, not the implementation.

That article talks about Universal and Global components which I've also heard called Base/Variants. I do also appreciate the differentiation of View components in this article because I think that was the main benefit I found from using Container components.

I had been guilty of following the Presentational and Container pattern just because it's a best practice which should have been a warning sign of its uselessness.

Was this article helpful?

I'm writing an ebook called Robust UI. Subscribe to get chapters from it via email