Alternatives to Google Fonts logo

Alternatives to Google Fonts

Font Awesome, Typekit, InVision, Figma, and Adobe Photoshop are the most popular alternatives and competitors to Google Fonts.
77.5K
13

What is Google Fonts and what are its top alternatives?

Google Fonts is a popular web font service provided by Google that allows users to easily add high-quality, open-source fonts to their websites. It offers a wide range of fonts to choose from, supports multiple languages, and provides simple integration with just a line of code. However, Google Fonts may have limitations in terms of customization options and loading speed.

  1. Adobe Fonts: Formerly known as Typekit, Adobe Fonts offers a vast library of high-quality fonts for web and desktop use. It provides seamless integration with Adobe Creative Cloud apps and allows for easy font syncing across projects. However, Adobe Fonts may require a subscription for full access.

  2. Font Squirrel: Font Squirrel offers a collection of free fonts that can be downloaded for use on websites. It also provides a webfont generator tool to convert fonts for web use. The platform is known for its easy-to-use interface and high-quality font selection.

  3. Font Awesome: Font Awesome is a popular icon and font toolkit that offers scalable vector icons and customizable CSS-based fonts. It provides a vast library of icons and fonts that can be easily integrated into websites. However, Font Awesome may have limitations in terms of font variety compared to Google Fonts.

  4. Adobe Edge Web Fonts: Adobe Edge Web Fonts is a free web font service that allows users to choose from a wide selection of high-quality fonts. It offers seamless integration with Adobe tools like Dreamweaver and Muse, making it easy to use for web design projects. However, the service may have a limited selection of fonts compared to Google Fonts.

  5. Fontstand: Fontstand is a unique font rental service that allows users to temporarily license fonts for use in projects. It offers a curated selection of high-quality fonts from independent foundries, making it a great choice for designers looking for unique typefaces. However, Fontstand may have higher costs compared to Google Fonts.

  6. Fontspring: Fontspring is a font marketplace that offers a wide selection of high-quality fonts for use in commercial projects. It provides a variety of licensing options and supports multiple languages, making it a versatile alternative to Google Fonts. However, Fontspring may require purchasing individual fonts.

  7. Fonts.com: Fonts.com is a font marketplace that offers a vast library of fonts from various foundries. It provides a user-friendly interface for browsing and purchasing fonts, making it easy to find the right typeface for web design projects. However, Fonts.com may have limitations in terms of free font options compared to Google Fonts.

  8. MyFonts: MyFonts is a font marketplace that offers a wide selection of fonts for web and desktop use. It provides advanced search options, sample texts, and font pairing suggestions, making it a useful tool for designers looking for specific typefaces. However, MyFonts may have higher costs for purchasing fonts compared to Google Fonts.

  9. Font Library: Font Library is an open-source font project that offers a collection of free fonts for web use. It provides a community-driven platform where designers can contribute and share their fonts, making it a collaborative alternative to Google Fonts. However, Font Library may have limited font options compared to commercial font services.

  10. Open Foundry: Open Foundry is an open-source platform that promotes free and open fonts for web and desktop use. It offers a diverse selection of typefaces created by independent designers and foundries, making it a great resource for discovering unique fonts. However, Open Foundry may have limitations in terms of font availability and support compared to established font services.

Top Alternatives to Google Fonts

  • Font Awesome
    Font Awesome

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

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

  • InVision
    InVision

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

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

  • Sketch
    Sketch

    Easily create complex shapes with our state-of-the-art vector boolean operations and take advantage of our extensive layer styles. ...

  • Adobe Illustrator
    Adobe Illustrator

    The industry-standard vector graphics app lets you create logos, icons, sketches, typography, and complex illustrations for print, web, interactive, video, and mobile. ...

  • Adobe XD
    Adobe XD

    A vector-based tool developed and published by Adobe Inc for designing and prototyping user experience for web and mobile apps. ...

Google Fonts alternatives & related posts

Font Awesome logo

Font Awesome

57.5K
15.1K
21
The internet's most popular icon toolkit
57.5K
15.1K
+ 1
21
PROS OF FONT AWESOME
  • 8
    CDN
  • 7
    CSS Styling
  • 6
    Open source
  • 0
    Easy Upgrades
  • 0
    Auto-accessibility (A11y)
  • 0
    API
CONS OF FONT AWESOME
    Be the first to leave a con

    related Font Awesome 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
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 24 upvotes · 4.9M 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
    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

        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 · 579.9K 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 · 159.2K 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
          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

          Sketch logo

          Sketch

          1.7K
          1K
          59
          Professional Digital Design for Mac
          1.7K
          1K
          + 1
          59
          PROS OF SKETCH
          • 23
            Lightweight alternative to Photoshop
          • 11
            Mirror designs on mobile devices
          • 9
            Reusable elements/components
          • 7
            Vector
          • 5
            Plugins for everything
          • 2
            Real-time design preview on iOS devices
          • 1
            Constant updates
          • 1
            Thought for UI design
          CONS OF SKETCH
          • 4
            Not for Windows
          • 3
            Horrible for slide presentations

          related Sketch posts

          Priit Kaasik
          CTO at Katana Cloud Inventory · | 8 upvotes · 579.9K 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
          Adobe Illustrator logo

          Adobe Illustrator

          1.5K
          981
          2
          Create logos, icons, sketches, typography and complex illustrations
          1.5K
          981
          + 1
          2
          PROS OF ADOBE ILLUSTRATOR
          • 2
            Vector Creation
          CONS OF ADOBE ILLUSTRATOR
          • 3
            Massive disk space usage
          • 3
            Adobe Updater to slow you down even more
          • 2
            Expensive
          • 1
            Not really a tool for web design
          • 1
            Clunky

          related Adobe Illustrator posts

          Adobe XD logo

          Adobe XD

          1.3K
          941
          55
          UX/UI design and collaboration tool
          1.3K
          941
          + 1
          55
          PROS OF ADOBE XD
          • 15
            Free
          • 9
            Interactive Prototypes
          • 8
            Reusable elements/components
          • 8
            Clean Design
          • 8
            Vector
          • 5
            Imports Sketch files
          • 1
            Repeat Grid
          • 1
            Import Adobe files
          CONS OF ADOBE XD
          • 6
            No dark theme

          related Adobe XD posts

          Howard Kiewe
          Senior Director of UX at ValGenesis · | 6 upvotes · 37.6K views

          Our UX designers currently use Adobe XD and we are considering moving to UXPin with Merge. Our UI developers are transitioning to React and perhaps React Native, so I'm intrigued by UXPin/Merge abilities to leverage React components, both for improved design fidelity and easier integration with production components. If you use or have evaluated UXPin and/or Merge, I'm interested to know your observations on UXPin/Merge as a design tool compared to any alternative, as well as to what extent Merge delivers on its promise of seamless integration between designers and front-end developers.

          See more
          Nadia Matveyeva
          UI Designer at freelancer · | 5 upvotes · 159.2K 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