DHTMLX delivers versatile JavaScript/HTML5 libraries and UI widgets designed for building modern 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
$79
one-time fee lowest cost single component
Oracle Java SE
Score 8.0 out of 10
N/A
Oracle Java SE is a programming language and gives customers enterprise features that minimize the costs of deployment and maintenance of their Java-based IT environment.
N/A
Quickbase
Score 8.6 out of 10
N/A
Quickbase helps users tackle any project, no matter how complex. Quickbase helps customers see, connect and control complex projects. Whether it’s raising a skyscraper or coordinating vaccine rollouts, the no-code software platform allows business users to custom fit solutions to the way they work – using information from across the systems they already have.
$700
per month
Pricing
DHTMLX
Oracle Java SE
Quickbase
Editions & Modules
DHTMLX Gantt Individual - Professional Functionality with Standard Support
$699
one-time fee for 1 developer
DHTMLX Gantt Commercial - Professional Functionality with Premium Support
$1399
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
Enterprise
Full Customizable
per month/billed annually
Business
Starting at $2,200
per month
Team
Started at $700
per month
Offerings
Pricing Offerings
DHTMLX
Oracle Java SE
Quickbase
Free Trial
Yes
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Optional
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.).
—
Quickbase offers three key plans, with feature distinction, simple and consistent entitlements, and a flexible licensing model, giving users the option of either user based or usage based licensing across all 3 plans.
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.
Oracle Java SE is well suited to long-running applications (e.g. servers). Java Swing (UI toolkit) is now rather outdated, lacking support for modern UI features. JavaFX, the potential replacement for Swing, has now been separated out of Java core. Ideally, there would be a path to migrate a large application incrementally from Swing to JavaFX, but due to different threading models and other aspects, it is difficult. At this point, it is probably better to use an embedded web browser (e.g. JxBrowser) to provide a modern UI in HTML/Javascript and keep just the business logic in Java.
I no longer think that Quickbase is the way of the future. They do not fix major bugs in a timely manner, and are releasing basic functionality behind a paywall. I believe that Enterprise Level Tier should be given certain things, like SLAs on Support and up-time. However, as a low-code no-code platform the majority of the accounts, "builders", and users are not going to be able to justify the cost of an Enterprise Tier Plan, and won't be able to use the features that Quickbase continues to advertise.
Commercial Licensing in 2019. Oracle will charge commercial organizations using Java SE for upgrading to the latest bug fixes and updates. Organizations will now need to either limit their implementation of Java SE or may need to drop it altogether.
Slow Performance. Due to the all of the abstraction of the JVM, Java SE programs take much more resources to compile and run compared to Python.
Poor UI appearance on all of the major GUI libraries (Swing, SWT, etc.). Through Android Studio, it is easy to get a native look/feel for Java apps, but when it comes to desktops, the UI is far from acceptable (does not mimic the native OS's look/feel at all).
I'd like to see a link on email notices that take you directly into said notice. On an app that only has 1 or 2 email notices firing, there's no issue. However, we have some tools that are so complex that they have about 20 email notices firing at any given time based on the action users take. In this case, if we have to go in to modify a notice, we have to guess or scroll down the long list of notices to see which one we need to customize. It would be great if Quickbase had the URL of said notice somewhere at the footer of that notice so when Administrators click on it, it takes them into the exact notice they need to update.
When filling out or reviewing a lengthy form, I'd like to see the Save & close button, as well as a Save & next option at the bottom of the form rather than having to scroll back up to the top of those forms just to click on those choices.
For our use-case of QuickBase, there really aren't any other products out there that can offer us the same out-of-the-box solutions they provide to us. We're also so integrated with it in our daily processes that to move away from it abruptly would cause mass chaos, so it's going to be renewed for at least the next several years.
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.
Oracle Java SE provides the new features along with timely security patches. New features like Record patterns and pattern matching for switches are very useful. With every new release of Java, it is getting better. Sequenced collections are also an interesting feature added to Java. With all these new features, backward compatibility is also maintained.
Quick Base has done everything we have asked it to do and then some. Our original goal was to have one system for CRM that encompassed both the sales process and the customer management. We have gone w-a-y beyond that with analytics, project management, system bug logging, and historical effort reporting.
Once we did get Quick Base configured and customized it was reliably available when we needed it. We may have had one or two occasions when the product was inaccessible but those were few. The greatest challenge with its availability was its difficulty with integrating with our systems.
Some of our tables that hold over a million records are starting to perform poorly, with some summaries taking over 20 seconds to load. This may be an indication that it is best to archive old data when reaching large volumes like this.
Java is such a mature product at this point that there is little support from the vendor that is needed. Various sources on the internet, and especially StackOverflow, provide a wealth of knowledge and advice. Areas that may benefit from support is when dealing with complex multithreading issues and security libraries.
If you utilize the community, the support is amazing. Unfortunately, I find their actual support system a bit underwhelming. They don't seem to have a great process for interacting directly with an issue and often sweep significant issues under the rug by categorizing them as "Enhancement" ideas or legacy items.
Quick Base already is having a separate portal of providing training to customers and it is very easy to use and updates as per the new features added in to the application
I was not directly involved with the initial account implementation, only a bystander. For the app I directly implemented for my department only, I wish I had know to create an app diagram first. I don't remember if that was suggested. I think that would be a great help tip tool when a new app is created, to have a page with a check list of what is needed or how to get started. If you are a regular app builder, then you can bypass it or have the ability to turn it off in the app settings.
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.
Chose to go with Java instead of Python or C++ due to the expertise on the ground with the technology, for its ease of integration with our heterogeneous setup of production servers, and for the third party library support which we've found was able to address some challenging aspects of our business problem.
Well, there's a plethora of low-code tools out on the marketplace and, you know, there's a reason that we've decided to partner with QuickBase because it has all the right balance of the ability to integrate with the ability for a citizen developer to create apps successfully. So if you look at something like Zo Ho's low-code offering, for example, yes, there are some similarities there, but they're really dependent on all of their other licensed products to get you where you want to be, where with QuickBase you have the ability to truly create something custom.
It has evolved really well with our company, but there is a hard limit to the table size that has begun to affect us and not let us grow. The table size limit is set at 500 MB and we have had to jump through quite a few hoops to be able to get by.
The different versions make it harder to work with other companies where some use newer versions while some use older versions, costing time to make them compatible.
Licenses are getting to be costly, forcing us to consider OpenJDK as an alternative.
New features take time to learn. When someone starts using them, everyone has to take time to learn.
ROI is HUGE. Our company saved over 3.5 million in one year alone based on developments that year in Quickbase that saved time for many teams
Less user error - implementing automations and standardized workflows has led to less user error as was previously seen by maintaining spreadsheets or Smartsheets
