[minimaxir]

For internal projects/webpages (similar to Google Data Studio as mentioned), where you would expect the user to only be using it on a desktop, having no mobile support is fine.

But for external projects/webpages in 2016, where atleast 1/3 of usage can come from mobile devices, having a lack of mobile support is a complete, 100% nonstarter. And there are plenty of competing React UI frameworks with mobile support already.

[eyko]

> And there are plenty of competing React UI frameworks with mobile support already.

Citation needed.

In all honesty though, good quality UI frameworks with good mobile support are on the top of my "#want" list.

[woah]

There are a bunch of bootstrap components ported to React in the Reactstrap project.

[ethanbond]

I'm not sure how you come to this distinction between internal/external. The delineation is much simpler and more obvious. Is Blueprint made for mobile use cases? No. Therefore it's highly optimized for non-mobile use cases. Despite the buzzword focus on mobile applications, there's still plenty of work being done (and left to do!) outside of that. For those uses, Blueprint is great!

This is especially valuable for teams that don't have the design talent necessary to generate something as visually rich and feature complete as Blueprint. But you're right, a mobile framework it is not.

[serb348]

Such As?