The Hybrid App Advantage
Web UI in a FileMaker shell — and why that's more powerful than it sounds.
What is a hybrid app?
A hybrid app renders modern web UI inside a FileMaker Web Viewer. The web layer handles the interface — rich interactions, beautiful components, responsive layouts — while FileMaker provides the backend: data, security, scripting, and infrastructure.
Think of it like Electron, but better. Slack, VS Code, and Figma are all web apps in a native shell. A ProofKit hybrid app does the same thing — but with a multi-user database, a security model, and a backend included out of the box.
The core idea
Anything a FileMaker script can do
A Web Viewer app can call FileMaker scripts. That means the modern web UI is not trapped in the browser sandbox — it can reach the database, run business logic, generate PDFs, call external APIs, and use the local machine through FileMaker.
You build the interface with web tools. FileMaker remains the secure, scriptable application platform underneath it.
What you inherit for free
By building inside FileMaker, your app gets all of this without writing a single line of infrastructure code:
Security
Privilege sets, user accounts, encrypted data at rest.
A secure backend
FileMaker scripts — no secrets exposed in the browser.
CORS-free network
Access any API without proxy servers or CORS headaches.
File system access
Read and write files on the local machine.
Printing & PDFs
Use FileMaker's built-in PDF engine.
Offline support
Works without a server or internet connection.
Plugin extensibility
Access the full FileMaker plugin SDK.
Faster screens, not just prettier screens
A lot of FileMaker layout behavior is powered by show/hide logic, conditional formatting, filtered portals, sortable portal headers, and unstored calculations. Those patterns work, but they can make the database do expensive work just to draw a screen.
A Web Viewer can move that presentation logic into the browser, where filtering, sorting, conditional rendering, and rich interactions are cheap. The result is often a layout that feels faster and asks less of the FileMaker engine.
Start with one layout
You do not have to rewrite your system to get value from a hybrid app. Replace one FileMaker layout with a Web Viewer experience, keep the same users, data, security, scripts, and deployment model, then expand when the next workflow is ready.
That staged path is the practical advantage: modernize the parts of your app that need a better interface without putting the whole business system at risk.
AI makes migration easier. It does not make it risk-free.
AI coding tools can dramatically reduce the time it takes to move a complex FileMaker solution to a modern web stack. But migration is still migration. You still have to learn new systems, rebuild authentication, reproduce permissions, handle files, replace offline workflows, recreate PDF generation, and operate new infrastructure.
With ProofKit, you do not have to trade all of that working FileMaker capability just to give users the interfaces they want. Keep the platform you know. Modernize the experience on top of it.