You’ll want many of these iOS apps to work offline–you’ll want them to be able to sync offline changes with data on your FileMaker Server–and we’re thrilled to let you know that GoZync just works with bound iOS apps.

This means you can bind your app just once, and then keep delivering new versions to your users.īecause GoZync is transactional, it knows if all your mobile changes have been synced to the server and will thus only let users update (replace) their local files once they’ve synced all their changes. That’s an update process you can trust. The first question a lot of developers are asking is “ how can I update my solution once I’ve distributed it through test flight or through the app store?” We know that’s important as you’re always adding features and fixing bugs.įortunately, GoZync has always been able to update mobile solutions and can update the business logic and interface files inside an iOS SDK app once it’s been distributed. GoZync adds in-app updates to native iOS apps

For a great FAQ on the SDK, see Todd’s excellent post here: iOS SDK FAQ Why This Matters to You… 1. frowns on this.īut what if you don’t have an app you want to publish widely? Does this SDK do anything for regular developers managing a FileMaker Go app for their mobile workforce? It does. And it makes GoZync more important than ever in syncing and updating files you’ve already distributed. This means that developers can bind their FileMaker Go solutions as native apps and distribute them through several new channels: MDM solutions, test flight, and even in the iOS App Store (providing your app is approved), though FileMaker, Inc. We’re very psyched about the new FileMaker iOS SDK.

The FileMaker iOS SDK – Create Native iOS Apps in FileMaker Go

Filemaker go 19 android