Alternatives to Buefy logo

Alternatives to Buefy

Vuetify, Bulma, ElementUI, Bootstrap Vue, and Bootstrap are the most popular alternatives and competitors to Buefy.
81
132
+ 1
9

What is Buefy and what are its top alternatives?

We like to think that Buefy is the javascript layer for your Bulma interface, since it doesn't require for it to be a sophisticated Single-Page Application. You can import it completely or single components on a ordinary webpage and use Vue.js as a replacement for jQuery.
Buefy is a tool in the JavaScript Framework Components category of a tech stack.
Buefy is an open source tool with 8.7K GitHub stars and 1K GitHub forks. Here’s a link to Buefy's open source repository on GitHub

Top Alternatives to Buefy

  • 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. ...

  • Bulma

    Bulma

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

  • ElementUI

    ElementUI

    It is not focused on Mobile development, mainly because it lacks responsiveness on mobile WebViews. ...

  • Bootstrap Vue

    Bootstrap Vue

    Build responsive, mobile-first projects on the web using Vue.js and the world's most popular front-end CSS library — Bootstrap V4. ...

  • Bootstrap

    Bootstrap

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

  • Element

    Element

    Element is a Vue 2.0 based component library for developers, designers and product managers, with a set of design resources. ...

  • React Router

    React Router

    React Router is a complete routing solution designed specifically for React.js. It painlessly synchronizes the components of your application with the URL, with first-class support for nesting, transitions, and server side rendering. ...

  • styled-components

    styled-components

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

Buefy alternatives & related posts

Vuetify logo

Vuetify

862
1.4K
143
Material Component Framework for VueJS 2
862
1.4K
+ 1
143
PROS OF VUETIFY
  • 26
    Enables beauty for graphically challenged devs
  • 23
    Wide range of components and active development
  • 19
    Vue
  • 14
    New age components
  • 11
    Easy integration
  • 10
    Material Design
  • 9
    Open Source
  • 8
    Nuxt.js
  • 5
    Not tied to jQuery
  • 4
    Awesome Component collection
  • 4
    Awesome Documentation
  • 4
    Internationalization
  • 2
    Best use of vue slots you'll ever see
  • 2
    Not tied to jQuery
  • 1
    Responsiveness
  • 1
    Treeshaking
CONS OF VUETIFY
  • 18
    It is heavy

related Vuetify posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 19 upvotes · 620.3K 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
Paul Whittemore
Developer and Owner at Appurist Software · | 15 upvotes · 681.9K views

I'm building most projects using: Server: either Fastify (all projects going forward) or ExpressJS on Node.js (existing, previously) on the server side, and Client app: either Vuetify (currently) or Quasar Framework (going forward) on Vue.js with vuex on Electron for the UI to deliver both web-based and desktop applications for multiple platforms.

The direct support for Android and iOS in Quasar Framework will make it my go-to client UI platform for any new client-side or web work. On the server, I'll probably use Fastly for all my server work, unless I get into Go more in the future.

Update: The mobile support in Quasar is not a sufficiently compelling reason to move me from Vuetify. I have decided to stick with Vuetify for a UI for Vue, as it is richer in components and enables a really great-looking professional result. For mobile platforms, I will just use Cordova to wrap the Vue+Vuetify app for mobile, and Electron to wrap it for desktop platforms.

See more
Bulma logo

Bulma

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

related Bulma posts

Daniel Hernández Alcojor
Frontend Developer at atSistemas · | 8 upvotes · 345.4K 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
ElementUI logo

ElementUI

43
88
3
A Desktop UI toolkit for Vue.js
43
88
+ 1
3
PROS OF ELEMENTUI
  • 3
    Avaliable for other frontend frameworks too
  • 0
    Wqas
CONS OF ELEMENTUI
    Be the first to leave a con

    related ElementUI posts

    Sarmad Chaudhary
    Founder & CEO at Ebiz Ltd. · | 9 upvotes · 382.5K views

    Hi there!

    I just want to have a simple poll/vote...

    If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

    1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

    2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

    Your advice would help a lot! Thanks in advance :)

    See more
    Bootstrap Vue logo

    Bootstrap Vue

    147
    381
    37
    A front end CSS And Vue component library
    147
    381
    + 1
    37
    PROS OF BOOTSTRAP VUE
    • 7
      Vue
    • 6
      Open Source
    • 4
      Maintained
    • 3
      Easily themable
    • 3
      Bootstrap v4.x
    • 3
      Nuxt.js Integration
    • 3
      Customizable via SASS variables
    • 3
      Not tied to jQuery
    • 3
      ARIA Accessibility out of the box
    • 2
      Active development
    CONS OF BOOTSTRAP VUE
      Be the first to leave a con

      related Bootstrap Vue posts

      I'm migrating from pure Laravel with Bootstrap project to a kind of Laravel + Vue.js. Which one should I use for the UI?

      We are considering bootstrap version 4. Still, which of these 3 should I choose? Pure bootstrap, Vuetify, or Bootstrap Vue?

      See more
      Bootstrap logo

      Bootstrap

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

      related Bootstrap posts

      Ganesa Vijayakumar
      Full Stack Coder | Module Lead · | 18 upvotes · 2.3M 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 · 720.8K 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
      Element logo

      Element

      60
      82
      3
      A Vue 2.0-based desktop UI library for developers, designers and PMs
      60
      82
      + 1
      3
      PROS OF ELEMENT
      • 3
        Very complete solution
      CONS OF ELEMENT
      • 1
        Buggy in parts

      related Element posts

      React Router logo

      React Router

      1.4K
      952
      12
      A complete routing solution for React.js
      1.4K
      952
      + 1
      12
      PROS OF REACT ROUTER
      • 12
        Because there's not alternative
      CONS OF REACT ROUTER
        Be the first to leave a con

        related React Router posts

        ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

        ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

        React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

        styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

        React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

        Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

        See more

        I'm creating a website with React in my free time, and this is my first time doing this. So far, I've worked with React and React Router, but migrating to Next.js or Gatsby would cover Routing and SEO, which I currently cannot work with. Most things I read say that Next.js is the best solution, but I am trying to decide whether it is worth the time and effort to recreate the site for SEO and speed purposes. Does anyone have suggestions?

        See more
        styled-components logo

        styled-components

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

          related styled-components posts

          Johnny Bell
          Software Engineer at Weedmaps · | 14 upvotes · 477.7K views

          For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.

          Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.

          We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.

          Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.

          The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.

          If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.

          #StackDecisionsLaunch

          See more

          ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

          ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

          React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

          styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

          React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

          Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

          See more