Why WebViewers?
Why modern web UI inside FileMaker is a strong architecture.
A Web Viewer app lets you replace a FileMaker layout with modern web UI while keeping the FileMaker capabilities that already make the system valuable.
What you gain
- UI freedom: use modern components, charts, grids, calendars, drag-and-drop, and responsive layouts.
- Inherited security: keep FileMaker accounts, privilege sets, and data access rules.
- Scripts as a backend: run business logic in FileMaker instead of exposing secrets in browser code.
- CORS-free requests: let FileMaker scripts call external APIs when the browser cannot.
- File system access: use FileMaker and plug-ins for local machine capabilities.
- Printing and PDFs: keep using FileMaker's print and PDF workflows.
- Staged adoption: replace one workflow before you rewrite anything else.
A useful analogy
Slack, VS Code, and Figma all use web UI in a native shell. A FileMaker hybrid app uses the same broad idea, but the shell includes a multi-user database, security model, scripting engine, and deployment path.
What stays FileMaker
The Web Viewer does not replace your whole solution. Your users, data, security, scripts, and deployment model can remain FileMaker-native while selected screens become modern web experiences.
Next step
Read Architecture to see how the pieces connect.