Claris' FileMaker is presented as a Workplace Innovation Platform, and is used to create a custom app. Manual processes can be automated with Claris FileMaker Pro, and apps can be created to manage contacts, track inventory, organize projects, etc.
$21
per month per user
DHTMLX
Score 8.8 out of 10
N/A
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
Pricing
Claris FileMaker
DHTMLX
Editions & Modules
Platform Subscription
$21
per month per user
Individual desktop license
$594
one-time fee
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
Offerings
Pricing Offerings
Claris FileMaker
DHTMLX
Free Trial
No
Yes
Free/Freemium Version
No
No
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.).
More Pricing Information
Community Pulse
Claris FileMaker
DHTMLX
Features
Claris FileMaker
DHTMLX
Low-Code Development
Comparison of Low-Code Development features of Product A and Product B
If your company is really small, I can understand the need for a product like this. However, I would go for MS Access... FileMaker Pro can not be integrated with other systems (like MS Access can at least be handled by C# for instance, and can be integrated with MS Excel or even SQL server). I'm really not sure in what scenario one would choose for FileMaker Pro. If your application or company grows bigger, you're going to have a problem to move to another environment. Also, the fact that only one person can work with the backend at any given time is a problem in a somewhat larger company.
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.
The relational database management system makes the program highly customizable to fit the needs of any product. You can add a ton of information to each record and update your inventory on a regular basis with an Excel import or manually inside of the record. It has the capability to incorporate barcoding, which can manage your available inventory with ease.
The scripting language allows FileMaker to automatically calculate complex algorithms automatically or generate report outs with the click of a button. This allows for greater UI, especially with active users who are not familiar with writing code. Almost all of our internal data is linked to the FileMaker database
The server license allows many users to update the database in real time, which is handy if your inventory is constantly changing. We have users with Macs, PCs, iPhones and handheld tablets linked to our FileMaker database and they are updating the information constantly throughout the day.
If you invest some time into formatting and scripting the database, there is a high ease of use for users without knowledge of any programming or FileMaker itself.
Developer features need to be beefed up - namely adding the ability to search code for a phrase or keyword and the ability to do the same in the "relationship graph" in the database.
Add ability for users to edit the same table record at the same time by version control.
Allow Filemaker Server to use more than 1 core; currently multi-processing is not supported and it can be tricky to find just the right server to support the application you've built to the fullest capacity.
It it not really up to me but my opinion does have some weight in the decision and the reason I would renew my use FileMaker Pro 8.5 is because I am finally getting used to it! Now that I have been working with the program, tasks have become quicker and projects are getting done faster. File Maker Pro 8.5 really is a versatile tool and I think we are just scratching the surface with it's abilities.
It's almost what it should be after so may years and with Apple's longevity and strength behind it. For people who earn their living based on efficiency I think there are too many developer obstacles that waste time and therefore money.
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.
The forums are great with lots of helpful experts and the staff monitor them to provide help where needed. There have been a couple of unique technical issues I've had to deal with that I haven't been able to get resolved so I chose to score this a 9 instead of a 10.
Suggest you use an iterative R.A.D. or AGILE development approach. (i.e. rather than writing a gigantic spec for a system, then building it). FileMaker facilitates quick prototypes. Developing an example, then allowing users to "try it out" is a snap.
FileMaker is still the quickest way to go from zero to having a minimum viable working solution. Simple solutions can be built in as little as a afternoon of development. It is the only tool I am aware of which allows tech savy end users with domain knowledge to build bespoke apps for their businesses without undertaking professional software development training.
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.
We are a more agile company because of FileMaker. A few of us who are tech-savvy enough to manage the database (but are not professional developers) can make needed adjustments to our database without having to employ an in-house developer or contract with a 3rd party. As our business processes evolve and change, it's easy to update the database to accommodate those changes.