It could very well be that I&#x27;ve completely misunderstood the intention of these frameworks then.<p>I was under the impression that at the end of the day you&#x27;re creating either React components and&#x2F;or Angular directives when you&#x27;re building a web application.  And the particular framework takes care of how the view changes when the model changes, it provides you with some abstractions like Resources (to talk to REST APIs) and Routers (for navigation).  Even when you look at ExtJS I don&#x27;t see why they couldn&#x27;t provide ReactExtJS or AngularExtJS by just wrapping their widgets so that you&#x27;re either creating them with &quot;props&quot; or by specifying the initial &quot;scope&quot; if you&#x27;re doing it Angular directives, for example.<p>Creating standardized widgets which can be &quot;wrapped&quot; to expose a React (prop&#x2F;state) or Angular (isolated scope directive) style interface, and then &quot;skinned&quot; (Bootstrap or Material Design or whatever) I would have thought would be the logical thing to do.  As another poster commented, perhaps this is what people are calling &quot;Components&quot;?  However, I&#x27;m pretty sure it could be done right now with what we currently have.<p>If you say it&#x27;s an extremely narrow need, I understand because typically I end up facing problems no one else seem to have :)