What is PrimeFaces and what are its top alternatives?
Top Alternatives to PrimeFaces
It is the fastest way to build web applications in Java. It automates the communication between your server and the browser and gives you a high-level component API for all Vaadin components ...
- Spring MVC
A Java framework that follows the Model-View-Controller design pattern and provides an elegant solution to use MVC in spring framework by the help of DispatcherServlet. ...
It is an advanced UI component framework for easily integrating Ajax capabilities into business applications using JSF. ...
It is a powerful JSF framework that takes the best from Bootstrap and jQuery UI to let develop well-designed responsive state-of-the-art next-gen Front-end Enterprise Applications fast and easy supporting HTML5. ...
It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community ...
It is a modern server-side Java template engine for both web and standalone environments. It is aimed at creating elegant web code while adding powerful features and retaining prototyping abilities. ...
Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...
PrimeFaces alternatives & related posts
- Quick to develop887
- Great mvc587
- Backed by google503
- Two-way data binding349
- Open source328
- Dependency injection305
- Great community63
- Extend html vocabulary38
- Easy to test26
- Easy to learn24
- Easy to templates23
- Great documentation23
- Easy to start21
- Light weight17
- Angular 2.014
- Great extensions13
- Easy to prototype with10
- High performance8
- Two-way binding7
- Lots of community modules7
- Easy to e2e6
- Clean and keeps code readable6
- Easy for small applications5
- One of the best frameworks5
- Fast development4
- Works great with jquery4
- I do not touch DOM3
- Be a developer, not a plumber.2
- Declarative programming2
- The two-way Data Binding is awesome2
- Hierarchical Data Structure2
- The powerful of binding, routing and controlling routes1
- Fkin awesome1
- Opinionated in the right areas1
- Supports api , easy development1
- Common Place1
- Very very useful and fast framework for development1
- Amazing community support1
- Readable code1
- Linear learning curve1
- Programming fun again1
- Consistency with backend architecture if using Nest1
- Httpș//Acoperișul 07576043350
- Angular js0
- Oautho loc0
- Acoperișul 07576043350
- Bot Ionescu0
- Dependency injection3
- Learning Curve2
- Event Listener Overload2
- Hard to learn1
related AngularJS posts
Our whole Node.js backend stack consists of the following tools:
- Lerna as a tool for multi package and multi repository management
- npm as package manager
- NestJS as Node.js framework
- TypeScript as programming language
- ExpressJS as web server
- Swagger UI for visualizing and interacting with the API’s resources
- Postman as a tool for API development
- TypeORM as object relational mapping layer
- JSON Web Token for access token management
The main reason we have chosen Node.js over PHP is related to the following artifacts:
- Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:
- 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.
- Open Source6
- Example packages2
- OSGI Support1
- Paid for more features3
related Vaadin posts
related Spring MVC posts
Material Design for Angular Angular 2 Node.js TypeScript Spring-Boot RxJS Microsoft SQL Server Hibernate Spring MVC
We built our customer facing portal application using Angular frontend backed by Spring boot.
related RichFaces posts
related BootsFaces posts
- Rich and comprehensive Request Life-cycle2
- Very Mature UI framework1
- Server Side component1
related JSF posts
I need to modernize a Java web application that runs on JSF. I am used to building websites, so Bootstrap kinda feels like "home." But when it comes to applications, I feel Bootstrap is not the right way to go. Can someone explain to me what PrimeFaces is capable of in comparison with BS?
- Its delicous2
related Thymeleaf posts
I need some advice to choose an engine for generation web pages from the Spring Boot app. Which technology is the best solution today? 1) JSP + JSTL 2) Apache FreeMarker 3) Thymeleaf Or you can suggest even other perspective tools. I am using Spring Boot, Spring Web, Spring Data, Spring Security, PostgreSQL, Apache Tomcat in my project. I have already tried to generate pages using jsp, jstl, and it went well. However, I had huge problems via carrying already created static pages, to jsp format, because of syntax. Thanks.
- UI components1.2K
- Great docs779
- HTML, CSS, and JS framework467
- Open source410
- Widely used374
- HTML framework242
- Easy setup77
- Mobile first77
- Great grid system58
- Great community51
- Future compatibility38
- Very powerful foundational front-end framework28
- Build faster prototypes19
- Good for a person who hates CSS7
- Easy to setup and learn4
- Rapid development4
- Love it4
- Great and easy to use3
- Powerful grid system, Rapid development, Customization2
- Great customer support2
- Easy to use2
- Provide angular wrapper2
- Clean and quick frontend development2
- Great and easy2
- Sprzedam opla2
- Great and easy to make a responsive website2
- Love the classes?1
- Felxible, comfortable, user-friendly1
- The fame1
- Easy setup21
- Painless front end development1
- So clean and simple1
- It's fast1
- Pre-Defined components1
- Not tied to jQuery1
- Numerous components1
- Responsive design1
- Design Agnostic1
- Every site uses the defaults16
- Grid system break points aren't ideal15
- Too much heavy decoration in default look14
- Verbose styles8
- Super heavy1
related Bootstrap posts
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.
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! :)
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.