Why I stopped using CSS Frameworks, Should you too?

Opinionated CSS Frameworks

Buttons in Bootstrap
Buttons in MaterialUI
The appearance of Input Box in Bootstrap
Similar default Appearance of Input Box in MaterialUI

Utility First CSS Frameworks

Custom CSS

Okay, I know these already, but what’s wrong with using Frameworks?

So Should I start writing CSS from scratch and ignore every CSS library that can help me?

  1. One Timer / Small Project: Projects without specific design requirements, or where designs are in agreement with Framework’s ideology or projects with short delivery timelines; I would recommend using opinionated Framework as it will accelerate development and will let you focus on business logic more than CSS management. However, it might add up to bundle size.
  2. Mid-level projects: Projects that are going to be in “Development and Release Loop” for a while i.e, there will be iterative changes, and the feedback from customers or end-users might affect the look & feel of the product in the upcoming iteration. I would suggest, it would be sensible to use utility first CSS libraries. These will accelerate your development and still keep the scope of the design schema extension intact. You can anytime sprinkle some custom-made CSS. Using Utility First CSS Libraries will even help you maintain guidelines for CSS as all collaborators/developers need not create CSS classes which will help to avoid CSS duplication or collision
  3. Big Projects/Long-term Projects: These are the projects where such a decision becomes crucial. Most of the projects that I deal with falls under this category. And I have seen many projects where these dependencies have slowed down the entire development process. If UI Designs and Schemas are by those of opinionated frameworks, and no major deviation is guaranteed then it’s safe to go ahead with the CSS framework approach. However, If designers are providing designs that are either not suitable for opinionated frameworks, or for projects where standardization can not be guaranteed from Product or Designer Teams. It’s safest to go ahead with the custom CSS approach. It will be comparatively hard to start such a project and the first observable milestone might take time to be achieved, but in long run, it will pay you off, as you won’t be bound by any framework limitation. But remember this freedom comes at the cost of extra efforts in maintaining the codebase and strictly following some standards that can avoid duplication of codes.

Wrapping Up

--

--

--

Leading Growth Projects in EdTech Startup

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Getting started with OpenFaaS on Minikube

Handling Custom Error Pages(404, 500) In Django

“Real” Big Data: PySpark to SQL to Pandas using only 9 simple methods()

Integer to Roman — Day 93(Python)

#Birdchain Project

Three Branching Paths

How To Update Your Hackintosh to macOS to Catalina

Chicka Chicka Boom Boom Game Inspired Arduino Build

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Aditya Dixit

Aditya Dixit

Leading Growth Projects in EdTech Startup

More from Medium

5 Reasons To Try CSS Grid On Your Next UI Development

Front-End: Enhancing Styling With CSS

Building Design Systems: How to Treat CSS Styles

How I Built a Smooth Horizontal Scrolling List with Only a Few Lines of CSS