DHTMLX delivers JavaScript/HTML5 libraries and UI widgets designed for building enterprise web apps of any complexity. With these out-of-the-box components, web developers can streamline their coding processes and integrate advanced functionality, to reduce development time. The actual DHTMLX product lineup comprises a range of web-based tools that can cover most of the contemporary business needs. DHTMLX
$799
one-time fee for 1 developer
React (React.js)
Score 8.9 out of 10
N/A
React or React.js is a JavaScript library for building user interfaces. React enables users to create interactive UIs.
N/A
Pricing
DHTMLX
React (React.js)
Editions & Modules
DHTMLX Gantt Individual - Professional Functionality with Standard Support
$799
one-time fee for 1 developer
DHTMLX Gantt Commercial - Professional Functionality with Premium Support
$1599
one-time fee for 5 developers
DHTMLX Gantt Enterprise - Professional Functionality with Premium Support
$2999
one-time fee for 20 developers
DHTMLX Gantt Ultimate - Professional Functionality with Ultimate Support
$5999
one-time fee for an unlimited number of developers
No answers on this topic
Offerings
Pricing Offerings
DHTMLX
React (React.js)
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
UI widgets are available standalone or "a la carte," or as part of bundles built around a theme (e.g. complete edition, scheduling components, planning components, etc.).
Compared with from scratch development of a graphical modeler or even a tabular representation in JS, using DHTMLX saved us a significant amount of precious time. By relying on this actively maintained product, we've been able to concentrate on the business aspects that are …
We looked at Kendo UI for ASP.Net Core as it has a Gantt chart but it was not as close a fit to our requirements as the DHTMLX Gantt Resource Management component. We'd have had to do much more work to make this fit.
DHTMLX offers a package of specialized components which is difficult to find in other libraries - specifically rich functional components like Gantt chart and scheduler
DHTMLX surpasses other solutions with its extensive features and strong maintenance support. It offers a wide range of capabilities, including advanced data manipulation, sophisticated visualizations, and intricate user interface controls. DHTMLX stands out in its commitment to …
DHTMLX library boasts lots of readily available components that can be easily integrated into web applications. Each feature is equipped with a multitude of events and methods that provide developers with complete control over data manipulation and management. DHTMLX is more …
We have tried few other options also which are not exactly tools and they are not listed here. The brief documentation along with the features samples makes DHTMLX better when compared with other options.
This was very difficult because flutter is extremely easy to use and if you have React in the background, it makes it even easier. What makes Flutter a little better is the response, the components are rendered before the loading and that gives the user a better experience. The …
I have also used Angular before coming to React. Web apps created with React are much faster than Angular because React is based on virtual DOM which reloads only those components of the web page that change and everything else remains the same. Angular's learning curve is also …
I have also used Vue, Angular, and Ember for various projects. Out of the three, I am most intrigued by Vue. It takes a more beginner-friendly approach than React and changes some of the abstractions it uses to be more transparent to the user. It also comes with a lot more …
There are other options for building SPAs, and the two most common aside from React are Vue and Angular. React has been the leader of the pack for a while and has been an innovator. Angular is good for companies that want an opinionated framework so that it standardizes …
Like most people, I started in serious client-side web development with the introduction of jQuery, the first robust library for cross-browser DOM manipulation. React provides a much closer WYSIWYG translation from the declarative JSX template to HTML elements compared to using …
While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at …
When choosing a front-end framework, you have a ton of choices. There are numerous articles that will try to convince you this way or that about which one is better. I have used Blaze as a UI layer for Meteor Application development quite extensively and have found it to …
DHTMLX is an excellent choice for incorporating complex components into your website or platform. Its versatility and customization options make it suitable for various industries and use cases. With DHTMLX, you can seamlessly integrate sophisticated data grids, interactive charts, customizable UI controls, and dynamic calendars into your existing infrastructure. These components can be tailored to match your branding and design requirements, ensuring a seamless integration with your platform's aesthetics. Additionally, DHTMLX provides comprehensive documentation and responsive support, making it easy for developers to utilize the full potential of the components. In summary, DHTMLX offers the flexibility and functionality needed to enhance your software applications with powerful and visually appealing features.
React is a JavaScript user interface construction library that works well for:
Developing web apps with dynamic and complicated user interfaces.
creating reusable UI elements that may be used in other applications.
creating single-page applications with dynamic content updates that don't require a page reload.
The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.
React, on the other hand, might be less suitable for:
Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
When creating mobile apps, React Native is a better option.
Server side rendering only, as React is designed to run on the client side.
Solid backing by large organization (Facebook) thats committed to keeping the development on the project. In my mind, this is the number one priority for any library because without this: time is wasted on getting up-to speed on a library that you will never use, have a codebase with a library thats hard to maintain because few years down the lane, hiring devs to maintain an unsupported library is very difficult.
As with any libraries, open source community's support is critical for success of any framework because this allows for more pre-built components that could be used right out-of-box => makes Development using React a breeze.
React's Stateful and Stateless components make organizing your code a breeze. These components would also allow for writing clean Unit Tests on the logic.
React's component lifecycle. It offers a variety of lifecycle methods, that allows for handling different scenarios of loading and manipulating data in the UI.
I found React's documentation very well maintained with plenty of examples explaining each feature.
Responsiveness is a very important criteria in selecting a UI and React is very responsive. It does some neat optimizations on re-rendering using virtual DOM and would only re-render parts of the DOM that changed. These optimizations makes React Applications feel really fast.
React Native would allow for building applications that span across web and mobile interfaces (iOS and Android). This makes learning React even more enticing, because using a single library, you could build applications that span across Web, iOS and Android.
create-react-app is an effort by Facebook (creators of React) that makes getting started with React really easy. It does all the heavy lifting of configurations for you and allow you to focus on just development.
Small footprint, minified React + React DOM is under 150Kb, that makes loading UI's with react really fast.
React + Enzyme (backed by Airbnb) + Sinon + Mocha + Chai makes unit testing the UI components fun and improves the overall maintainability of the project.
React's state management can get hairy if you have a deeply nested component and need to pass things up or down the tree very far. This is where libraries like Redux come in, however.
The progressive nature of its development and change cycles can leave information outdated online faster than other frameworks. This can make finding help or documentation on 3rd party sites frustrating.
The learning curve on "thinking in React" can be slightly higher than other more familiar patterns of web development.
Building an app in it can be cumbersome to set up with webpack, but things like Create React App can get you going in a jiffy.
With regard to the two major components we used, namely the tabular representation and the graphical modeler, we were able to effectively replace the existing building blocks of our applications by integrating them. We were able to retain existing functionalities and benefit from a significant enhancement with what DHTMLX offers natively. This made it easy for us to get our end-users to adopt the change.
There are a few things that may take some getting used to when coming to a modern JS frontend. Tools like Babel and Webpack (or abstractions that hide their details from you) are often a starting point and JSX can be confusing at first. But assuming the developer is already familiar with modern frontend tools, React is a very natural fit and makes creating user interfaces a joy.
Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
DHTMLX library boasts lots of readily available components that can be easily integrated into web applications. Each feature is equipped with a multitude of events and methods that provide developers with complete control over data manipulation and management. DHTMLX is more easy for building enterprise-level applications that require complex UI elements and data visualization.
There are other options for building SPAs, and the two most common aside from React are Vue and Angular. React has been the leader of the pack for a while and has been an innovator. Angular is good for companies that want an opinionated framework so that it standardizes practices. However, Angular is known to be more difficult to work with and unnecessarily complex. Vue is seen as taking the best from React and Angular, and it is built for incremental upgrades. Vue has a passionate and growing user base, but it hasn't quite caught React in popularity.
Since we're still in the conversion cycle, all the data is not in. But React has had a positive impact on Developer productivity and the ability to produce efficient, highly flexible UX. This in turn, enhances our customer experience, which is generally the most important component of our ROI.
Conversion has been difficult since it requires a change of mindset. Most developers have adapted quite well, but the process has been lengthy, and 2 years in, we are still not fully converted. This essentially is a temporary negative impact on ROI.