It’s easy to forget that FileMaker, Inc., is a wholly owned subsidiary of Apple. The direct successor to Claris, FileMaker has, to a degree that saddens its main product’s many dedicated users, become something of a red-headed stepchild within the Apple universe. In many ways, FileMaker (the database program) is an anomaly in that universe, a throwback to the days when Apple’s software bore the Claris label.
Since 1998, Claris has been FileMaker, Inc., a company so utterly separate from its sole owner that one could easily be forgiven for imagining that the two companies have no connection at all. While you can find reference to FileMaker, Inc., at the Apple Web site if you search for it, it’s not easy to find. In fact, only Bento, Filemaker’s personal database, is available on the Mac App Store while its grown-up stablemates are not. And nowhere has the distance between the two corporations been more clear than on the iPhone.
When Apple unveiled the iOS App Store in 2008, FileMaker devotees were sure that Apple’s very own purveyor of fine database software would be among the first to place products in the App Store. FileMaker, after all, wasn’t a total stranger to the mobile market: FileMaker Mobile provided a solution to Palm and Pocket PC users as early as 2006. But it took the company two years after the opening of the App Store to release FileMaker Go in July 2010. I’ve been using it for some time, and wanted to share my impressions.
FileMaker Go for the iPhone is not an impulse purchase. At $19.99, it’s not the cheapest app in the App Store, and it’s not even the cheapest FileMaker client — FMTouch costs half that amount. And $19.99 gets you only the iPhone version — FileMaker Go for the iPad costs $39.99. (Note: This article focuses on the iPhone app, but the conceptual issues, if fewer of the screen size concerns, are the same.)
FileMaker Go is essentially a FileMaker thin client — data within FileMaker databases can be manipulated quite easily on the iPhone using the onscreen keyboard. You enter fields by tapping them; absent a Tab key, you move between fields by tapping the Next button. Buttons trigger scripts as they do on a desktop machine. Calculations, well, calculate. Overall, the software’s functionality, once a database is open, is quite acceptable.
Where a FileMaker developer will find new challenges is in configuring a database for an iOS device, and, in particular, an iPhone. While a desktop-based FileMaker solution can take advantage of relatively large expanses of screen, an iPhone held in portrait view has a limited available display area. FileMaker’s design guidelines recommend limiting layouts to 312 pixels in width to avoid forcing users to zoom out in order to view an entire layout.
The small iPhone screen means less data is visible, and scrolling lists of related data presented in a portal can be viewed only with difficulty — the scrolling navigation cues that are comfortable on a desktop or laptop computer’s screen don’t scale well to the iPhone’s screen. Therefore, layouts have to be designed carefully, and cunningly scripted sequences of forms become the most practical way of manipulating data. To help with that, FileMaker’s Get(SystemPlatform) and Get(ApplicationVersion) script functions can be called to identify an instance of the database running on FileMaker Go, and the database can then be scripted to switch to a mobile-friendly layout. Compare the top (desktop FileMaker Pro) and bottom (FileMaker Go on the iPhone) screenshots below.
Data structures also need to be prepared quite thoroughly, because once a database has been loaded onto an iPhone, its database schema can’t be changed there. Although records in any FileMaker table can be modified (if the user has the right access privileges), that is the extent to which FileMaker Go can interact with the data. Tables can’t be added or deleted, nor can fields, and relationships between tables cannot be modified. Scripts can be run, but cannot be written or edited. Similarly, any layout can be made accessible to the iPhone (although not all layouts will be suitable), but they cannot be modified on the iPhone.
Databases, therefore, need to be prepared in FileMaker Pro on a desktop computer and then transferred to the iPhone via one of two methods. If a database is shared, either using FileMaker sharing under FileMaker Pro or via FileMaker Server, then FileMaker Go can access it in much the same way that a desktop version of FileMaker Pro would; that is, by using a file-browser interface on the iPhone that offers a list of all available files on a selected server. The major advantage of this method is instant updating — since FileMaker Go is interacting directly with the database on the server, updates made to the data with the iPhone app are automatically updated live on the server, and those updates are then reflected on any other clients that happen to have the database open.
FileMaker Go can access shared databases over a Wi-Fi or a cellular data connection. This means that a salesman on a sales call, for example, can check inventory or the status of an order from his iPhone — provided that he has a decent Internet connection and his company’s database is shared over the Internet, of course.
Databases can also be synced to an iPhone via the Apps tab in iTunes. Databases installed this way reside entirely on the device, not on a server, and so changes made locally stay local until the file is copied back to the computer to which the device syncs.
Layout compromises aside, FileMaker Go does offer a couple of new opportunities for capturing data. Container fields in FileMaker Go databases can contain the same variety of data as their desktop counterparts, but data entry becomes a little more interesting.
Tap a container in Browse mode and, in addition to the obvious Choose From Library option, two new data sources are available. Take Photo enables the user to take a photo — but not a video — with the iPhone’s built-in camera (front or back, if it’s an iPhone 4 or 4S), with a button offering a choice of full, large, medium or small file sizes and resolutions. A third choice, Get Signature, offers a plain white screen with a horizontal (in landscape mode) line labeled “Sign Here.” Sign with your fingertip (or a stylus), and then tap either Clear to try again — it’s not easy to sign legibly with your finger — or Accept to place your signature in the container field. Once a container field is filled, a tap on its contents reveals two additional options, Email and Open.
The ability to use fully scriptable databases on an iPhone offers interesting possibilities beyond simple database manipulation. There is a small degree to which FileMaker Go could be considered a development platform for iOS, offering developers, as it does, the capability to build rich and complex solutions that can then be ported to the iPhone simply by syncing, rather than having to develop from scratch using Objective-C.
Database-like applications have been available on the desktop for some time now, with FileMaker Pro Advanced, née Developer, having the capability to generate stand-alone applications encapsulating the functionality of a database. The significant difference with iOS devices is the fact that stand-alone solutions are not possible — you must be running FileMaker Go on your iPhone or iPad in order to access the database, but that’s not a massive price to pay in order to develop, quickly and quite easily, a custom iOS “app.” FileMaker claims they’re apps; they’re not, of course — they’re documents. They’re rich and complex documents, granted, but they’re still documents.
Unlike Bento, the iOS versions of which are limited to sharing data only with Bento on the Mac, FileMaker Go is a solution many FileMaker users have been waiting for since the day Steve Jobs announced third-party apps on the iPhone. (For more about Bento, see the various articles TidBITS has published about the software.) Despite the inevitable layout and design compromises that the small size of the iPhone imposes on the FileMaker developer, FileMaker Go for the iPhone is a solid piece of software that integrates well with the existing FileMaker universe. Why Apple keeps it at arm’s length remains a mystery.
[Steve McCabe is a Mac consultant, tech writer, and physics teacher in New Zealand. He writes about his adventures in New Zealand, he blogs about technology, and he has just finished rebuilding his personal Web site.]