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
Power Apps
Score 8.1 out of 10
N/A
PowerApps is a low code / rapid application development product from Microsoft that allows users to quickly build apps.
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.
PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams. PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution
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.
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
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.
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!
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
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.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
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.
Much cheaper, much more customizable, and easier to use. There is not much of a learning curve and the licensing cost is much cheaper. PowerApps does one thing very well, whereas other platforms are mediocre. There is much more customization possible for your in-house workflows that you can build yourself vs using NetSuite engineers to build it for you.
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.
It has given us a focal point for development. We now have the possibility of connecting to mobile and the default SharePoint online interface isn't always easy to manipulate. PowerApps has given us an opportunity to improve our user experience.
An improved user experience has given us a better shot at compliance. When users don't fight the environment, they don't gravitate towards workarounds or non-compliance.
As lists and libraries change, the platform scales pretty well.
Having users with the capability to create their own forms and tools has dialed back the app dev need (there is a balance though) and distributed power to the process architects and people who actually need the solutions in the first place—much more efficient model of service delivery: self-service.
