Frequently asked questions
Blueprint was designed from the ground up for desktop applications. It has not been tested thoroughly on mobile web browsers (iPad works ok). We have played around with the idea of more robust mobile support, but this is unlikely to happen soon and would likely require significant work. We'll write up a proposal RFC as a Github issue if this stance changes.
No, you can consume Blueprint with plain old JavaScript. Of course, you'll get a better development experience if you do use TypeScript—autocompletion, in-editor props validation & docs, the works!
We decided to ship Blueprint with a traditional global CSS stylesheet for a few reasons:
- Tooling for inline styles is still pretty nascent, while Sass and Stylelint are wonderful tools we love using.
- Regular CSS is easier to for consumers override and theme—this is especially important when authoring a library instead of an application. We have some use cases where we want to allow consumers to do this after build time, which is nearly impossible to do with inline styles that are applied in an application's JS bundle.
Additional notes:
- This approach doesn't prevent you from using inline styles for your own application built on top of Blueprint.
- We've generally been able to circumvent CSS collision issues with proper namespacing.
- That said, we are considering something like CSS Modules for future major versions of Blueprint.