Alternatives to Tailwind CSS logo

Alternatives to Tailwind CSS

Bootstrap, tachyons, Bulma, Material-UI, and Sass are the most popular alternatives and competitors to Tailwind CSS.
3.4K
2.8K
+ 1
244

What is Tailwind CSS and what are its top alternatives?

Tailwind CSS is a utility-first CSS framework that allows developers to rapidly build custom user interfaces. Its key features include a large set of pre-built utility classes for styling, a responsive design system, and the ability to customize styles using configuration files. However, its verbose class names can make the HTML markup cluttered, and some developers may find the learning curve steep.

  1. Bootstrap: Bootstrap is a popular front-end framework that provides a wide range of pre-designed components and utility classes for building responsive websites. Its key features include a grid system, reusable components, and extensive documentation. Pros: Rich set of components, active community support. Cons: Less customization compared to Tailwind CSS.
  2. Bulma: Bulma is a modern CSS framework based on flexbox that offers a clean and minimalistic design. Its key features include a responsive grid system, customizable variables, and lightweight file size. Pros: Easy to learn and use, well-documented. Cons: Limited number of components.
  3. Materialize: Materialize is a CSS framework based on Google's Material Design guidelines, providing a sleek and modern look for websites. Its key features include responsive components, Sass integration, and JavaScript plugins. Pros: Material Design aesthetics, comprehensive documentation. Cons: Less flexibility in customization.
  4. Foundation: Foundation is a responsive front-end framework that offers a customizable grid system, flexible styling options, and a library of components. Its key features include semantic markup, Sass support, and accessibility features. Pros: Highly customizable, robust framework. Cons: Steeper learning curve compared to Tailwind CSS.
  5. Semantic UI: Semantic UI is a development framework that uses human-friendly HTML to create responsive designs with ease. Its key features include a modular structure, theming support, and a large ecosystem of plugins. Pros: Intuitive syntax, theming capabilities. Cons: Limited grid system compared to Tailwind CSS.
  6. Foundation for Apps: Foundation for Apps is a front-end framework specifically designed for building web applications with AngularJS. Its key features include AngularJS integration, a responsive grid system, and a focus on performance. Pros: Optimized for web apps, support for AngularJS. Cons: Limited compared to Tailwind CSS for general website development.
  7. Spectre.css: Spectre.css is a lightweight and modern CSS framework that offers a minimalistic design approach for fast and responsive websites. Its key features include a responsive grid system, CSS variables support, and a focus on performance. Pros: Lightweight file size, flexible customization. Cons: Smaller community compared to Tailwind CSS.
  8. Tailwind Components: Tailwind Components is a collection of ready-to-use components built with Tailwind CSS, allowing developers to quickly integrate common design elements into their projects. Its key features include a variety of components, responsive design, and easy customization. Pros: Easy integration with Tailwind CSS, time-saving for developers. Cons: Limited compared to full-fledged CSS frameworks.
  9. UIKit: UIkit is a lightweight and modular front-end framework that offers a rich set of components and utilities for building modern websites. Its key features include a modular architecture, flexible layout options, and customizable themes. Pros: Modular components, extensive documentation. Cons: Smaller community support compared to Tailwind CSS.
  10. Chakra UI: Chakra UI is a simple and modular component library for building accessible and responsive web applications with ease. Its key features include a set of customizable components, theme-based styling, and extensive documentation. Pros: Accessible design system, theming capabilities. Cons: Less mature compared to Tailwind CSS.

Top Alternatives to Tailwind CSS

  • Bootstrap
    Bootstrap

    Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...

  • tachyons
    tachyons

    Create fast loading, highly readable, and 100% responsive interfaces with as little CSS as possible. ...

  • Bulma
    Bulma

    Bulma is a CSS framework based on Flexbox and built with Sass

  • Material-UI
    Material-UI

    Material UI is a library of React UI components that implements Google's Material Design. ...

  • Sass
    Sass

    Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin. ...

  • Vuetify
    Vuetify

    Vuetify is a component framework for Vue.js 2. It aims to provide clean, semantic and reusable components that make building your application a breeze. Vuetify utilizes Google's Material Design design pattern, taking cues from other popular frameworks such as Materialize.css, Material Design Lite, Semantic UI and Bootstrap 4. ...

  • styled-components
    styled-components

    Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅 ...

  • BEM
    BEM

    This methodology was developed at Yandex with the goals in mind that Fast development and long-lasting results for standard projects,A project involves many people,Scalable teams,Code reuse. ...

Tailwind CSS alternatives & related posts

Bootstrap logo

Bootstrap

55.3K
13.1K
7.7K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
55.3K
13.1K
+ 1
7.7K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 943
    Consistent
  • 779
    Great docs
  • 677
    Flexible
  • 472
    HTML, CSS, and JS framework
  • 411
    Open source
  • 375
    Widely used
  • 368
    Customizable
  • 242
    HTML framework
  • 77
    Mobile first
  • 77
    Popular
  • 77
    Easy setup
  • 57
    Great grid system
  • 52
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 28
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 14
    Grids
  • 9
    Good for a person who hates CSS
  • 8
    Clean
  • 4
    Easy to setup and learn
  • 4
    Rapid development
  • 4
    Love it
  • 3
    Great and easy to use
  • 2
    Easy to use
  • 2
    Devin schumacher rules
  • 2
    Boostrap
  • 2
    Community
  • 2
    Provide angular wrapper
  • 2
    Great and easy
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Clean and quick frontend development
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 1
    Painless front end development
  • 1
    Love the classes?
  • 1
    Responsive design
  • 1
    Poop
  • 1
    So clean and simple
  • 1
    Design Agnostic
  • 1
    Numerous components
  • 1
    Material-ui
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Vue
  • 1
    Felxible, comfortable, user-friendly
  • 1
    Pre-Defined components
  • 1
    It's fast
  • 1
    Geo
  • 1
    Not tied to jQuery
  • 1
    The fame
  • 1
    Easy setup2
CONS OF BOOTSTRAP
  • 26
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 15
    Grid system break points aren't ideal
  • 14
    Too much heavy decoration in default look
  • 8
    Verbose styles
  • 1
    Super heavy

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Technical Lead · | 19 upvotes · 4.7M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Francisco Quintero
Tech Lead at Dev As Pros · | 13 upvotes · 1.6M views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
tachyons logo

tachyons

66
78
0
Quickly build and design new UI without writing css
66
78
+ 1
0
PROS OF TACHYONS
    Be the first to leave a pro
    CONS OF TACHYONS
      Be the first to leave a con

      related tachyons posts

      Bulma logo

      Bulma

      750
      855
      38
      Free, open source, & modern CSS framework based on Flexbox
      750
      855
      + 1
      38
      PROS OF BULMA
      • 12
        Easy setup
      • 6
        Easy-to-customize the sass build
      • 6
        Community-created themes
      • 5
        Responsive
      • 5
        Great docs
      • 4
        Easy to learn and use
      CONS OF BULMA
      • 2
        Not yet supporting Vue 3

      related Bulma posts

      CDG

      I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

      Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

      As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

      To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

      CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

      Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

      See more
      Daniel Hernández Alcojor
      Frontend Developer at atSistemas · | 8 upvotes · 1M views

      I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.

      But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.

      What do you think we should use? Maybe you have another suggestion?

      See more
      Material-UI logo

      Material-UI

      2.2K
      3.6K
      441
      Material UI is a library of React UI components that implements Google's Material Design.
      2.2K
      3.6K
      + 1
      441
      PROS OF MATERIAL-UI
      • 141
        React
      • 82
        Material Design
      • 60
        Ui components
      • 30
        CSS framework
      • 25
        Component
      • 14
        Looks great
      • 12
        Responsive
      • 12
        Good documentation
      • 9
        LESS
      • 8
        Ui component
      • 7
        Open source
      • 6
        Code examples
      • 6
        Flexible
      • 5
        JSS
      • 3
        Angular
      • 3
        Very accessible
      • 3
        Fun
      • 3
        Supports old browsers out of the box
      • 2
        Typescript support
      • 2
        # of components
      • 2
        Interface
      • 2
        Designed for Server Side Rendering
      • 1
        Support for multiple styling systems
      • 1
        Css
      • 1
        Easy to work with
      • 1
        Accessibility
      CONS OF MATERIAL-UI
      • 35
        Hard to learn. Bad documentation
      • 28
        Hard to customize
      • 21
        Hard to understand Docs
      • 8
        Bad performance
      • 7
        Extra library needed for date/time pickers
      • 7
        For editable table component need to use material-table
      • 2
        Typescript Support
      • 1
        # of components

      related Material-UI posts

      Adebayo Akinlaja
      Engineering Manager at Andela · | 30 upvotes · 3.3M views

      I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

      A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

      In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

      If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

      See more

      I just finished tweaking styles details of my hobby project MovieGeeks (https://moviegeeks.co/): The minimalist Online Movie Catalog

      This time I want to share my thoughts on the Tech-Stack I decided to use on the Frontend: React, React Router, Material-UI and React-Apollo:

      1. React is by far the Front-End "framework" with the biggest community. Some of the newest features like Suspense and Hooks makes it even more awesome and gives you even more power to write clean UI's

      2. Material UI is a very solid and stable set of react components that not only look good, but also are easy to use and customize. This was my first time using this library and I am very happy with the result

      3. React-Apollo in my opinion is the best GraphQL client for a React application. Easy to use and understand and it gives you awesome features out of the box like cache. With libraries like react-apollo-hooks you can even use it with the hooks api which makes the code cleaner and easier to follow.

      Any feedback is much appreciated :)

      See more
      Sass logo

      Sass

      41.9K
      31.3K
      3K
      Syntactically Awesome Style Sheets
      41.9K
      31.3K
      + 1
      3K
      PROS OF SASS
      • 613
        Variables
      • 594
        Mixins
      • 466
        Nested rules
      • 410
        Maintainable
      • 300
        Functions
      • 149
        Modular flexible code
      • 143
        Open source
      • 112
        Selector inheritance
      • 107
        Dynamic
      • 96
        Better than cs
      • 5
        Used by Bootstrap
      • 3
        If and for function
      • 2
        Better than less
      • 1
        Inheritance (@extend)
      • 1
        Custom functions
      CONS OF SASS
      • 6
        Needs to be compiled

      related Sass posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 4.8M views

      Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

      • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
      • Vue Styleguidist as our style guide and pool of developed Vue.js components
      • Vuetify as Material Component Framework (for fast app development)
      • TypeScript as programming language
      • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
      • ESLint, TSLint and Prettier for coding style and code analyzes
      • Jest as testing framework
      • Google Fonts and Font Awesome for typography and icon toolkit
      • NativeScript-Vue for mobile development

      The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

      • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
      • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
      • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
      • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
      • Large scaling. Vue.js can help to develop pretty large reusable templates.
      • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
      See more
      Ali Soueidan
      Creative Web Developer at Ali Soueidan · | 18 upvotes · 1.2M views

      Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

      For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

      To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

      DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

      Side note: I used npm for package management. 🎉

      *Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

      See more
      Vuetify logo

      Vuetify

      1.2K
      1.8K
      170
      Material Component Framework for VueJS 2
      1.2K
      1.8K
      + 1
      170
      PROS OF VUETIFY
      • 29
        Enables beauty for graphically challenged devs
      • 24
        Wide range of components and active development
      • 22
        Vue
      • 18
        New age components
      • 13
        Easy integration
      • 11
        Material Design
      • 10
        Nuxt.js
      • 10
        Open Source
      • 6
        Awesome Documentation
      • 5
        Awesome Component collection
      • 5
        Internationalization
      • 5
        Not tied to jQuery
      • 4
        Best use of vue slots you'll ever see
      • 2
        Not tied to jQuery
      • 2
        Treeshaking
      • 2
        Active Community
      • 2
        Responsiveness
      CONS OF VUETIFY
      • 19
        It is heavy
      • 3
        Not Vue 3 Ready (Alpha-Version)

      related Vuetify posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 4.8M views

      Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

      • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
      • Vue Styleguidist as our style guide and pool of developed Vue.js components
      • Vuetify as Material Component Framework (for fast app development)
      • TypeScript as programming language
      • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
      • ESLint, TSLint and Prettier for coding style and code analyzes
      • Jest as testing framework
      • Google Fonts and Font Awesome for typography and icon toolkit
      • NativeScript-Vue for mobile development

      The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

      • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
      • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
      • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
      • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
      • Large scaling. Vue.js can help to develop pretty large reusable templates.
      • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
      See more
      Jeyabalaji Subramanian

      At FundsCorner, when we set out to pick up the front-end tech stack (around Dec 2017), we drove our decision based on the following considerations:

      (1) We were clear that we will NOT have a hybrid app. We will start with Responsive Web & once there is traction, we will rollout our Android App. However, we wanted to ensure that the users have a consistent experience on both the Web & the App. So, the front-end framework must also have a material design component library which we can choose from.

      (2) Before joining FundsCorner as a CTO, I had already worked with Angular. I enjoyed working with Angular, but I felt that I must choose something that will provide us with the fastest time from Concept to Reality.

      (3) I am strong proponent of segregating HTML & JavaScript. I.e. I was not for writing or generating HTML through JavaScript. Because, this will mean that the Front-end developers I have to hire will always be very strong on JavaScript alongside HTML5 & CSS. I was looking for a Framework that was on JavaScript but not HEAVY on JavaScript.

      (3) The first iteration of the web app was to be done by myself. But I was clear that when someone takes up the mantle, they will be able to come up the curve fast.

      In the end, Vue.js and Vuetify satisfied all the above criteria with aplomb! When I did our first POC on Vue.js I could not believe that front-end development could be this fast. The documentation was par excellence and all the required essentials that come along with the Framework (viz. Routing, Store, Validations) etc. were available from the same community! It was also a breeze to integrate with other JavaScript libraries (such as Amazon Cognito).

      By picking Vuetify, we were able to provide a consistent UI experience between our Web App and Native App, besides making the UI development ultra blazing fast!

      In the end, we were able to rollout our Web App in record 6 weeks (that included the end to end Loan Origination flow, Loans management system & Customer engagement module). www.jeyabalaji.com

      See more
      styled-components logo

      styled-components

      1.8K
      602
      12
      Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps...
      1.8K
      602
      + 1
      12
      PROS OF STYLED-COMPONENTS
      • 11
        Very easy to use and integrate
      • 1
        Huihui
      CONS OF STYLED-COMPONENTS
        Be the first to leave a con

        related styled-components posts

        Johnny Bell

        I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

        I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

        I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

        Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

        Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

        With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

        If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

        See more
        Vishal Narkhede
        Javascript Developer at getStream.io · | 19 upvotes · 439K views

        Recently, the team at Stream published a React Native SDK for our new Chat by Stream product. React Native brings the power of JavaScript to the world of mobile development, making it easy to develop apps for multiple platforms. We decided to publish two different endpoints for the SDK – Expo and React Native (non-expo), to avoid the hurdle and setup of using the Expo library in React Native only projects on the consumer side.

        The capability of style customization is one a large deal breaker for frontend SDKs. To solve this, we decided to use styled-components in our SDK, which makes it easy to add support for themes on top of our existing components. This practice reduces the maintenance effort for stylings of custom components and keeps the overall codebase clean.

        For module bundling, we decided to go with Rollup.js instead of Webpack due to its simplicity and performance in the area of library/module providers. We are using Babel for transpiling code, enabling our team to use JavaScript's next-generation features. Additionally, we are using the React Styleguidist component documentation, which makes documenting the React Native code a breeze.

        See more
        BEM logo

        BEM

        121
        95
        0
        It is a methodology, that helps you to achieve reusable components and code sharing in the front-end
        121
        95
        + 1
        0
        PROS OF BEM
          Be the first to leave a pro
          CONS OF BEM
            Be the first to leave a con

            related BEM posts