Alternatives to PrimeReact logo

Alternatives to PrimeReact

Material-UI, Ant Design, Bootstrap, reactstrap, and PrimeNg are the most popular alternatives and competitors to PrimeReact.
16
140
+ 1
10

What is PrimeReact and what are its top alternatives?

PrimeReact is a rich set of open source UI Components for React.
PrimeReact is a tool in the JavaScript Framework Components category of a tech stack.
PrimeReact is an open source tool with 2.7K GitHub stars and 578 GitHub forks. Here鈥檚 a link to PrimeReact's open source repository on GitHub

Top Alternatives to PrimeReact

  • Material-UI
    Material-UI

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

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

  • Bootstrap
    Bootstrap

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

  • reactstrap
    reactstrap

    It provides prebuilt Bootstrap 4 components that allow a great deal of flexibility and prebuilt validation. This allows us to quickly build beautiful forms that are guaranteed to impress and provide an intuitive user experience. ...

  • PrimeNg
    PrimeNg

    It has a rich collection of components that would satisfy most of the UI requirements of your application like datatable, dropdown, multiselect, notification messages, accordion, breadcrumbs and other input components. So there would be no need of adding different libraries for different UI requirements. ...

  • Semantic UI
    Semantic UI

    Semantic empowers designers and developers by creating a shared vocabulary for UI. ...

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

PrimeReact alternatives & related posts

Material-UI logo

Material-UI

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

related Material-UI posts

Adebayo Akinlaja
Engineering Manager at Andela | 27 upvotes 路 1M views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen鈥攕ince I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more

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

See more
Ant Design logo

Ant Design

858
1.4K
225
A set of high-quality React components
858
1.4K
+ 1
225
PROS OF ANT DESIGN
  • 43
    Lots of components
  • 34
    Polished and enterprisey look and feel
  • 22
    TypeScript
  • 20
    Easy to integrate
  • 18
    Es6 support
  • 17
    Beautiful and solid
  • 16
    Beautifully Animated Components
  • 15
    Quick Release rhythm
  • 14
    Great documentation
  • 14
    Typescript support
  • 11
    Short Code
  • 1
    Easy to customize Forms
CONS OF ANT DESIGN
  • 18
    Less
  • 8
    Large File Size
  • 7
    Close
  • 4
    Poor accessibility support
  • 1
    Sdf
  • 1
    Dangerous to use as a base in component libraries
  • 1
    Gago
  • 0
    D

related Ant Design posts

Sarmad Chaudhary
Founder & CEO at Ebiz Ltd. | 9 upvotes 路 523K 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
Bootstrap logo

Bootstrap

53.7K
12.3K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
53.7K
12.3K
+ 1
7.6K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 943
    Consistent
  • 779
    Great docs
  • 678
    Flexible
  • 467
    HTML, CSS, and JS framework
  • 410
    Open source
  • 374
    Widely used
  • 367
    Customizable
  • 242
    HTML framework
  • 77
    Easy setup
  • 77
    Mobile first
  • 77
    Popular
  • 58
    Great grid system
  • 51
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 28
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 14
    Grids
  • 8
    Clean
  • 7
    Good for a person who hates CSS
  • 4
    Easy to setup and learn
  • 4
    Rapid development
  • 4
    Love it
  • 3
    Great and easy to use
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Easy to use
  • 2
    Provide angular wrapper
  • 2
    Community
  • 2
    Clean and quick frontend development
  • 2
    Great and easy
  • 2
    Sprzedam opla
  • 2
    Great and easy to make a responsive website
  • 1
    Love the classes?
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 1
    Painless front end development
  • 1
    So clean and simple
  • 1
    Reactjs
  • 1
    It's fast
  • 1
    Geo
  • 1
    Boostrap
  • 1
    Pre-Defined components
  • 1
    Not tied to jQuery
  • 1
    Numerous components
  • 1
    Responsive design
  • 1
    Material-ui
  • 1
    Design Agnostic
  • 1
    Recognizable
  • 1
    Intuitive
  • 0
    Frefsd
CONS OF BOOTSTRAP
  • 25
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 15
    Grid system break points aren't ideal
  • 14
    Too much heavy decoration in default look
  • 8
    Verbose styles
  • 1
    Super heavy

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Technical Lead | 19 upvotes 路 2.8M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Francisco Quintero
Tech Lead at Dev As Pros | 13 upvotes 路 881.2K 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
reactstrap logo

reactstrap

90
146
3
Easy to use React Bootstrap 4 components compatible with React
90
146
+ 1
3
PROS OF REACTSTRAP
  • 3
    Prebuilt Bootstrap 4 components
CONS OF REACTSTRAP
    Be the first to leave a con

    related reactstrap posts

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

    See more
    Shared insights
    on
    Material-UIMaterial-UIreactstrapreactstrap

    I need to create a footer. Can I use reactstrap and Material-UI, or is it one or the other? If it's only one, what is the best way to create a footer with MaterialUI?

    See more
    PrimeNg logo

    PrimeNg

    107
    204
    7
    A collection of rich UI components for Angular
    107
    204
    + 1
    7
    PROS OF PRIMENG
    • 4
      Complete
    • 3
      Wide range of components
    CONS OF PRIMENG
    • 3
      Need to buy themes
    • 2
      No documentation
    • 2
      Components are hard to customize
    • 2
      Easy to use
    • 2
      Functionality differs for all components
    • 2
      Hard to understand

    related PrimeNg posts

    I am a novice to AngularJS, but I have a strong web development background. I need help with the pros and cons of choosing the Angular Material or PrimeNg for our new application. Our new application will be using Angular for the front-end and .NET Core for the Web API. I looked at both tools and leaned toward Angular Material. It would be beneficial if I could obtain some expert advice from the community.

    See more
    Shared insights
    on
    BootstrapBootstrapPrimeNgPrimeNgAngularJSAngularJS

    We are building a PWA using AngularJS targeting Mobiles, Tablets, Laptops and Desktops. Like for smaller to larger screens. This is our first PWA and my first project in Angular. We are confused between PrimeNg and Bootstrap. I read in an article that PrimeNg has got Bootstrap implemented in it from 5.x.x version. Which is the best Framework for this?

    See more
    Semantic UI logo

    Semantic UI

    870
    1.5K
    673
    A UI Component library implemented using a set of specifications designed around natural language
    870
    1.5K
    + 1
    673
    PROS OF SEMANTIC UI
    • 157
      Easy to use and looks elegant
    • 92
      Variety of components
    • 64
      Themes
    • 61
      Has out-of-the-box widgets i would actually use
    • 57
      Semantic, duh
    • 44
      Its the future
    • 42
      Open source
    • 37
      Very active development
    • 31
      Far less complicated structure
    • 28
      Gulp
    • 9
      Already has more features than bootstrap
    • 8
      Just compare it to Bootstrap and you'll be hooked
    • 7
      UI components
    • 7
      Clean and consistent markup model
    • 6
      Responsiveness
    • 4
      Elegant. clean. readable. maintainable
    • 4
      Because it is semantic :-D
    • 4
      Good-Looking
    • 2
      Great docs
    • 2
      Consistent
    • 2
      Is big and look really great, nothing like this
    • 2
      Modular and scalable
    • 1
      Jquery
    • 1
      Easy to use
    • 1
      Blends with reactjs
    CONS OF SEMANTIC UI
    • 5
      Outdated build tool (gulp 3))
    • 3
      Poor accessibility support
    • 3
      HTML is not semantic (see list component)
    • 2
      Javascript is tied to jquery

    related Semantic UI 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
    React Router logo

    React Router

    2.1K
    1K
    12
    A complete routing solution for React.js
    2.1K
    1K
    + 1
    12
    PROS OF REACT ROUTER
    • 12
      Because there's not alternative
    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

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

        related styled-components posts

        Johnny Bell

        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