I know, the discussion about runtimes may seem completely outdated, but in light of the latest technical developments, I'm coming back to it once again (probably for the very last time) so that Claris might reconsider it’s decision.
My Status Quo
I have a 4 digit number of customers using a FileMaker Runtime that was last built with FileMaker 18. As we all know, that was the final version supporting runtimes. Technically, everything is based on an outdated foundation – not optimized for Apple Silicon.
Starting next year, Apple will no longer ship Rosetta 2. That means our existing runtimes simply won’t run on newer Macs.
So I’m currently facing a decision:
-
Move to FileMaker SBA → massive price increase for my customers
-
Or rebuild my product from scratch
Experimenting with Claude Code and Swift
Inspired by a thread in the German FileMaker Magazine, I started experimenting with Claude Code – and I’m genuinely amazed by the results.
I’m converting my runtime into a native Swift macOS app with the help of Claude Code. And it works – surprisingly well.
The starting point was a DDR of my solution, followed by splitting the DDR into many small XML files using the MBS Plugin (google “MBS Split DDR”). I don’t understand Swift at all, yet the generated code works flawlessly. Smaller issues or change requests can be handled with simple prompts in Claude Code. If everything continues like this, I see no reason why I shouldn't switch to a native macOS app.
In other words: it has never been easier to migrate away from FileMaker! That should set off alarm bells at Claris!
Why Runtimes were important – and still are
I know the runtime discussion is old, and for many it’s a dead horse that shouldn’t be beaten anymore. But there are still very good reasons why runtimes matter:
-
No recurring license costs
-
Ideal for demo versions
-
Full branding without “FileMaker Pro”
-
Perfect for small, clearly defined solutions
-
Ideal for vertical solutions with many installations
-
Extremely simple distribution
-
Possible distribution via the macOS App Store
-
No psychological barrier for new customers
-
A stepping stone toward real FileMaker licenses in multi-user scenarios
For my target audience, SBA licenses are simply not a viable alternative.
Why Claris Must Act Now
The market has changed. With AI tools, it’s now realistic to rebuild a FileMaker solution as a native app in a relatively short time.
At the same time, there is a growing number of no-code and low-code platforms competing with FileMaker, which increasingly risks being perceived as a dinosaur.
If Claris does not bring back runtimes – in whatever form – many developers will turn their backs on FileMaker.
That would be a massive missed opportunity.
The Opportunity for Claris
Runtimes are not a step backward. They are a strategic addition:
-
Entry point for new developers
-
Incubator for small products that can grow much larger
-
A way to keep many small vendors within the ecosystem
-
Revenue from a market segment that would otherwise disappear
-
Access to new target groups by positioning Claris as the low-code platform for database-driven, cross-platform apps (also for the App Store)
-
Revenue through volume instead of high-priced licenses
-
Presumably little effort for Claris, as existing FileMaker apps only need to be limited in terms of their capabilities (Layout Mode, Network).
Claris is currently positioning itself strongly in the enterprise space. That’s legitimate. But FileMaker has always also been the platform for solo developers and vertical solutions. If this audience disappears, FileMaker loses part of its DNA.
Unfortunately, Claris’ current pricing policy also contributes to discouraging new developers.
Conclusion
An affordable runtime option and reasonably priced licenses would send a strong signal to the community. It would create new opportunities and revenue streams – both for us developers and for Claris.
Otherwise, 2026 may become the year when many developers turn their backs on FileMaker. And that would be a real shame.
What are your thoughts about this?
Disclaimer: This thread was written with the help of AI, as I am not a native speaker, but the thoughts reflect my opinion 100%.