Before Extensions had a name, before the how it works page, before any of the articles on this site — there was a book I was writing about where software is going. Halfway through, I realized the argument I was making had a direct, immediate implication for the FileMaker owners I've worked with for thirty years. This site is that implication.

What The Last Interface argues.

The short version: the interface layer is being rewritten.

For fifty years, software worked one way. A programmer built menus, buttons, forms, and fields. Users learned where to click, what to type, which screen held which data. The interface was a language the user had to learn.

That is ending. AI as the interface means the user talks — types, speaks, or asks — and the software figures out what they meant. No menus to memorize. No forms to fill in the exact right way. The layer people used to have to learn is going away.

The book is called The Last Interface because it argues that natural language is the last one. Nothing more comes after it, because there is nothing left to reduce.

That's the theory. The book is at last-interface.com — it's free.

What this means for FileMaker.

Is FileMaker dead? No. It's cooked.

It runs the operations of thousands of small and mid-size businesses. It holds decades of institutional knowledge in scripts, calcs, and relationships that would cost a fortune to rebuild. The database part — where the real records live — is fine. It works, and it's yours.

The interface part is dated. FileMaker layouts were designed for a desktop world of trained users. That world still exists inside your office. It does not extend to your warehouse guy on a phone, your traveling salesperson in a hotel room, or your client asking a natural-language question at nine on a Sunday night. Those people are not going to learn a FileMaker layout. They are going to ask, in words, and expect an answer.

The book's argument, applied to FileMaker: you don't need to leave FileMaker to update the interface. You need to add an interface layer that meets people where they are — browser, phone, spoken word — while your FileMaker system keeps the real records underneath.

That is what Extensions is.

Where Extensions comes in.

An Extension is a modern interface layer next to your existing FileMaker system. A dashboard that opens in a browser. A daily brief that arrives by email. A page a customer can ask questions of in plain English. A phone view of what your crew is doing tomorrow.

Underneath, FileMaker keeps running exactly as it does today. The scripts, the calcs, the security, the rules your business runs on — all preserved. What changes is who can reach the system, and how they reach it.

The book's use-case chapters are the theory made real. Chapter seven walks through a lighting and equipment rental company that solved exactly this problem: new screens next to the system they already had, with nothing rebuilt and the staff still in the tool they know. The names are anonymized in the book. The system is real. It's live.

If you read the book and thought "OK, but what does that actually look like for my business" — this is where you find out.

Where to start.

If you want the theory first, The Last Interface is free. It takes about three hours to read and it's the whole framework.

If you want to see the pattern, the how it works page shows it in one diagram, and the capability pages show four specific things you can extend to: when FileMaker gets slow, the daily brief, dashboards, and asking your data questions.

If you're ready to talk about your system, the assessment puts the whole conversation in writing — what you'd get, what it would cost, and whether it makes sense before you commit to anything.

The book explains why the interface layer matters. This site is where you get one built.