DHTMLX vs. React Native

Rapid development of web applications: DHTMLX provides a set of pre-built UI widgets that can be easily integrated into web applications, which makes it well suited for developing applications quickly. DHTMLX is well suited for building enterprise-level applications that require complex UI elements and data visualization. DHTMLX is less appropriate for Simple applications: If you are building a simple application that does not require a complex UI, DHTMLX may be overkill, and you may be better off using a lighter-weight framework.

Incentivized

We are implementing React Native framework for the development of the Front-End for the machine learning models maintenance and monitoring website. It provides meaningful error messages, and time-saving and robust tools make it a premium choice over other platforms. Moreover, it provides intelligent debugging tools and error report mechanisms. And most importantly for us, it provides the aesthetic minimal functionality to learn in order to implement it, thereby eliminating the need to work in Xcode or Android Studio for iOS or Android apps respectively.

Incentivized

• We got a response and fix for every issue we opened a ticket for
• The components are full with quite a lot of feature
• The team is responsiveness is very quick

• Customized Components
• State Management
• Extensibility
• Usage and Community

Incentivized

• Advanced customization of editors
• Advanced charts representation
• Auto layout with specific arrangements

• Performance is still lower than native app development (Kotlin, Swift, etc.)
• Not efficient design-wise (if you are planning to implement some advanced design, then you should reconsider the approach provided by React Native)
• Issues with the update to the last release of React Native

Incentivized

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.

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.

Incentivized

Decision for React Native came mainly from the big popularity of the framework. Thus, we had a big base of resources we could come back to. We also used it because it is a javascript framework. Thus, we could utilize the already existing experience in javascript and web development to ensure a smoother implementation of the app.

Incentivized

• Rapid development of web applications
• Rich data visualization tools, which makes it ideal for building data-driven applications
• Suited for building enterprise-level applications

Incentivized

• Decreased the development process time via robust and easy-to-use platform
• Easier to debug with a provided intelligent tool as well as error-prone messages, which allows developing in a paced manner for the decreased Time-To-Market
• Reusable code base can directly impact lead time and thereby on ROI in a positive manner

Incentivized