Alternatives to Foundation logo

Alternatives to Foundation

Bootstrap, Primer, Animate.css , Material Design for Angular, and Material-UI are the most popular alternatives and competitors to Foundation.
1.2K
1.1K
+ 1
738

What is Foundation and what are its top alternatives?

Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices.
Foundation is a tool in the Front-End Frameworks category of a tech stack.
Foundation is an open source tool with GitHub stars and GitHub forks. Here’s a link to Foundation's open source repository on GitHub

Top Alternatives to Foundation

  • Bootstrap
    Bootstrap

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

  • Primer
    Primer

    Primer is the basecoat of GitHub, made by nerds just like you who share a passion for HTML and CSS. ...

  • Animate.css
    Animate.css

    It is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness. ...

  • Material Design for Angular
    Material Design for Angular

    Material Design is a specification for a unified system of visual, motion, and interaction design that adapts across different devices. Our goal is to deliver a lean, lightweight set of AngularJS-native UI elements that implement the material design system for use in Angular SPAs. ...

  • Material-UI
    Material-UI

    MUI (formerly Material-UI) is the React UI library you always wanted. Follow your own design system, or start with Material Design. ...

  • Tailwind CSS
    Tailwind CSS

    Tailwind is different from frameworks like Bootstrap, Foundation, or Bulma in that it's not a UI kit. It doesn't have a default theme, and there are no build-in UI components. It comes with a menu of predesigned widgets to build your site with, but doesn't impose design decisions that are difficult to undo. ...

  • Nuxt.js
    Nuxt.js

    Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more. ...

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

Foundation alternatives & related posts

Bootstrap logo

Bootstrap

53.7K
12.3K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
53.7K
12.3K
+ 1
7.6K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 943
    Consistent
  • 779
    Great docs
  • 678
    Flexible
  • 467
    HTML, CSS, and JS framework
  • 410
    Open source
  • 374
    Widely used
  • 367
    Customizable
  • 242
    HTML framework
  • 77
    Easy setup
  • 77
    Mobile first
  • 77
    Popular
  • 58
    Great grid system
  • 51
    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
  • 8
    Clean
  • 7
    Good for a person who hates CSS
  • 4
    Easy to setup and learn
  • 4
    Rapid development
  • 4
    Love it
  • 3
    Great and easy to use
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Easy to use
  • 2
    Provide angular wrapper
  • 2
    Community
  • 2
    Clean and quick frontend development
  • 2
    Great and easy
  • 2
    Sprzedam opla
  • 2
    Great and easy to make a responsive website
  • 1
    Love the classes?
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 1
    Painless front end development
  • 1
    So clean and simple
  • 1
    Reactjs
  • 1
    It's fast
  • 1
    Geo
  • 1
    Boostrap
  • 1
    Pre-Defined components
  • 1
    Not tied to jQuery
  • 1
    Numerous components
  • 1
    Responsive design
  • 1
    Material-ui
  • 1
    Design Agnostic
  • 1
    Recognizable
  • 1
    Intuitive
  • 0
    Frefsd
CONS OF BOOTSTRAP
  • 25
    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 · 2.8M 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 · 881.6K 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
Primer logo

Primer

11
46
6
CSS toolkit and guidelines that power GitHub
11
46
+ 1
6
PROS OF PRIMER
  • 4
    simple
  • 2
    Pretty
  • 0
    Maintained by GitHub
CONS OF PRIMER
    Be the first to leave a con

    related Primer posts

    Animate.css  logo

    Animate.css

    9.7K
    1.8K
    0
    A library of CSS animations
    9.7K
    1.8K
    + 1
    0
    PROS OF ANIMATE.CSS
      Be the first to leave a pro
      CONS OF ANIMATE.CSS
        Be the first to leave a con

        related Animate.css posts

        Material Design for Angular logo

        Material Design for Angular

        9.2K
        7.4K
        518
        Material Design for AngularJS Apps
        9.2K
        7.4K
        + 1
        518
        PROS OF MATERIAL DESIGN FOR ANGULAR
        • 119
          Ui components
        • 62
          Backed by google
        • 51
          Free
        • 50
          Backed by angular
        • 47
          Javascript
        • 34
          Open source
        • 32
          Responsiveness
        • 31
          Easy to learn
        • 28
          Quick to develop
        • 20
          Customizable
        • 8
          Easy to start
        • 8
          Powerful
        • 6
          Themes
        • 6
          Flexible
        • 4
          Flexbox Layouts
        • 3
          Great community
        • 3
          I like its design
        • 2
          Great extensions
        • 1
          CDK
        • 1
          Consistents
        • 1
          It's the best looking out of the box
        • 1
          Seamless integration with AngularJS but lack of docs
        • 0
          Progressive Web Apps - to learn
        CONS OF MATERIAL DESIGN FOR ANGULAR
        • 4
          No practical examples

        related Material Design for Angular posts

        Material-UI logo

        Material-UI

        1.8K
        3.1K
        389
        The React UI library you always wanted.
        1.8K
        3.1K
        + 1
        389
        PROS OF MATERIAL-UI
        • 122
          React
        • 77
          Material Design
        • 53
          Ui components
        • 26
          CSS framework
        • 21
          Component
        • 12
          Looks great
        • 10
          Responsive
        • 10
          Good documentation
        • 9
          LESS
        • 7
          Open source
        • 6
          Code examples
        • 5
          Flexible
        • 5
          Ui component
        • 4
          JSS
        • 3
          Supports old browsers out of the box
        • 3
          Angular
        • 3
          Fun
        • 3
          Very accessible
        • 2
          Designed for Server Side Rendering
        • 2
          LADO
        • 2
          Barev Arman
        • 2
          Interface
        • 1
          Easy to work with
        • 1
          Asdasd
        • 0
          555
        • 0
          User
        CONS OF MATERIAL-UI
        • 29
          Hard to learn. Bad documentation
        • 23
          Hard to customize
        • 19
          Hard to understand Docs
        • 6
          Extra library needed for date/time pickers
        • 6
          Bad performance
        • 5
          Long Code
        • 5
          For editable table component need to use material-table

        related Material-UI posts

        Adebayo Akinlaja
        Engineering Manager at Andela · | 27 upvotes · 1.1M 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

        My React website is a simple 5-pager that attaches to a database to store and display registrations and other data. The user (small user base) can change any form elements, but I don't need theme-ing, though that would be fun for the user. reactstrap/react-bootstrap built on Bootstrap 4 sounds dated. I am familiar with reactstrap, but a friend said to try Material-UI. The thought of learning it is interesting, but somehow I think it might be overkill. So... reactstrap, react-bootstrap, or Material UI, which should I use?

        See more
        Tailwind CSS logo

        Tailwind CSS

        1.5K
        1.9K
        222
        A utility-first CSS framework for rapid UI development
        1.5K
        1.9K
        + 1
        222
        PROS OF TAILWIND CSS
        • 36
          Highly customizable
        • 28
          Quick setup
        • 28
          Utility first styles, its amazing
        • 21
          Versatile
        • 21
          Great docs
        • 16
          Fast
        • 16
          Customizable
        • 15
          Consistent
        • 11
          Open source
        • 11
          Semantic
        • 11
          Very light
        • 8
          Responsive
        CONS OF TAILWIND CSS
        • 14
          Priced
        • 4
          Cluttered html structure

        related Tailwind CSS posts

        James Bender
        Lead Application Architect at TekPartners · | 9 upvotes · 17.1K views
        Shared insights
        on
        Tailwind CSSTailwind CSSBootstrapBootstrap

        Bootstrap is a great idea until your designer wants something that doesn't fit neatly into a 12 column paradigm. Then things start to get difficult. We've had to add customizations and tweaks to Bootstrap-ed HTML that by the time we were done, we would have been better off just going straight CSS. Bootstrap helps with responsiveness, but again, it's an "80/20" solution at best. And that 20 percent can be a nightmare. Plus, most clients have this odd belief that you just drop Bootstrap into an app, and abracadabra, your site is totally responsive over every type of screen and form factor in existence. This is not the case. We have had MUCH better and faster results with Tailwind CSS. Our designers are happy we're not trying to force them into a Bootstrap-friendly design, and even with responsive sites, development has been easier and faster.

        See more
        Giordanna De Gregoriis
        Jr Fullstack Developer at Stefanini Inspiring · | 8 upvotes · 158.3K views

        TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

        Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.

        We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.

        • The cold start takes too much time
        • Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
        • Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)

        I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.

        I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.

        What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

        See more
        Nuxt.js logo

        Nuxt.js

        1.5K
        1.3K
        292
        The Vue.js Framework
        1.5K
        1.3K
        + 1
        292
        PROS OF NUXT.JS
        • 45
          SSR
        • 41
          Automatic routes
        • 27
          Middleware
        • 22
          Hot code reloading
        • 19
          Easy setup, easy to use, great community, FRENCH TOUCH
        • 17
          Static Websites
        • 17
          SPA
        • 16
          Plugins
        • 14
          Code splitting for every page
        • 14
          Custom layouts
        • 11
          Automatic transpilation and bundling (with webpack and
        • 10
          Modules ecosystem
        • 9
          Easy setup
        • 8
          Amazing Developer Experience
        • 7
          Vibrant and helpful community
        • 7
          Pages directory
        • 6
          Not React
        • 2
          Its Great for Team Development
        CONS OF NUXT.JS
        • 4
          Still vue 2
        • 2
          Not React
        • 1
          Not Next

        related Nuxt.js posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.1M 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
        Giordanna De Gregoriis
        Jr Fullstack Developer at Stefanini Inspiring · | 8 upvotes · 158.3K views

        TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

        Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.

        We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.

        • The cold start takes too much time
        • Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
        • Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)

        I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.

        I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.

        What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

        See more
        Vuetify logo

        Vuetify

        1K
        1.6K
        149
        Material Component Framework for VueJS 2
        1K
        1.6K
        + 1
        149
        PROS OF VUETIFY
        • 27
          Enables beauty for graphically challenged devs
        • 22
          Wide range of components and active development
        • 21
          Vue
        • 15
          New age components
        • 12
          Easy integration
        • 10
          Material Design
        • 9
          Open Source
        • 8
          Nuxt.js
        • 5
          Not tied to jQuery
        • 5
          Awesome Documentation
        • 4
          Internationalization
        • 4
          Awesome Component collection
        • 3
          Best use of vue slots you'll ever see
        • 2
          Not tied to jQuery
        • 1
          Responsiveness
        • 1
          Treeshaking
        CONS OF VUETIFY
        • 19
          It is heavy
        • 3
          Not Vue 3 Ready (Alpha-Version)
        • 0
          D

        related Vuetify posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.1M 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 · 799K 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