Thank you for your review
Email me when discounted: 
FileMaker Pro is powerful, easy-to-use database software that helps you and your team get any task done faster. Millions of people in business, government, and education use FileMaker Pro to effortlessly manage all their information on Windows, Mac, and the web.

In addition to the more than 30 built-in Starter Solutions that help you manage your important tasks, FileMaker Pro also has more easy-to-use tools to enable you to:

Create custom databases
Create custom databases for your own unique needs. To get started just drag and drop Microsoft Excel data into FileMaker Pro. more...

What's New

Version 13.0.3:
  • Includes OpenSSL 1.0.1g, which is not vulnerable to the Heartbleed bug.
  • In addition, the TLS heartbeat in OpenSSL is disabled, which removes the attack method used by the Heartbleed bug.


  • OS X 10.7 or later
  • FileMaker Pro 13.0.1 or later

Similar Software

Open Comparison
Suggest Other Similar Software
Leave a Review

FileMaker Pro User Discussion

Nobody has reviewed or commented on this app yet. Add your own comment and get a discussion going!

Most Helpful Reviews...

MacUpdate most helpful reviews user icon
from JasonE

Terrible upgrade policy for those that purchase FileMakerPro Advanced. Every time you want to upgrade, you pay the exact same as if you are upgrading to Advanced from Regular. In other words, Regular FileMaker Pro users pay less for more features more...

5 people found this review helpful
Version 12.0.4
Sort by: Time | Smiles
Spank-Me-Baby Member IconReview+1

A number of FileMaker developers can now report that the regular sudden crashes on launching FileMaker Pro 13 and less often (but no less annoying) during development work within the FileMaker application since version 13.0v1 continue to persist in version 13.0v3. A selection of crash reports have revealed the following information:

Crash 1
Application Specific Information: BUG IN LIBDISPATCH: flawed group/semaphore logic.
Crashed Thread: 23 Dispatch queue: com.filemaker.PSConversionHelper.xpcq
0 libdispatch.dylib 0x98bf599f _dispatch_semaphore_signal_slow + 73

Crash 2
Application Specific Information: *** error for object 0x1: Non-aligned pointer being freed.
Thread 0 crashed with X86 Thread State (32-bit)

Crash 3
Application Specific Information: Java information: Exception type: Bus Error (0xa) at pc=0000000081120069.
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

If you experience any of these errors, you must send the crash reports to Apple, Inc. Alternatively, you should not purchase FileMaker Pro 13 until the bugs are fixed and there is a reasonable level of stability in this product.

NOTE FOR FILEMAKER PRO ADVANCED USERS: The runtime database solutions created by the Advanced software appear to be free of these sudden crash bugs. However, the Data Viewer security hole and the GetNthRecord function bug remains in both the runtime solution and the FileMaker Pro.app.

Reply0 replies
Version 13.0.3
Spank-Me-Baby Member IconReview+1

Something worth noting for would be FileMaker users and experienced alike:

If you intend to store and manipulate financial data or anything that requires the use of the GetNthRecord function in a field for displaying numbers or text from the previous record in a list of records, you will notice after the 79th record how the function turns up its toes and decides to show a "?" (would have been amusing if the application showed WTF before the question mark). This anomaly does not exist in FileMaker Pro 12.0 or earlier, but did exist in FileMaker Go 11 or 12 version before it was fixed in FileMaker Go 13. Since porting a number of features from the Go package into FileMaker Pro 13, it seems FileMaker, Inc. has kind of overlooked the error.

FileMaker Pro has been notified in writing to a customer service representative (name withheld for privacy reasons), but whether the email actually reached the software development division of the company is another question altogether. Since sending it in January 2014, the updates for FileMaker Pro 13 have not yet addressed the issue (yawn!).

There are also other issues, including unexpected quits of the application on startup and while assigning scripts to lots of buttons and other things (hoopefully not too bad for other FileMaker users). This is another one I've had the pleasure of sending to FileMaker, Inc. Still getting someone to check FileMaker Pro 13.0.3 to see if the crashes are still prominent.

Although I don't believe in superstition, but given the more bugs I have noticed with version 13 compared to any previous version, one can't help wonder whether FileMaker Pro 13 is unlucky for the wrong reasons. Perhaps FileMaker Pro 14 would be the better way to go when it eventually comes out (Zzzzz....).

The rating I show here is rather generous only because the features provided are reasonable (but still hoping for more if only Apple isn't so protective about its own contacts.app, iTunes.app etc in OSX and the possibility that some FileMaker Pro developers might provide alternative contacts, MP3 player and other solutions at a very low cost or free...)

Reply4 replies
Version 13.0.3

Every database application has bugs. So complaining about bugs here is ludicrous.

Filemaker has been actively updating Filemaker Pro. We are already at version 13.03. Filemaker Pro 13.x is much faster than Filemaker Pro 12.x And it has addressed bugs that were in 12.x.

If you use 4th Dimension, not only does it cost $1000+ more, but you have to spend at least $300+ a year just to get updates. So Filemaker Pro is cheap in comparison. And 4D has a ton of bugs and is more unstable than Filemaker Pro.

ProVUE hasn't updated its database Panorama in 4 years. It has bugs and still looks like it came straight out of the 1980s for its creaking old interface.

Any other database on Mac OS X has to be custom programmed - including SQL databases - so you have to be heavily into database programming to even start developing in those databases. Even then, you are going to run into bugs. And they certainly won't be as simple and easy to use to make sophisticated software as Filemaker Pro.

Your last paragraph is telling. You feel entitled and developers should provide their apps for free. Free doesn't pay the bills. And Free results in poor software and developers that don't care about supporting their software. Free is only good if it is a loss leader to paying the developer in other ways - through ads, through service contracts, etc. Software developers are perfectly free to develop alternatives to Apple's apps. Daylite for example provides a leading industry alternative to Apple's contact and Calendar apps. Daylite is definitely not free.

So if you don't like Filemaker, simply choose another database. And good luck with that.


I hear the point you are making.

In response, I have to say that sure, it is reasonable to expect every software in the world to have bugs. I don't dispute you there. The point I'm making as a developer of FileMaker Pro databases and other developers who use FileMaker Pro is that if a bug is identified and sent to FileMaker, Inc., that the company will make reasonable efforts to fix the bugs. As a case in point, you may wish to look at more bugs from the FileMaker Pro Advanced listing here at MacUpdate, but there is a long-running security bug where the company is fully aware of the issue for more than 2 years since several developers have mentioned it (and the bug was introduced after FileMaker Pro Advanced 10). If the company does not wish to do anything to fix it or at least acknowledge the bug exists and an effort will be made at some point in the future, it is important for all potential users of FileMaker Pro to be aware of those bugs before purchasing. Because I hate to see users waste money on a product that has bugs that won't get fixed and which could well affect the ability of users from achieving what they want from the product. I think it is only fair that people who are deciding to purchase a database product that they know what they are getting themselves into and make sure the product does as it is intended and advertised. And there is a reasonable expectation while using a product of this kind (and any software tool for that matter) that efforts are made to fix bugs when they are identified (I should know, I sell FileMaker database solutions and know of the importance to fix bugs as they come to my attention), otherwise one cannot assume the product is fit for the purpose it is intended if a consumer cannot do what he/she wants to do properly with it.

If you check my post again, I mentioned an example involving financial manipulations in a FileMaker Pro database system and the limitation users are likely to experience from using this product (the GetNthRecord function is particular useful in this regard and just so happens to have a bug introduced in version 13.0v1). It was been mentioned to FileMaker, Inc. in writing since the beginning of the year (and again in April 2014), so I'm curious to know how long it takes to fix it. If FileMaker Inc has no plans to fix it, users need to be aware of it.

I'm not saying at all that FileMaker Pro is crap. Far from it. It has a lot of endearing qualities and potential to be a great application. And it may well be a slightly better product that some other database development platforms as you have mentioned. But this is not to say FileMaker Pro could not be better. In fact, some developers have noticed lapses in the company in recent times in terms of quality control issues and just plain ignoring written requests to fix critical bugs.

This is not good customer service.

But I'm happy to reply again in the near future and say what a wonderful product FileMaker Pro is (just as you have done, and even right down to comparing to other products just to make FileMaker Pro look the better product) as soon as I see the bugs are fixed. In fact, I'll be happy to be the leading spokesperson for the company giving absolutely glowing recommendations about the product and why everyone should use it if I know the product is top quality and I and other developers can see there are no long-running bugs remaining to be fixed. You will have my vote any time.

As for suggesting that I should be entitled to free FileMaker solutions, that was thrown in to see the reaction (and no I don't expect products to be free) because it has come to my attention from another FileMaker developer that Apple, the owner of FileMaker Pro, is trying to compete with FileMaker developers who sell their solutions to consumers (i.e., not for use within organisations or for private use) via the now defunct Bento product (now Apple has figured out a way to give itself the advantage by removing Web Publishing from the lower cost FileMaker Pro product so databases can't easily be displayed in web browsers of iOS mobile products, and is happy to leave a security bug within the Data Viewer to affect the solutions sold by developers to consumers, and introduce other bugs along the way to make it harder for developers to provide quality solutions to consumers). And by pricing Bento lower than key FileMaker solutions, the aim is to lower the price of FileMaker developers' own solutions (even to the point of being free) because developers don't have a hope in hell to compete with Apple's own free OS X applications such as contacts.app and iTunes.app while the company owns FileMaker Pro (there is a purpose for Apple to get consumers to use its own Apple applications e.g. identify users, what they do and have on their computers, what they like, what ideas they come up with and share with their iOS devices etc).

Sure, if users can get around the FileMaker Pro bugs or not likely to need to do things like financial work in a FileMaker database, and are happy to create their own databases for personal use (or perhaps within an organisation as part of their career), fine. I am all in favor of them buying FileMaker Pro.

For me and some other developers, it is about giving people choice and providing a product that shows efforts by the company to be free of bugs once identified by the developers.

I don't think this is too much to ask in this day and age.


I think it is a lot to expect that Filemaker will ever give you an answer when or if they will fix a bug. That has NEVER been their style - particularly with the low price of Filemaker Pro. And developers don't pay Filemaker much.

Bugs are fixed all the time with incremental updates - just like the current 13.0.3 update - the 3rd one since 13.0 was released. When yours is fixed will depend on where it is in line for fixing.

The bugs in Filemaker have always needed to be worked around. In a way, this is good since slow updates means Developers can at least have a STABLE PLATFORM on which to work - bugs and all - for themselves and their customers.

4th Dimension - on the other hand - has an 18 month upgrade schedule, with occasional .x updates, and numerous hot-fix updates (for those who are members paying $400 to $3000+ a year for the privilege). You can expect 4th Dimension to more rapidly fix your bugs because it comes with updates at a very rapid pace. And you can expect 4th Dimension to more rapidly answer your questions - because you are PAYING for it.

However, this aggressively rapid upgrade cycle means as a Developer, the platform is never stable. You have to constantly keep testing your solutions for bugs that crop up in your code as it becomes incompatible with new updates. It costs you, the developer a lot of money to keep up with 4th Dimension's updates. And it costs a lot of money to keep updating your customer's databases to keep up with 4th Dimension's upgrades. Few customers want to pay you for these rapid updates. They just want a stable solution that works for years.

Thus, even those Filemaker has bugs, they are not showstopper bugs. The show stopper bugs are the ones which get priority in updates, the others will take time. The advantage to developers however is that Filemaker is a much more stable platform for them and their customers than 4th Dimension. That is an advantage.


Complaining you say?

Actually, it is not complaining. In the consumer world, we call it informing other consumers (i.e. the users of software) who want to know more about a software product, and need a more comprehensive review of a product beyond the standard "Wow, this is a great product, better than 4th Dimension etc" and that's it. Sometimes people need to know a little more than how great a product might be.

In fact, all products have to take a little bit of the bad as well as the good for a truly balanced review of the products.

But does that mean I'll mention any bug in a product? No. Bugs that get fixed quickly as soon as they get reported by users is not something I care about. What I do mention are bugs that don't get fixed after, say 2 years, as well as no indication through an acknowledgement from the software developer of whether the bug *IS* a bug and will be looked at and fixed within a reasonable amount of time. What's a reasonable amount of time? Is it a year? Is it sooner? Or much later? Only the company (or software developer) that makes the product will know and experience by users of the product over many years will tell you how the company handles bugs.

Long-running bugs, and those that get introduced with no apparent signs it will be fixed are the sorts of things all users contemplating on purchasing FileMaker Pro want to know about, as well as those experienced users who are not yet aware of the issues but need to be aware of them within certain versions of the product, and especially if it is likely to affect their ability to achieve certain things with the product for the long term. It tells users something about the potential long-term limitations of the product for a given version and how far back the limitations have persisted, and even the possibility of perhaps what's happening at FileMaker, Inc. (with its bigger sibling Apple, Inc watching over) and how it approaches the problem of handling bug reports from users (i.e., new database developers as well as experienced ones) and how long things are likely to take with certain bugs (if they ever do get fixed depending on whether there is a reason for Apple to inform FileMaker, Inc. to maintain certain bugs - see my previous response for a likely scenario of what's happening for some developers selling solutions to consumers).

Among those limitations in the software include the rather long-standing issue of the inability of a number of FileMaker developer to make their solutions secure for consumers (such as the Data Viewer problem), and the other involves serious problems in not being able to perform basic financial manipulations in the database (introduced into FileMaker Pro 13, when all previous versions had no such problem, and yet the fix has not arrived).

There are other bugs to report for FileMaker Pro 13 including unexpected quits, showing signs of poor quality control of a product that users are being asked to pay for. Okay, so Apple (like its computers in the early models) have to go through rapid software cycles and, therefore, likely to leave many more bugs in the software.

Well, it is important for users to be aware of this too. This is the perfect place to mention those sorts of bugs for whatever version FileMaker Pro is at to ensure FileMaker, Inc. does get the picture that it needs to get its act together and start fixing bugs that are already on its table for quite some time, and to focus more on quality control issues, and stop getting ahead of itself with adding just a few new features (but not very many new features, and we even lose Web Publishing along the way, which is not exactly a new feature).

You mention how expensive it is to update (and presumably to upgrade) software these days.

Well, how expensive is it when features can be removed, and a few new features ported over from FileMaker Go into FileMaker Pro 13?

As an example, FileMaker developers had to do a survey in 2013 asking a disproportionate number of questions about the Runtime feature of the Advanced software as if Apple was determining how many developers actually use this feature. And if there were any indications of not enough developers deciding to use it, why not drop this feature as well (now that would make it real tough for developers to sell solutions to consumers at a low cost - because their overheads are much lower than Apple's)?

Fortunately the Runtime feature remains in FileMaker Pro 13 Advanced.

If Apple had its way there, we wouldn't have the Runtime feature. Not exactly an improvement to FileMaker Pro. And surely not that expensive to remove features.

But I don't think it takes a lot of time and money to add new features. Even Bento seem to have had more new features than when FileMaker Pro 12 (or 13) came out (and only costs US$50). And now that Bento is defunct, we still don't get those extra features added to FileMaker Pro 13.

I think the reality is that Apple, Inc. and its subsidiary FileMaker, Inc. has so much money that it can afford to choose which aspects to update and what sort of features to add when it wants to. Apple, Inc and ultimately FileMaker, Inc. will select what it is they will fix, add and when, if it helps their bottom-line. Already the OpenSSL bug was fixed very fast before any FileMaker developer ever had a chance to mention it. Clearly important when enough people elsewhere online mention it and Apple saw an opportunity to jump on the bandwagon and look like it is on the ball and making its software secure. All good for extra profit in selling the product. You have to admit, that is extraordinary. But when other equally important bugs don't get fixed for more than 2 years and the company knows about them (and there is no incentive to do anything if they don't see their own profits go up), well, one questions how serious the company is in fixing the bugs that the average developers (i.e., the humble consumer) mention? Is FileMaker, Inc. willing to fix all known bugs, or is it toeing the line of Apple too closely by leaving certain bugs in place to affect some developers who wish to sell solutions to consumers (there is an email from FileMaker, Inc. stating there is no problem in selling to consumers, so why aren't certain long-running bugs getting fixed within reasonable time?)

Sure, I understand your point that software development can potentially be expensive. All those hundreds of employees at FileMaker, Inc. (and what about Apple, Inc?). They all need to be paid. And those executives running the companies have big mortgages to pay when living in those affluent suburbs. You have got to make sure they are all taken care of.

Yet it is amazing how Claris Corporation (the previous and original owners of FileMaker Pro) had no trouble producing extremely stable products and still sold the product at a handsome profit (and did very well selling again to Apple, Inc. when it was time to pack up and leave the business). Yet somehow Apple/FileMaker, Inc., with all its programming might and shear numbers of employees can't seem to get all the bugs quashed (or add significant numbers of new features), and it doesn't matter if developers mention them to FileMaker, Inc.

Things must be getting expensive at Apple/FileMaker, Inc.

If things are really that expensive, then why is it that in the last FileMaker update, we have reached version 13.0v3 suggesting a complete version check over and presumably a whole bunch of bugs fixed? Yet I don't see that many bugs get fixed at all. In fact, only one bug fixed (the OpenSSL security bug). One week's work and your argument suggests this costs a lot of money for which the profit of selling the product to consumers can't cover. If it is as expensive as you say, these software companies should have gone broke by now. Yet I see Apple and FileMaker, Inc are still around after all these years. No, I don't think the updates are that expensive (and especially with the profit they make from the product). Most of the time we see it is the company forging ahead adding just enough features to make people think it is worth paying an upgrade fee and not much more than this. The actual updates themselves are really not that expensive given how quickly FileMaker, Inc. can quash the OpenSSL bug. Then the company asks people to pay for upgrades, and pay they do. A big profit is earned as can be seen by the product's popularity. So there is no excuse in not being able to cover the minimal costs and time to fix bugs. In the case of the bugs I've mentioned, it would be a simple task of copying and pasting the correct, stable and workable code from the previous FileMaker Pro versions into the current version and that's it. Problem fixed. You don't need to be Albert Einstein to figure how to do that one. And how long can that possibly take (assuming their software is well documented)?

I don't think that's the problem. I think it is that Apple is a bit like the rich brat down the street that likes to get its own way all the time, and if it can't, might as well select which bugs to fix to look like it is doing something if it helps to make a bigger profit e.g. make it more secure on the OpenSSL technology (funny that considering the security bug of the Data Viewer is not fixed yet for more than 2 years, suggesting security is a relative concept). Otherwise don't do anything, leave some bugs in place to make it difficult for some other developers to do what they are legally entitled to do (i.e. sell database solutions to consumers), and then focus their time adding just a few more extra features for the next upgrade.

Geez, life is tough at Apple, Inc.

And yes, we all have to pay for the upgrade to get a few extra new features. If it really is that expensive, we should by now be paying double, if not not triple, the cost of the retail price, but we don't. So somehow the company is able to make substantial profits at the current level of pricing for the product to continue developing the product.

I think the bigger problem is whether the company is willing to fix all the bugs.

Looking further, I see in your last paragraph the repeated suggestion that you think I should be entitled to see software for free. I repeat my answer, "No I don't".

Then you gave an example using Daylite to suggest Apple is not being anti-competitive. Well, the company cannot be seen to be discriminating certain software so it has to make it available on the App Store. Furthermore, Apple can't stop people with Xcode to development software it likes, so long as they continue to support the products with each iteration of Apple's OS X to make the software work again - a clue as to how Apple likes to find ways to make it harder for some software to continue surviving for a long time) The other thing I have noticed is that Daylite actively keeps a history of your activities with no option to encrypt the data it transmits to an iOS mobile device prior to displaying the unencrypted data. This means, Apple can still use this tool to indirectly view users' personal information, business confidential data, etc.

With FileMaker databases, you can encrypt the data and with Web Publishing on FileMaker Pro, it would have been a great platform for users to get a secure solution.

Unfortunately Apple does not like this encryption option, which is why some FileMaker developers are limited in what they can do now in FileMaker Pro 13, or else pay a lot more for FileMaker Server (and we all know how much ordinary consumers don't like to pay for this product just to get a more secure FileMaker solution).

If this isn't true, why is it that Apple has never provided encryption as standard to all its OS X and iOS Apple applications where personal information and your ideas for sharing on your devices and with selected individuals or organisations are likely to be produced and kept?

There is a reason for this.

As for Daylite not being free, that was the developer's own decision. And for a long time, not much had changed with this product. Now that version 4 has come out, the developer has decided for the extra effort to revamp the interface and add a few new features that it is worth getting paid. Good for him.

Of if there are others who do provide it for free, that's fine too. They have their reasons. Just as people don't expect Apple to give away certain applications in OS X for people to use. But the company does.

Again, I don't expect to see things free.

As for choosing another database development platform, I am not interested only because I have invested my time and money with FileMaker Pro (and for a number of other developers). But I don't care if Apple decides next week to wind up all development work on FileMaker Pro and says "Bye Bye" to the software. It won't bother me. What I do care, are the people who are wondering whether it is worth spending US$350 up to $US550 on FileMaker Pro and can still achieve what they want over the long-term.

For that, the bugs do have to be fixed, especially the long-running ones. Claims of being too expensive are more excuses (especially for companies making considerable profit from their products). All software developers who sell products and have an expectation to sell more for profit have to make an effort to fix bugs in reasonable time. If not, it means developers are too rich to do anything else but choose what to fix if it helps their bottom-line.

Xco Member IconReview+205

The new Filemaker 13 family is a big step forward, and lays the foundation for yet more improvements in future. I am pleased.

Reply0 replies
Version 13.0.1
Runtime Member IconComment+47

Requirements is 10.7 (sadly)

Reply0 replies
Version 13.0.1
Appledogx Member IconComment+146

Filemaker started out as an affordable, well designed database on the Mac. Filemaker Pro is now fairly well designed, much more powerful, but no longer affordable for personal use. Filemaker killed Bento and left no good alternatives, and an cross-grade price that is too expensive for the majority of Bento users. I've always found Filemaker to be a bit arrogant in dealing with customers, and I've kept up on their new versions enough to see that they offer a little, buy always cost a lot. Too bad their is no Filemaker personal version or something priced to the individual user as it was in its roots. Not all Filemaker users are bigger businesses, but you'd never know it. They act sort of like the Microsoft of Mac databases.

Reply1 reply
Version 13.0.1

Filemaker Pro is cheap compared to the competition.

Filemaker Pro 13 is $329.
4th Dimension 14 is $379 + $100 per year for updates

Filemaker Pro Advanced is $500.
4th Dimension 14 Developer Pro is $1409 + $350 per year for updates.

ProVUE Panorama 6 + image pack costs $314 + $130 per runtime + $30 to use on a second computer + $20 for dictionary. And it hasn't been updated in 4 years. They haven't even started development on Panorama 7.

Any other alternative will cost a lot of time and money and needs heavy database programming experience and will be much more difficult to use. Or the alternatives will have developers that will abandon the software because it won't pay the bills.

The reason there are no good alternatives to Bento is that no other developer or company is willing to spend a lot of time and money into developing a cheap but sophisticated database and support it THE REST OF THEIR LIVES. It is simply too hard and expensive to do that. So complaining gets you nowhere.

Pugwash Member IconReview+48

Since Apple/Filemaker have chosen to abandon Bento (why, I wish I knew??), I have been forced to buy Filemaker. Having worked with it for a week or so now I have to say that despite the large price difference between the two, I find Bento to be far and away more stable. While working with FM I'm finding that I get the spinning beach ball on a frustratingly regular basis while working.
While FM may have more under the hood I preferred working with Bento. Another there is no upgrade pricing from Bento to FM. If you're looking for a Bento substitute, don't leap straight into FM.

Reply0 replies
Version 12.0.4
Xco Member IconComment+205

Dear Apple,

Is Filemaker Pro effectively dead, or merely in drawn out retirement?

When will the core OSX application be brought up to date, so that we can realize its tremendous potential? While iOS is important to us all, many of us still spend most of our working lives using computers - not iPhones, iPods and iPads - to do our real work.

We live and breath in an eco-system in which the Macintosh (or PC) remains at the center. That PC sales are declining reflects not the declining absolute importance of the PC. Rather it reflects a market saturated with powerful devices that readily outpace the needs of the software that generally runs on them: ie, hardware innovation outpaces commercial software innovation by a country mile.

Could Filemaker be a much better, more effective product? Sure it could, with a little bit of imagination and investment.

Would I pay for it: yes, no doubt.

Would others do the same: I have no clue ... (everyone wants software for free these days or at nominal prices)

There in lies the problem I suppose ...

I do hope Apple does move Filemaker's development along ... unfortunately there are no real alternative products to replace it.

Well perhaps 4D?

Kind regards ...

- a 30-year Mac veteran

Reply1 reply
Version 12.0.4

Do you even use FileMaker? There is a LOT going on and their business is still growing. I do work full-time in FileMaker, and there's nothing nearly as good for getting things built quickly with good interfaces and able to deploy to Mac, Windows, and iOS. It's an amazing product, and FileMaker is continuing to get better. They've made some serious changes over the last two versions that lay the groundwork for even more advances going forward.

Xco Member IconComment+205

Dear Apple,

iWork is a terrific package: Keynote, Pages and Numbers.

( Filemaker mentioned below, too )

Yes these have almost fully replaced MS-Office in my work.

But, as so often occurs with Apple, the package progresses little. I am a power-user. So I am less concerned about iWork apps on iOS or the web. I am also an older user. So I recall when MacWrite, MacDraw and MacProject led the field in software innovation. I also recall how Apple let these great products in their time languish and die. Apple was in its heart, after all, a hardware company. The software had done its job. Finito.

And what about Filemaker Pro ( a package with great potential but in need of an overhaul ) which languishes even more?

Will the same fate best the iWorks apps?

If so, who will take up the slack?

The problem is, no investor with $$$ will take up the slack.

Only small under-resourced developers are left. The web-based SAS model, still in so many ways flawed (not to mention inherently insecure), has driven investors out of the desktop application space. And who wants to compete against the likes of Google, Yahoo, SalesForce, Apple, etc in that space?

We live in a world where software development is all too often driven by a mass market, lowest common denominator mentality. Those of us who are power users find our needs are met less and less. There is just not enough net revenue after the less power-needy users are taken care of. So it seems.

I do hope I am proved wrong, and a significant iWorks apps feature upgrade appears this fall. But I am skeptical.

Yours sincerely ...

Reply0 replies
Version 12.0.4
JasonE Member IconReview+112

Terrible upgrade policy for those that purchase FileMakerPro Advanced. Every time you want to upgrade, you pay the exact same as if you are upgrading to Advanced from Regular. In other words, Regular FileMaker Pro users pay less for more features and Advanced users get suckered into upgrading to get their bugs fixed.

FIleMakerPro has a lot of potential, but I agree with others here. They have rested while everything else advances and they still have serious usability issues. Screens are getting wider, yet they moved to the top control bar that wastes the entire top of the screen. They also have a mess for their hot-keys. Only Filemaker goes against what is common place for many keyboard shortcuts.

Also, server is WAY, WAY, WAY overpriced for what it does.

All in all, A+ opportunity, D effort, F Customer service and respect towards developers.

Reply0 replies
Version 12.0.4
Xco Member IconComment+205

Gosh, if only Apple took Filemaker seriously.

Imagine that, we'd have a fully modern relation database creation tool for the "rest of us." The current iPad app does not fit the bill.

We need something on the Mac that also ports readily to the iPad.

There are few choices these days. The fact is, the undue preoccupation with creating web applications (and marketing tools) has decimated investment in useful ad hoc development tools such as Filemaker. It's a real shame, for all of us.

Reply0 replies
Version 12.0.3
user icon+47
Version 13.0.1
user icon+4
Christian Bauer
Version 13.0.1
user icon+130
Version 13.0.1
user icon-1
Version 12.0.3
user icon+84
Version 11.0.3
user icon-1
Version 11.0.3
user icon+14
Version 11.0.3
> 4 24


Current Version (13.x)


Downloads 235,225
Version Downloads 4,563
License Updater
Date 22 Apr 2014
Platform OS X / Intel 32
Price $329.00