Alternatives to Evergreen logo

Alternatives to Evergreen

Timely, React Router, styled-components, Angular CLI, and Ant Design are the most popular alternatives and competitors to Evergreen.
7
23
+ 1
0

What is Evergreen and what are its top alternatives?

Evergreen is a pragmatic UI kit for building evolving products on the web. It is built and maintained open-source by Segment.
Evergreen is a tool in the JavaScript Framework Components category of a tech stack.
Evergreen is an open source tool with 10.5K GitHub stars and 631 GitHub forks. Here鈥檚 a link to Evergreen's open source repository on GitHub

Top Alternatives to Evergreen

  • Timely

    Timely

    It is a new time tracking app for iOS and the Web that promises to do away with the pain of filling out timesheets and other related paperwork by allowing users to schedule how time will be spent in advance. The definitive automatic time tracking tool for improving productivity and profitability. ...

  • React Router

    React Router

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

  • styled-components

    styled-components

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

  • Angular CLI

    Angular CLI

    A command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications. You can use the tool directly in a command shell, or indirectly through an interactive UI such as Angular Console. ...

  • Ant Design

    Ant Design

    An enterprise-class UI design language and React-based implementation. Graceful UI components out of the box, base on React Component. A npm + webpack + babel + dora + dva development framework. ...

  • Angular Material

    Angular Material

    Sprint from Zero to App. Hit the ground running with comprehensive, modern UI components that work across the web, mobile and desktop. It allows to create material styled angular apps fast and easy. ...

  • Storybook

    Storybook

    It is an open source tool for developing UI components in isolation for React, Vue, and Angular. It makes building stunning UIs organized and efficient. ...

  • Vue CLI

    Vue CLI

    Vue CLI aims to be the standard tooling baseline for the Vue ecosystem. It ensures the various build tools work smoothly together with sensible defaults so you can focus on writing your app instead of spending days wrangling with config. ...

Evergreen alternatives & related posts

Timely logo

Timely

4
9
0
A time tracking app which works to manage your time your way
4
9
+ 1
0
PROS OF TIMELY
    Be the first to leave a pro
    CONS OF TIMELY
      Be the first to leave a con

      related Timely posts

      React Router logo

      React Router

      1.4K
      920
      16
      A complete routing solution for React.js
      1.4K
      920
      + 1
      16
      PROS OF REACT ROUTER
      • 12
        Because there's not alternative
      • 2
        Extremely easy to use
      • 2
        Similar implementations for React and React Native
      CONS OF REACT ROUTER
        Be the first to leave a con

        related React Router posts

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

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

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

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

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

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

        See more

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

        See more
        styled-components logo

        styled-components

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

          related styled-components posts

          Johnny Bell
          Software Engineer at Weedmaps | 14 upvotes 路 452.7K views

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

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

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

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

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

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

          #StackDecisionsLaunch

          See more

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

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

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

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

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

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

          See more
          Angular CLI logo

          Angular CLI

          695
          541
          0
          A command line interface for Angular
          695
          541
          + 1
          0
          PROS OF ANGULAR CLI
            Be the first to leave a pro
            CONS OF ANGULAR CLI
              Be the first to leave a con

              related Angular CLI posts

              Vaibhav Taunk
              Team Lead at Technovert | 31 upvotes 路 1.3M views

              I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

              See more

              Picked Angular 2 as framework since Angular CLI made it easy to get started on a self-contained frontend web project with TypeScript for easier development -- thanks to intellisense extensions for Visual Studio Code, hassle-free browser compatibility with the built-in Babel transpiler and packaging with the built-in Webpack configuration.

              See more
              Ant Design logo

              Ant Design

              642
              1K
              155
              A set of high-quality React components
              642
              1K
              + 1
              155
              PROS OF ANT DESIGN
              • 30
                Lots of components
              • 24
                Polished and enterprisey look and feel
              • 15
                Easy to integrate
              • 14
                Es6 support
              • 14
                TypeScript
              • 13
                Beautiful and solid
              • 12
                Quick Release rhythm
              • 9
                Beautifully Animated Components
              • 9
                Great documentation
              • 9
                Typescript support
              • 6
                Short Code
              CONS OF ANT DESIGN
              • 12
                Less
              • 6
                Large File Size
              • 4
                Close
              • 1
                Poor accessibility support

              related Ant Design posts

              Sarmad Chaudhary
              Founder & CEO at Ebiz Ltd. | 8 upvotes 路 158K views

              Hi there!

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

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

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

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

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

              See more
              Shared insights
              on
              Material-UIMaterial-UIAnt DesignAnt Design

              Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.

              Here is a list of my requirements.

              1. Good documentation.
              2. easy CRUD ( date picker and date range picker bundled )
              3. built-in multi-lang feature or Great 3rd library support
              4. Admin dashboard template
              5. well code maintenance

              Which is better for the long run?

              See more
              Angular Material  logo

              Angular Material

              469
              542
              25
              Easy to use material design for angular
              469
              542
              + 1
              25
              PROS OF ANGULAR MATERIAL
              • 10
                Components
              • 5
                Backed by a well known company
              • 3
                Simple
              • 2
                Easy
              • 2
                Very good documentation
              • 2
                Rte
              • 1
                Implements well known material design
              CONS OF ANGULAR MATERIAL
              • 2
                Fairly large

              related Angular Material posts

              Storybook logo

              Storybook

              443
              260
              0
              Build bulletproof UI components faster
              443
              260
              + 1
              0
              PROS OF STORYBOOK
                Be the first to leave a pro
                CONS OF STORYBOOK
                  Be the first to leave a con

                  related Storybook posts

                  Robert Zuber

                  We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

                  See more
                  Vue CLI logo

                  Vue CLI

                  366
                  372
                  3
                  Standard Tooling for Vue.js Development
                  366
                  372
                  + 1
                  3
                  PROS OF VUE CLI
                  • 1
                    GUI for installing dependencies
                  • 1
                    Visual Web Interface
                  • 1
                    Detects and run npm tasks
                  CONS OF VUE CLI
                    Be the first to leave a con

                    related Vue CLI posts

                    Simon Reymann
                    Senior Fullstack Developer at QUANTUSflow Software GmbH | 19 upvotes 路 483.1K 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