Tag - FileMaker
For the first time ever, we're splitting a review into two completely different parts, and this is the one for you if you already use this software. Existing users know what it does, you just need to know whether it's worth your time and money upgrading to the latest one. Consequently, we can do this pretty quickly: with certain small exceptions, the answer is yes. Upgrade to FileMaker Pro 15.
This may be a first for us: we're examining a new software release in not one, but two separate reviews. It's not because this is going too long, either. It's because this software is FileMaker Pro 15 and it's less an app, more a whole world. If you are an existing user, then you probably love it -- but you also know that any upgrade has to earn its keep, so you'll be looking for details of what's new. Yet if you've never touched it before, the differences between this and the previous version 14 won't really tell you whether it's worth your time and money. So do this for us, please: if you have never tried FileMaker Pro, carry on reading this; if you're an old hand, read the other review -- that one's for you.
Today FileMaker announced the latest release of its custom app and database platform, FileMaker 15. This upgraded platform improves upon the fundamentals of custom app development with new mobility, automation, integration, ease of use, and security features alongside performance enhancements across the entire product line.
Like every app covered in Developer Insight so far, FileMaker Pro is deeply popular and a very longstanding success -- but in every other way, it is completely different. Most apps are bought by people who need them to do a certain job, but if you buy FileMaker Pro, you're actually buying it in order to then create your own solution to a job or a problem. It is a development tool just as much as it is a consumer one, and that has advantages and disadvantages -- but it also attracts a gigantic degree of loyalty from its users.
It all sounded so easy one week ago when we revealed that we were going to make a Job Book database in FileMaker Pro and for the most part, it has been very easy. We took a deep dive into fields on Wednesday which meant absorbing terms that might be new and using database calculations that –– to us anyway –– felt like Sudoku puzzles to be solved. Otherwise, though, it was a pretty smooth ride from idea to final working database. That's the key thing here: the database is working. It's a real database that we truly are using every day and as we keep saying, the way to learn something is to have a real project to do.
There is one thing we haven't mentioned in this entire project: we're here to make a Job Book database that records our commissions, but it is only useful if we can actually use it. All the planning we did, and then all of yesterday's detail work about fields and records -- what we want to note about the work we do -- is for nothing if we don't use the database. Full disclosure: sometimes we haven't. So, in this chapter, we're making the database not just usable, but pleasant to use, reducing the excuses to not use it.
Previously on this MacNN project, we realized we had a problem, and that a database would be the solution. To our mind, that means a FileMaker Pro solution. It means FileMaker in part because we've used that application in one-man companies and international media ones; it also means that because we've learned how flexible it is.
First, we realized we needed a database. Then, it took about a picosecond to realize that what we need is FileMaker Pro 14. This is a tool for making databases, from simple ones like ours up on to the tools that international corporations use. Whether you're a corporate level user or starting out, though, the steps involved in creating and using a new database are the same -- they're the steps and considerations we're using in this project to build a Job Book database.
We're building a Job Book in FileMaker Pro: a database that we are genuinely using in freelance work to log and do some basic tracking of the commissions we get. Last week we explained what this was about, and why we know it's the way to take a productive deep dive into the very powerful database app. Today we're doing something that might not sound right: we're leaving FileMaker Pro.
FileMaker has launched a new software development kit to create fully native iOS apps, without using the existing FileMaker Go tool. The iOS App SDK can be used with existing FileMaker files to create the standalone database apps for iOS devices, with the release giving developers another way to produce applications using the Apple subsidiary's platform that are potentially faster and more lightweight compared to previous efforts.