You will need FileMaker pro 17 Advanced. To work online you will need a FileMaker 17 server connection. The current beta requires a FM 17 server connection. The final shipping version will not need this if your app is entirely offline.

At present, we support deployment to Android, iOS and Mac. We expect to add Windows and Linux at a later date, also potentially Raspberry Pi if there is sufficient demand.

While you will be able to deploy to Windows, you need a Mac to run the LCFM Native compiler. Depending on demand, we may add a Windows edition at a later date, but this will not be in version 1.

Yes, you need to have a license from FileMaker as well as from us.

Yes, LCFM Native connects seamlessly to the FileMaker servers using the Data API.

A user is anyone who either develops or uses your app. So you might have a team of 3 developers, each of whom is a user, plus 20 named users of the app. You would need a total of 23 user licenses for this app.

Your app could be used by specific people, that you can name. For example, you might sell your app to a Financial Services company, which has 20 people in their accounts department using the app. These are named users. They can change over time, and seats can be unassigned and assigned to a new named user.

Alternatively, your app could be used by anonymous, concurrent users. It might be an app in the iOS App store, for eg a conference schedule, used by large numbers of unknown people, at the same time. These numbers could fluctuate greatly from month to month.

 

If your app is used by fluctuating numbers of concurrent users – don’t worry! Just make your best guess at the peak number you expect at any given time. LCFM Native will work it out for you. The connections will be tracked, and if you have more users than you thought, we’ll let you know and you can purchase more users.

You can run as many solutions through the compiler as you like. If you have more than one developer using LCFM Native to compile apps, then you need more than one compiler.

Yes. Your user packs are specific to a particular app. For example, if you have two apps, one for managing the accounts of a large firm, used by 10 people in the client company, and one for managing the schedule for a conference available in the Google Play store, you will need separate user packs and different user types for each app. Your accounting app needs 10 named users, but your conference app might need 100 concurrent users (depending on how large the conference is). You need to buy 2 separate user packs.

 

 

 

 

A compiler license allows you to compile your solutions an unlimited amount of times. It belongs to one named developer. It comes with 5 users, one of these users will be required for your developer license. 4 of them may be used for other testers of the app or for end users. For any users above that, you will need to purchase a user pack. The compiler license is a set $499, and the user pack pricing fluctuates based on the number required, and the configuration of your solution. See our pricing calculator to generate a personalized quote for your solution/s.

Yes, you can. Note that this is not yet supported in the current beta, but it is coming soon.

We do not offer a demo version, you would need to buy at least the compiler (which comes with 5 free users) to try out your solution. The good news is, during the beta you can request a refund at any time, and our 30 day guarantee will run until 30 days after we are out of beta and version 1 has shipped.

Yes, you do not need to have a connection to use your apps. If you choose a syncing license type for your users, when a connection does become available again, any new data can be synced with the server.

Your solution will look the same on all platforms, except where a native object has been used to give the appropriate native look and feel. For example the date picker on Android looks a bit different to that on iOS or on a Mac.

We will only track the number of users your solution has, using the connection through the Data API. We will not have access to, or store any of your data.

You can choose between online and offline mode, and how often your data is synced. Other than that, it works automatically, you don’t need to worry about it.

No programming expertise, other than your existing FileMaker knowledge is required. All you need to do is drag and drop your existing FileMaker solution into the compiler, choose your layouts and which OS you’d like to deploy to, and LCFM Native does the rest.

Yes! LCFM Native allows you to bypass the need to use the complex FM SDK to create a fully native app, saving you significant amounts of development time.

LCFM Native also lets you access the device’s operating system directly while connecting back to FileMaker Server/Cloud using the Data API without the need to create a complex back end. The Data API is typically a very efficient way to utilize your FileMaker licensing, as each FileMaker “user” includes a generous 2GB month of data transfer which can be used among multiple users.

You will be able to add functionality not supported by FileMaker to your LCFM Native iOS app. LCFM Native provides you with powerful online/offline syncing. All good reasons for using it for your iOS deployment needs.

Not at the moment. We will be looking at this as an option for the future. We will be offering a way to extend the functionality of your app to features not currently supported in FileMaker.

Yes. Our compiler has been tested with many large and complex solutions. Your compilation may take longer than smaller, simpler solutions – however the result will be the same.

That said, we do recommend that if you have a complex solution you test it with each beta so we can be certain that everything works correctly when we ship v1.

We define offline as never connecting to a FileMaker database. Your app can still connect to other web services or databases.