Alternatives to Font Awesome logo

Alternatives to Font Awesome

Google Fonts, Bootstrap, Ionicons, Material Design, and InVision are the most popular alternatives and competitors to Font Awesome.
57.5K
21

What is Font Awesome and what are its top alternatives?

You can get vector icons and social logos on your website with it. It is a font that's made up of symbols, icons, or pictograms that you can use in a webpage, just like a font.
Font Awesome is a tool in the Fonts category of a tech stack.
Font Awesome is an open source tool with 73.7K GitHub stars and 12.2K GitHub forks. Here’s a link to Font Awesome's open source repository on GitHub

Top Alternatives to Font Awesome

  • Google Fonts
    Google Fonts

    A library of 915 free licensed fonts, an interactive web directory for browsing the library, and APIs for conveniently using the fonts via CSS and Android. ...

  • Bootstrap
    Bootstrap

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

  • Ionicons
    Ionicons

    Premium designed icons for use in web, iOS, Android, and desktop apps. Support for SVG and web font. Completely open source and MIT licensed. ...

  • Material Design
    Material Design

    Material Design is a unified system that combines theory, resources, and tools for crafting digital experiences. ...

  • InVision
    InVision

    InVision lets you create stunningly realistic interactive wireframes and prototypes without compromising your creative vision. ...

  • Typekit
    Typekit

    It is an online service which offers a subscription library of high-quality fonts. The fonts may be used directly on websites or synced via Adobe Creative Cloud to applications on the subscriber's computers. ...

  • Figma
    Figma

    Figma is the first interface design tool with real-time collaboration. It keeps everyone on the same page. Focus on the work instead of fighting your tools. ...

  • Adobe Photoshop
    Adobe Photoshop

    It is the best in the world of graphic design and image processing software that will realize any of your ideas. Create and enhance photos, illustrations and 3D graphic objects. ...

Font Awesome alternatives & related posts

Google Fonts logo

Google Fonts

77.5K
13.4K
13
Making the web more beautiful, fast, and open through great typography
77.5K
13.4K
+ 1
13
PROS OF GOOGLE FONTS
  • 8
    Restrict character set
  • 5
    Free
CONS OF GOOGLE FONTS
    Be the first to leave a con

    related Google Fonts posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 24 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
    Bootstrap logo

    Bootstrap

    55.5K
    13.1K
    7.7K
    Simple and flexible HTML, CSS, and JS for popular UI components and interactions
    55.5K
    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
      Easy setup
    • 77
      Popular
    • 77
      Mobile first
    • 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
      Love it
    • 4
      Rapid development
    • 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 Architect · | 19 upvotes · 5.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 · 1.8M 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
    Ionicons logo

    Ionicons

    1.4K
    68
    5
    Beautifully crafted open source icons
    1.4K
    68
    + 1
    5
    PROS OF IONICONS
    • 2
      Ui Components
    • 2
      Icons
    • 1
      Looks Amazing
    CONS OF IONICONS
      Be the first to leave a con

      related Ionicons posts

      Material Design logo

      Material Design

      596
      886
      14
      Google's Material Design
      596
      886
      + 1
      14
      PROS OF MATERIAL DESIGN
      • 5
        They really set a new bar in design
      • 4
        An intuitive design
      • 3
        Simply, And Beautiful
      • 2
        Many great libraries
      • 0
        Composants
      CONS OF MATERIAL DESIGN
      • 2
        Sometimes, it can hang the browser

      related Material Design posts

      Giordanna De Gregoriis
      Jr Fullstack Developer at Stefanini Inspiring · | 8 upvotes · 481.2K 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
      Ashish Sharma
      Sr. UI Associate at Daffodil Software · | 5 upvotes · 718.8K views

      I am a bit confused when to choose Bootstrap vs Material Design or Tailwind CSS, and why? I mean, in which kind of projects we can work with bootstrap/Material/Tailwind CSS? If the design is made up on the grid, we prefer bootstrap, and if flat design, then material design. Similarly, when do we choose tailwind CSS?

      Any suggestion would be appreciated?

      See more
      InVision logo

      InVision

      8.4K
      5.8K
      617
      Prototyping & Collaboration For Design Teams
      8.4K
      5.8K
      + 1
      617
      PROS OF INVISION
      • 158
        Collaborative
      • 128
        Simple
      • 95
        Pretty
      • 79
        Quick
      • 45
        Works with lots of devices
      • 33
        Free
      • 29
        Cool for remote team prototyping
      • 17
        It revolutionized the way I share work with clients
      • 10
        Legendary customer support
      • 8
        Dropbox Integration
      • 3
        Easy
      • 3
        Collaboration
      • 2
        Rapid Prototyping
      • 2
        LiveShare
      • 1
        Annotation
      • 1
        They are always improving the product suite
      • 1
        Beautiful UI
      • 1
        Brings mockups to life
      • 1
        Allows for a comprehensive workflow
      CONS OF INVISION
        Be the first to leave a con

        related InVision posts

        Priit Kaasik
        CTO at Katana Cloud Inventory · | 8 upvotes · 575.4K views

        How we ended up choosing Confluence as our internal web / wiki / documentation platform at Katana.

        It happened because we chose Bitbucket over GitHub . We had Katana's first hackaton to assemble and test product engineering platform. It turned out that at that time you could have Bitbucket's private repositories and a team of five people for free - Done!

        This decision led us to using Bitbucket pipelines for CI, Jira for Kanban, and finally, Confluence. We also use Microsoft Office 365 and started with using OneNote, but SharePoint is still a nightmare product to use to collaborate, so OneNote had to go.

        Now, when thinking of the key value of Confluence to Katana then it is Product Requirements Management. We use Page Properties macros, integrations (with Slack , InVision, Sketch etc.) to manage Product Roadmap, flash out Epic and User Stories.

        We ended up with using Confluence because it is the best fit for our current engineering ecosystem.

        See more
        Nadia Matveyeva
        UI Designer at freelancer · | 5 upvotes · 155.5K views
        Shared insights
        on
        InVisionInVisionAdobe XDAdobe XD

        I am working on a project for a client, I need to provide them with ideas and prototypes. They all have Adobe XD, but not InVision - I am the only one who will have that if purchased. I am trying to decide what would be the best tool to hand off the work to a developer who in terms will be working in PySide (Qt related) or Tkinter. Is there any benefits to me or the developer to work in Adobe XD or InVision. I am just trying to use the best tool to get the job done between the two.

        Thank you in advance! Nadia

        See more
        Typekit logo

        Typekit

        4.2K
        127
        0
        An online service offering high-quality fonts
        4.2K
        127
        + 1
        0
        PROS OF TYPEKIT
          Be the first to leave a pro
          CONS OF TYPEKIT
            Be the first to leave a con

            related Typekit posts

            Figma logo

            Figma

            4K
            2.4K
            87
            The collaborative interface design tool.
            4K
            2.4K
            + 1
            87
            PROS OF FIGMA
            • 18
              Web-based application
            • 10
              Intuitive interface and perfect collaboration
            • 8
              Free software
            • 7
              Works on both Mac and Windows
            • 7
              Highly Collaborative
            • 6
              Great plugins, easy to extend
            • 5
              Works on multiple OS's
            • 5
              Imports Sketch files
            • 5
              Large community, tutorials, documentation
            • 5
              Hands done the best design tool for collaboration!
            • 4
              Prototyping, design files and comments all in one place
            • 4
              Interactive, event-based prototypes
            • 3
              No more syncing between Sketch and InVision
            CONS OF FIGMA
            • 6
              Limited Export options

            related Figma posts

            Jonathan Pugh
            Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 3M views

            I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

            For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

            Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

            I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

            I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

            I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

            I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

            For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

            For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

            For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

            I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

            So that's my latest mobile stack. What tools do you use? Have you tried these ones?

            See more
            Adam Neary

            The tool we use for editing UI is React Storybook. It is the perfect place to make sure your work aligns with designs to the pixel across breakpoints. You get fast hot module reloading and a couple checkboxes to enable/disable browser features like Flexbox.

            The only tricks I apply to Storybook are loading the stories with the mock data we’ve extracted from the API. If your mock data really covers all the various various possible states for your UI, you are good to go. Beyond that, if you have alternative states you want to account for, perhaps loading or error states, you can add them in manually.

            This is the crux of the matter for Storybook. This file is entirely generated from Yeoman (discussed below), and it delivers the examples from the Alps Journey by default. getSectionsFromJourney() just filters the sections.

            One other hack you’ll notice is that I added a pair of divs to bookend my component vertically, since Storybook renders with whitespace around the component. That is fine for buttons or UI with borders, but it’s hard to tell precisely where your component starts and ends, so I hacked them in there.

            Since we are talking about how all these fabulous tools work so well together to help you be productive, can I just say what a delight it is to work on UI with Zeplin or Figma side by side with Storybook. Digging into UI in this abstract way takes all the chaos of this madcap world away one breakpoint at a time, and in that quiet realm, you are good down to the pixel every time.

            To supply Storybook and our unit tests with realistic mock data, we want to extract the mock data directly from our Shared Development Environment. As with codegen, even a small change in a query fragment should also trigger many small changes in mock data. And here, similarly, the hard part is tackled entirely by Apollo CLI, and you can stitch it together with your own code in no time.

            Coming back to Zeplin and Figma briefly, they're both built to allow engineers to extract content directly to facilitate product development.

            Extracting the copy for an entire paragraph is as simple as selecting the content in Zeplin and clicking the “copy” icon in the Content section of the sidebar. In the case of Zeplin, images can be extracted by selecting and clicking the “download” icon in the Assets section of the sidebar.

            ReactDesignStack #StorybookStack #StorybookDesignStack
            See more
            Adobe Photoshop logo

            Adobe Photoshop

            2.2K
            1.4K
            56
            The industry standard in design, photography, video editing & more
            2.2K
            1.4K
            + 1
            56
            PROS OF ADOBE PHOTOSHOP
            • 14
              Photo editing
            • 14
              Powerful
            • 11
              Layers
            • 7
              You can use it for anything related to graphics
            • 4
              Magic wand
            • 2
              Pen Tool
            • 2
              Easy to crack
            • 2
              Raster-based Image Editing Software
            CONS OF ADOBE PHOTOSHOP
            • 4
              Heavyweight
            • 3
              Memory hungry
            • 2
              Steep learning curve

            related Adobe Photoshop posts