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
IBM Cloud Pak for Applications
Score 7.8 out of 10
N/A
IBM Cloud Pak® for Applications (CP4Apps) is an end-to-end hybrid cloud application platform, providing flexibility for deployments, building new cloud-native applications, refactoring and re-platforming existing applications. Designed to leverage a collection of application runtimes, modernization tools and a Kubernetes container platform to adapt to their landscape needs.
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.
IBM Cloud Pak for Applications is clearly suitable for modernizing the WebSphere runtime from the heavy, complex and expensive WAS-ND, and to a lesser extent WAS-base, to the super simple, fast and lightweight WebSphere Liberty runtime. I guarantee, once you start using Liberty you'll never look back. Enough cannot be said about how awesome Transformation Advisor is. The output analysis it produces, along with the migration plan and associated artifacts, considerably simplifies both the decision-making process surrounding modernization and subsequent implementation. Without TA we would've made bad decisions by blindly picking unsuitable apps for moving from WAS to Liberty. Using the results from TA we've excluded multiple WAS apps from our immediate plans to migrate to Liberty, saving time and effort that probably would have resulted in a failed migration. We recently used Transformation Advisor to help us successfully migrate an app from Tomcat to WebSphere Liberty. We needed to make some changes to the Tomcat app, but TA helped highlight these required changes. Without TA I'm not sure we would have succeeded.
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.
While the licensing is considerably simplified than it used to be, I still find it somewhat confusing. For example, WebSphere Liberty Core has an 8:1 VPC ratio. This is clear when dealing with VMs but it is still not clear to me as to whether we get an 8:1 ratio when running on OpenShift or whether we need to purchase additional OpenShift licenses to support running WebSphere Liberty Core in OpenShift.
Not so much related to IBM Cloud Pak for Applications, but while Transformation Advisor is an indispensable tool to help modernize to the WebSphere Liberty runtime, I wish we could run it against WebSphere Liberty itself. The reason being, we are now using TA as a single repository for our configurations. TA also highlights many potential issues when migrating to Liberty; these issues may also be applicable for apps already running in Liberty, we just don't know it yet.
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.
The usability rating I'm providing is for the development interface - the usability of the application you build is relative to how much effort is put into the application. Filemaker needs to roll out some features that are "modern" sooner rather than later. They do roll out new features every year, but at a slow pace. We generally get 1 new TRULY useful feature every year. They need to step it up some!
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.
Comparing IBM Cloud PAK for Applications against alternatives highlights its distinct advantages. Its robust support for hybrid and multi-cloud environments enables unmatched flexibility in application deployment, crucial for businesses seeking to leverage various cloud services. This contrasts with platforms that may limit their focus to a single-cloud approach or offer restricted multi-cloud capabilities.IBM Cloud PAK's seamless integration with AI and data analytics, particularly through IBM Watson, provides powerful tools for developing AI-driven applications. This integration is a key differentiator from competitors that might not offer as comprehensive AI and analytics tools, allowing businesses to easily incorporate advanced technologies into their applications.Furthermore, IBM Cloud PAK for Applications prioritizes ethical AI development and compliance with regulatory standards, aligning with OpenAI’s guidelines. This commitment is essential for organizations that value responsible AI practices and need to adhere to strict privacy and security regulations.The selection of IBM Cloud PAK for Applications was driven by its holistic approach to application development, offering a blend of flexibility, advanced technological integration, and a commitment to ethical standards, making it a superior choice for businesses focused on innovation while adhering to ethical and legal standards.
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.
We have been able to migrate apps away from the expensive WAS-ND to the more cost-effective WAS-base without throwing away our WAS-ND licenses. With a 1:4 ratio of WAS-ND to WAS-base we've been able to we've been able to save in excess of 75% on licensing charges for these apps.
By having a license model based on VPC ratios (1:4:8 - WAS-ND:WAS-base:Liberty core) we've been able to move away from using license pooling resulting in over-allocating (i.e. wasting) CPU cores for each license pool, to using consolidated license pools hosting a combination of WAS-ND, WAS-base and Liberty-core. This has allowed us to reduce our licensing costs accordingly.
