When FileMaker Go is the right answer, when you genuinely need Swift/SwiftUI, and the branded middle-ground most teams miss - a 2026 guide for UK product and operations leaders.
Updated April 2026 · 10 min read · By Neptune Digital
Clients come to us two ways. Group A turns up saying "we need a native iOS app for our field team - can you scope it?" and we often save them £100,000 by showing them FileMaker Go first. Group B turns up with an existing FileMaker Go deployment asking if they should switch to bespoke native, and occasionally the answer is yes. This guide walks through how to decide.
FileMaker Go is a free Claris-built iOS/iPadOS client, downloaded from the App Store, that runs any Claris FileMaker solution hosted on FileMaker Server or FileMaker Cloud. Conceptually it's like a native viewer for your FileMaker app - but with real native iOS capabilities: camera, barcode / QR scan, signatures, GPS, biometric login, audio recording, NFC (iPhone XS+), offline .fmp12 files, push notifications via MDM.
The important mental model: with FileMaker Go, your FileMaker "back-office" system isthe iOS app. You build a mobile-optimised layout on the server, and it appears on the iPad. You don't write any Swift; you don't submit anything to the App Store; you don't maintain iOS builds when Apple releases iOS 19.
| Dimension | FileMaker Go | Bespoke native iOS (Swift/SwiftUI) |
|---|---|---|
| Typical build cost (UK 2026) | £8,000 – £25,000 | £45,000 – £150,000+ |
| Annual maintenance | Minimal - Claris handles iOS updates | ~20% of build cost/year |
| Time to first working build | Days to weeks | Months |
| UI polish ceiling | Good for internal; obviously enterprise | Pixel-perfect, on-brand |
| Offline support | Yes - local .fmp12 or sync pattern | Yes - with engineering investment |
| Camera / barcode / signature / GPS | Built-in, zero code | Full native control |
| Deep iOS integrations (ARKit, HealthKit, CarPlay, Live Activities) | Not supported | Full support |
| Distribution | Free App Store install + Claris licence | App Store, Apple Business Manager, or enterprise |
| Android option | No (WebDirect in browser only) | Separate Android build or cross-platform |
| Branded app icon / store listing | Only via Claris iOS App SDK (middle ground) | Fully branded |
| Best for | Internal / B2B field workers | Consumer / public-facing apps |
Many teams don't realise there's a branded middle option. Claris ships an iOS App SDK that lets a Claris Partner wrap a FileMaker solution inside a branded iOS shell - your icon, your name, your splash screen - and distribute via your own Apple Developer account (typically via Apple Business Manager for private internal distribution).
You still get the speed and cost advantages of building in FileMaker; you lose the "App Store lists this app as 'FileMaker Go'" brand tax. For enterprise field-worker deployments where the client doesn't want their staff installing a third-party-branded app, this is usually the right call. It adds roughly £3,000–£8,000 to the build and requires an Apple Developer Program enrolment (£79/year or equivalent).
FileMaker Go for the staff side - travel logistics, medical forms, wellness check-ins, kit tracking, event day ops. A bespoke native iOS app for the public-facing fan/supporter app. Different audiences, different tools.
FileMaker Go wrapped via the Claris iOS App SDK with a custom icon, distributed via Apple Business Manager. Technicians see a branded "Acme Engineering" app; the business builds and maintains one solution that serves both the office and the field.
FileMaker Go for the operational side (patient intake, consent, observations, referral forms). Any patient-facing consumer app is usually bespoke native - App Store distribution, brand, integration with HealthKit / NHS login.
Almost always FileMaker Go, usually wrapped via the iOS App SDK. UK data residency matters, offline support matters, the audience is a small number of trained inspectors. Bespoke native is rarely justified.
If the audience is your own staff or B2B partners, start with FileMaker Go - wrap it in the Claris iOS App SDK if branding matters. If the audience is the public, or you genuinely need ARKit / HealthKit / CarPlay, build bespoke native. Most teams who turn up asking for "a custom iOS app" actually want the former and save roughly £60,000–£120,000 by not building the latter.
See also - Is FileMaker still worth using in 2026?, FileMaker vs Airtable (2026), and UK FileMaker Cost Guide.
FileMaker Go is Claris's native iOS/iPadOS client that runs any FileMaker solution hosted on FileMaker Server or FileMaker Cloud. It is a free download from the App Store, requires a Claris-licensed user connection to log in, and turns your FileMaker solution into a native iOS app - with camera, barcode scanner, signatures, GPS, biometric login and offline file support built in. For the majority of field-worker use cases, FileMaker Go eliminates the need to build a separate native iOS app.
Yes. FileMaker Go supports working with local .fmp12 files entirely offline (no server connection required), and for server-hosted solutions it supports an offline/sync pattern where a local file collects records in the field and syncs back to the server when connection is restored. The offline model is less elegant than a bespoke native app would provide, but for 80%+ of field-worker use cases it's good enough and saves you an App Store submission.
Build bespoke native iOS (Swift / SwiftUI) when any of these apply: (1) you need to ship to the public App Store for consumers (FileMaker Go is aimed at your own staff, not consumer distribution), (2) you need deep, tightly coupled iOS integrations like ARKit, HealthKit, CoreML, Live Activities, CarPlay, or advanced Camera APIs, (3) the UI needs to be pixel-perfect and on-brand for a consumer product, or (4) you have iOS engineering capacity already and FileMaker Go's UI will be perceived as too 'enterprise' for your audience. For internal/B2B workforce apps, FileMaker Go is almost always the cheaper and faster answer.
A production-grade bespoke iOS app - Swift / SwiftUI, backed by a real API, App Store submitted, with TestFlight distribution and CI/CD - typically costs £45,000–£150,000 depending on complexity, plus roughly 20% of build cost annually for OS-version maintenance (new iOS releases every year break things). A comparable FileMaker Go build on top of an existing FileMaker server is typically £8,000–£25,000 and carries negligible OS maintenance cost (Claris handles it). The cost gap is the main reason we push back when clients default to 'let's build a native app'.
No - FileMaker Go is iOS/iPadOS only. If you need Android, options are (a) FileMaker WebDirect (browser-based, works on Android but offline is limited and UX is weaker), (b) a thin custom Android app hitting the FileMaker Data API, or (c) dropping FileMaker Go and building a cross-platform native app (React Native / Flutter) over the Data API. For mixed-device UK workforces this is a genuine constraint - and a good reason to at least scope both paths before committing.
No - and Claris doesn't position it that way. FileMaker Go requires a Claris user connection (paid), it's branded Claris/FileMaker in the login and store listing, and the UX is calibrated for internal staff rather than consumer onboarding. For any app intended for public App Store distribution to consumers, you should build native iOS (and almost certainly Android too). For internal workforce / B2B apps, FileMaker Go is not only fine, it's usually the best choice.
Partially. Claris does not support rebranding FileMaker Go itself - the App Store listing, icon and login screen are Claris's. What you can do is use Claris's iOS App SDK to compile your FileMaker solution into a single-purpose iOS app with your own icon, splash screen and name, distributed via your own Apple Developer account (typically via Apple Business Manager for internal distribution). This is how several of our enterprise clients deploy - it gives you the fast-build advantages of FileMaker with a branded app experience for staff.
