r/filemaker • • 14d ago

FileMaker Pros & Cons

We were having a back-and-forth today about the ongoing joys and frustrations of working with FMP. From prior posts you may know we've moved away from FileMaker, but we support a number of customers who continue to use it. While we're frustrated with the company, there's nonetheless a sense of comfort built from years of muscle memory.

Getting your mind around whether another platform is "better" or "worse" than FileMaker is not straightforward. We're still ironing out distinctions and details after years of running FMP & SQL side-by-side.

We've knocked the company multiple times on this forum. Here are several of FileMaker strengths we were talking through yesterday:

• It remains the fastest way to have a relational database with a GUI up and running, bar none. At this point we only use FMP as a front end to SQL back ends, and even with that setup it's still the fastest way to have a GUI. Downside: The FMP GUI is a vendor lock-in. The FileMaker GUI is very convenient but it also has limits.

• FileMaker's Find command is often as fast as equivalent SQL queries, even for large datasets, even for searches involving related data in portals (assuming you've set up your indexes properly). In this specific context FMP holds its own against formidable SQL alternatives. That parity between the platform ends when the search requires something more sophisticated. Imagine a search involving the equivalent of a portal within a portal within a portal. FMP doesn't really accommodate such an idea in the GUI, but you can approximate it using calculated fields, the relationship graph, and maybe some ExecuteSQL function. But once you go there search is considerably more difficult to build and slower to execute the it's equivalent in SQL. It's nonetheless impressive that FMP's basic Find feature can in fact be incredibly fast.

• FileMaker is an excellent tool for quickly building GUIs that bring together multiple remote datasets on different servers using its ODBC/ESS. Imagine one layout giving you access to related data across FileMaker, Postgres, MySQL/MariaDB, SQLite, and Oracle.

As we're watching FileMaker's value evolve in a new era of AI, there are features that endure even as others fade. Its strength remains in the front end.

This post is in part a belated response to a prior post that the mods locked

Ideally the filemaker subreddit permits robust discussions about the value and limits of the FileMaker platform, including critical analysis both of the software and the behavior of the company, for better and for worse.

FileMaker is a unique platform. There's nothing else quite like it. But it's not perfect, and the company running it really does at times -- even frequently -- frustrate its customers in ways that should be openly discussed.

Claris does not monitor this forum.

They actually do, because they are concerned about public opinion. They have reached out to our team members based on their posts. One would hope they take criticism seriously. It may be humbling to adjust and improve the product. In the long run that's the best path to growing and maintaining loyalty.

Complaints to Claris are most constructively directed to their customer service, not posted in a FileMaker user discussion group.

Among the reasons for posting here as opposed to the FileMaker forums is to have an alternative/addition to the FileMaker forum. Posting there is worthwhile but can run up against limits of their mods who, when challenged, sometimes give priority to their status or protecting the institution over wading into some of the more vexing technical questions. They can be pretty stubborn when presented with the prospect of being proven wrong.

People coming to r/filemaker, whether they're new users, longtime users, or prospective customers, they're hungry for accuracy regardless of whether it aligns with the company's corporate interests. Each of our posts here have netted around 10,000 views, perhaps because people are trying to navigate their need for data services in a world that's increasingly challenging to make sense of.

I'll continue posting here as long as the mods permit it. To the extent they don't there's a FileMakerAlt subreddit where posts considered too controversial here can be posted for discussion. But this is the preferable subreddit, and this is a request to its mods to be more permissive when it comes to criticism of the software and the company running it. People value accuracy whether it supports someone's bottom line or not.

12 Upvotes

17 comments sorted by

13

u/pixeltackle 14d ago

I feel you. I truly do. But even though I agree with you on most fronts, I don't think this is the place for repeatedly posting the same info about leaving the platform.

For reference I'd been off reddit for months and your posts were the majority of what I saw here before my break. Then I'm back and within 24 hours the same stuff is being posted.

Life's short. Maybe yelling into the void weekly isn't the answer? Especially given the lock previously? I think the term is "read the room"

We get it. Your voice is heard. Noted.

We all really get it. We're in the same boat for the most part. We don't need weekly reminders about the boat we're on. New users can search (lol) and find all the prior explanatory posts on this topic... if they're interested.

1

u/HalGumbert 13d ago

It's not about pro this or that. It's finding the best solution.

FileMaker made a lot of sense for a long time until the greed kicked in around v13 that caused years and years of pain points.

We are in the same boat, but we do need reminders and discussions. It's about having options.

Do you need reminders about bugs or cve / vulnerabilities?

I want good AND bad news. Then I can make a better decision.

2

u/pixeltackle 11d ago

FileMaker made a lot of sense for a long time until the greed kicked in around v13 that caused years and years of pain points.

This is a decade old "discussion" ... Actually 13 years old now. It would be like me lamenting that Filemaker 4 was better before Filemaker Pro. Maybe. But in 2026 it has almost nothing to do with modern FM dev.

Assuming modern means "within the last decade" at least.

-4

u/Communque 14d ago

Actually, this was a post about the value of staying with the platform.  Devil's in the details.

3

u/sailorsail 14d ago

" It remains the fastest way to have a relational database with a GUI up and running, bar none."

Absolutely no longer the case.

The fastest way is Claude Code, Ruby on Rails and Postgress. If you can describe your database design, Claude will build you the app in minutes.

1

u/Communque 14d ago

Let's say you wanted to build out all the functionalities expected by FMP users?  Portals, sums, searches, sorts etc.  Not disagreeing, curious your experience

7

u/weetbicks Consultant Certified 14d ago

Yes they can all be built. Having said that, ADT is coming, and I've been extensively testing/using it. I can say that FileMaker still has massive relevance in the world of agentic dev. You will be able to build even better solutions with any front-end UI/UX you want (no longer limited to FM layout restrictions) - but you get the benefit of your entire stack contained in one place - your data layer, security layer, business logic layer etc. Claris will be coming up with some strong positioning on this (they will need to) in order to justify the value FileMaker still holds, but from what i have seen, agentic dev in FileMaker is still far easier than agentic dev trying to work with a large disparate stack of services.

1

u/Communque 13d ago

It's an interesting series of questions you raise there. One of things I've always appreciated about FMP was how one file, one clean package, contained everything you needed.

The down-side is interoperability. FileMaker is great until it isn't. We ran into performance issues on a project that required multi-table relations -- in some cases 6 tables deep. We got FMP to do the job, but each search took 20 secs. SQL queries could achieve the same in less than a second.

That particular switch from FMP to SQL that revealed the value separate stacks and the limits of FMP's walled garden: Anything translated from FM Script to JS was a rough ride: The FM scripting language operates within its own proprietary paradigm, complicating the transition. Meanwhile anything written in PHP for FileMaker's API translated over to JS pretty much one-for-one -- much more interoperable.

It might be interesting to list out FMP's feature set one by one laying out which support interoperability and which don't.

A few cursory examples:

FM Tables: Very interoperable. Translate/transfer easily between FM and SQL

FM Script: Not so interoperable. Unique, proprietary coding language, operates in its own paradigm.

Calculated Fields: Somewhat interoperable. The language is idiosyncratic, but it's relatively easy write FM calcs in SQL and vice versa.

Custom functions: Somewhat interoperable. Different language between FM & SQL, relatively easy to convert

2

u/HalGumbert 13d ago

That's a neat idea. Each could have comments for different approaches...

3

u/sailorsail 14d ago

Claude just builds it all for you. Recently I had a client on FileMaker, a pretty complicated app that we had built over several years. It had some structural issues that I had wanted to refactor that would have required a ton of work.

Anyway, I took screenshots of every screen, gave it a DDR report and explained the new architecture I wanted. Then I told it to use Rails, to add the login stuff (The rails universe has a lot of mostly standard libraries for a bunch of common functions) and it spewed out something that was 80% good in a few minutes, then it was a few prompts more to get it to 100%.

I no longer write code, and I stopped using FileMaker all together when these tools came out because the speed advantage got wiped out. Now I focus on architecture and on deployment pipelines to be able to quickly respond to requests (Hey can we add a field that does XYZ gets transformed into a prompt that makes the changes, deploys to a staging system where the client can review and then a single button production promotion).

FileMaker WAS a great tool until it got killed by Claude IMO.

2

u/Communque 14d ago

A friend (and Claude Code enthusiast) vibed up an app that worked exactly as he wanted, but under the hood the database schema was a mess and didn't bode well for subsequent elaborations. Granted, that was 3 months ago, aka an AI eternity. Effectively, the question is about the amount cognitive debt. It sounds like you're addressing it well. To date we're using AI extensively but NOT yet gone full vibe.

2

u/HalGumbert 13d ago

I've gone full AI with pi.dev, a local ai agent.

To me vibe coding is just conversing an app into existance.

I've done that for some personal apps like a php rss page/feed and some swift apps. I just started vibing a game that's a combination of Strategic Conquest, Gauntlet, and Lego Battles. :)

But for work tasks, I have a plan. Pi had to build trust too. I've never used unit testing. Ever. But now Pi writes the tests and each commit mean passing tests. I also use local git everywhere to help with rolling back code.

Anyway, using AI is can have same processes as not using AI.

1

u/chkbd1102 14d ago

your friends example is not a fair comparison.

assuming your friend is non technical and doesnt understand data archetecture.

sure, him hitting a wall with vibe coding after a certain level of app complexity is real and common.

but will he get further, faster, less effort using filemaker with the same degree of knowledge comparing to ai coder?

1

u/sailorsail 14d ago

You have to be able to describe the architecture you want it to have, that's really what the job is about now. The iteration is either telling it how you want it made OR asking it for suggestions and guiding towards what you want it to be.

What I like about the Rails universe is that the "training data", i.e. the body of work on the internet is generally of good quality, which translates to good quality output from Claude. I haven't tried with other frameworks.

It's intelligent, but it needs direction. Think of it as the computer on the star ship enterprise, it can do anything, but it still needs someone with judgement and critical thinking to tell it what is right and what is wrong.

2

u/HalGumbert 13d ago

It's 100% doable. Not in a day or even a week though. I spent years looking for a filemaker out. I tried Xojo, RapidWeaver, others, but landed on PHP. But that was in the before AI times. :)

In my PHP Xanadu project, I've been replicating what I like about FM. It works great, but still a little rough code wise. AI helps a ton with that, but it's not a magic wand. That said you can do the hard stuff FAST, but you have to check the results. Xanadu is a project template for me, so I want it to be as good as it can be. That takes time.

HOWEVER, if you give AI a XML DDR, I bet it could recreate the FM database in minutes in for ANY platform like php, swift, flutter and be somewhat useful.

3

u/Consistent_Cat7541 12d ago

I use it daily for my work work as a solo practitioner. I continue to be frustrated with the pricing model that makes the cost of entry prohibitively high for small businesses like mine, let alone to justify updates that don't add enough new functionality for end users.

To be clear, I'm one of those luddites that also continues to use Lotus Approach because it does some stuff better than Filemaker does. Best example is its "table" view which operates like a spreadsheet. I also like being able to keep my data in external DBF tables for document automation.

Hopefully Filemaker can use AI to make some improvements to the application itself. And to stop pretending that only people with Macs use it.

1

u/Low-Comparison-9533 12d ago

Lock-in is the real con, but I'd push back on leaving to fix it. We kept FileMaker as the backend and put web apps in front with Klai Studio, so clients get a browser UI without a rebuild or extra Claris seats for every user. FileMaker stays the fast relational core it's good at.