Alternatives to JetBrains Mono logo

Alternatives to JetBrains Mono

Hack, Google Fonts, Font Awesome, InVision, and Typekit are the most popular alternatives and competitors to JetBrains Mono.
14
13
+ 1
0

What is JetBrains Mono and what are its top alternatives?

JetBrains Mono is a free and open-source typeface designed specifically for developers with a focus on readability and ease of use. It features clear and concise design, customizable ligatures, and supports various programming languages. However, one limitation of JetBrains Mono is that it may not have as many font styles and weights as other alternatives in the market.

  1. Fira Code: Fira Code is a free monospaced font with programming ligatures that enhance readability by combining multiple characters into a single glyph.
  2. Cascadia Code: Developed by Microsoft, Cascadia Code is a versatile monospaced font optimized for terminal and code editors, featuring ligatures and support for various programming languages.
  3. Inconsolata: Inconsolata is a popular monospaced font known for its elegant design, clear readability, and support for different languages, making it a great alternative for JetBrains Mono.
  4. Droid Sans Mono: Droid Sans Mono is a simple and easy-to-read monospaced font that is freely available for developers, offering good legibility and clarity for coding.
  5. Hack: Hack is a free and open-source typeface designed specifically for source code and offers clear legibility, various styles, and support for programming ligatures.
  6. IBM Plex Mono: IBM Plex Mono is a modern monospaced font designed by IBM, featuring a clean and futuristic design, multiple weights, and comprehensive language support.
  7. Iosevka: Iosevka is a slender monospaced font optimized for programming that offers versatility, ligatures, customizability, and support for different writing systems.
  8. Ubuntu Mono: Ubuntu Mono is a simple and clear monospaced font developed by Ubuntu, offering good readability, multiple weights, and compatibility with various operating systems.
  9. Source Code Pro: Source Code Pro is a popular monospaced font by Adobe, known for its clean and modern design, diverse styles, and support for ligatures and programming languages.
  10. Monoid: Monoid is a customizable monospaced font tailored for coding, featuring a distinctive minimalistic design, ligatures, and support for multiple languages.

Top Alternatives to JetBrains Mono

  • Hack
    Hack

    Hack provides instantaneous type checking via a local server that watches the filesystem. It typically runs in less than 200 milliseconds, making it easy to integrate into your development workflow without introducing a noticeable delay. ...

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

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

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

  • Sketch
    Sketch

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

JetBrains Mono alternatives & related posts

Hack logo

Hack

570
29
A programming language for HHVM that interoperates seamlessly with PHP
570
29
PROS OF HACK
  • 6
    Interoperates seamlessly with php
  • 6
    Open source
  • 5
    Backed by facebook
  • 4
    HHVM
  • 2
    PHP like
  • 2
    Great documentation
  • 2
    Generics
  • 1
    Fast
  • 1
    Used by facebook
  • 0
    Great type system
  • 0
    Easy to learn
CONS OF HACK
    Be the first to leave a con

    related Hack posts

    Throughout 2016, Slack began migrating from PHP5 to Hack. They cite several well-known challenges inherent to PHP, including surprise type conversions, inconsistency around reference semantics, inconsistencies in the standard library, and the fact that “PHP tries very, very hard to keep the request running, even if it has done something deeply strange.”

    To overcome these challenges while maintaining the unique values of PHP, Slack turned to Hack, a gradual typing system for PHP. Hack runs on the HipHop Virtual Machine, or HHVM, an open source just-in-time (JIT) environment for PHP.

    See more

    Since the beginning, Cal Henderson has been the CTO of Slack. Earlier this year, he commented on a Quora question summarizing their current stack.

    Apps
    • Web: a mix of JavaScript/ES6 and React.
    • Desktop: And Electron to ship it as a desktop application.
    • Android: a mix of Java and Kotlin.
    • iOS: written in a mix of Objective C and Swift.
    Backend
    • The core application and the API written in PHP/Hack that runs on HHVM.
    • The data is stored in MySQL using Vitess.
    • Caching is done using Memcached and MCRouter.
    • The search service takes help from SolrCloud, with various Java services.
    • The messaging system uses WebSockets with many services in Java and Go.
    • Load balancing is done using HAproxy with Consul for configuration.
    • Most services talk to each other over gRPC,
    • Some Thrift and JSON-over-HTTP
    • Voice and video calling service was built in Elixir.
    Data warehouse
    • Built using open source tools including Presto, Spark, Airflow, Hadoop and Kafka.
    Etc
    See more
    Google Fonts logo

    Google Fonts

    77.8K
    13
    Making the web more beautiful, fast, and open through great typography
    77.8K
    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.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
      Font Awesome logo

      Font Awesome

      57.7K
      21
      The internet's most popular icon toolkit
      57.7K
      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 · 3.1M 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
        InVision logo

        InVision

        8.5K
        618
        Prototyping & Collaboration For Design Teams
        8.5K
        618
        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
        • 4
          Collaboration
        • 3
          Easy
        • 2
          Rapid Prototyping
        • 2
          LiveShare
        • 1
          Annotation
        • 1
          Allows for a comprehensive workflow
        • 1
          Beautiful UI
        • 1
          Brings mockups to life
        • 1
          They are always improving the product suite
        CONS OF INVISION
          Be the first to leave a con

          related InVision posts

          Priit Kaasik
          CTO at Katana Cloud Inventory · | 8 upvotes · 591.3K 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 · 168.8K 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
          0
          An online service offering high-quality fonts
          4.2K
          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

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

              related Figma posts

              Jonathan Pugh
              Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 3.1M 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
              56
              The industry standard in design, photography, video editing & more
              2.2K
              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
              59
              Professional Digital Design for Mac
              1.7K
              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 · 591.3K 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