FileMaker Falls BehindPosted by: Editor / Friday, October 26, 2007 – 2:25pm
Dissapointment hits homeWarning: This post started out simply about FileMaker’s Leopard compatibility. But then, it started to take a path towards becoming a rant. I decided to post it anyway, despite my aversion to doing so, because I feel it’s valuable to anyone who is just coming into the world of FileMaker thinking their brand-new FileMaker solution or web site is going to be loved by FileMaker and they’re going to get all kinds of support and love from FMI the company. To be honest, don’t expect much. It all started with the bad news. I was really excited to taste the new features in Leopard for OS X. Then I read this article on Macworld that gave me the bad news. It is, with this post, my sad duty to inform you that FileMaker is not currently compatible with OS X Leopard. What? Are you kidding me? FileMaker is owned by Apple! Yeah, that was my thought too. Then, after reading this article, my distaste for this news was eased a bit. It seems there are two issues which are causing the problems.
These are spelled out in very little detail by FileMaker. Now, this same announcement states that FileMaker is targeting a release for November 19, 2007. I can only guess there’s some hurried programming going on at the headquarters of FMI and who really knows what else might be broken. My only question is. “As an Apple owned subsidiary….[pause]…uh, how did this happen?”. I ask, not because I’m all heartbroken about installing a new version of the OS, and being an early adopter and having to weed through all the issues I’ll eventually resolve by searching MacFixit. Moreover, it’s because I’m not impressed that FileMaker hasn’t been brought into the 21st century with regards to its user interface and interaction. (No ill will towards my friends in the interaction dept. at FMI) The 1980’s happened over 20 years agoDon’t get me wrong, I love what I can do with FileMaker - and how quickly it CAN be done (that’s why I provide the content I do). What I don’t love is the lack of informational features throughout the interface. For example, why can’t you see, at a glance, in Layout mode, what table occurrence a layout is tied to, which table that’s tied to, and any anything else that will prevent me from jumping into the myriad of dialog boxes I have to swim through just to see what is connected to what. If I was leading FileMaker development, I would have ditched the four dialog boxes you have to open just to add a script parameter to a Perform Script script step all in favor of a single window that allows you to accomplish most of your programming efforts. Yeah, we’ve all heard the “Easy-to-use” mantra, and it worked when fewer people used the software, but it’s developers who are developing with FileMaker - even if they’re just starting out as beginning developers, do they really need all the dialog boxes that FileMaker employs? Seriously, if you have a comment about how you enjoy the number of dialog boxes in the application then please publicly flame me below. Let’s all be nice nowOk, so I don’t need to go slamming the market that feeds me, lest I fear a loss of income because FileMaker Inc. decides to stop providing me with information about what’s coming down the pike - Oh…. wait, they don’t do that currently. In fact, I have to tell you that FileMaker is one of the worst companies I have ever heard about (and personally worked with) with regards to supporting and promoting their third party markets - simply for the sake of supporting those companies who support them - with the desired result of reciprocal support for their own market. I guess they probably figure they’ll get it anyway. In fact, let me go so far as to say that FileMaker doesn’t even know how to leverage their third party market. They’re horrible at it. How do I know? Well, I have friends in other markets, who are paraded around by the companies they support. These companies are much larger than FileMaker Inc. and you’d think there was more red tape at them because they are larger. Who are they? Well, one is Adobe the others are smaller, but still much more supportive of their third party market. Here’s a little bit of info that supports my opinions. Did you know that FileMaker, Inc. only lists products, sites or solutions by members who pay an annual fee to be part of their developer programs - no matter how good it is? I know because there is a blank space on this webpage where the link used to read “Magazines”.
It’s not there anymore because I raised the issue and kept pursuing the fact that I didn’t feel I needed to pay to be part of their business program in order to have my quality resource listed - especially when they had a category which was earmarked exactly for my service. (Of course, who am I to say that my website and content is quality? Maybe my Alexa ranking should mean something.) Need more? Try this Google search looking for anything on the FileMaker.com web site that references this site. Nada. Zip. Zero.
I also have a number of friends within the third party FileMaker market and in pretty much every case, Ok, I’ll say 90% of them, they voice their opinions about FileMaker Inc’s support of third parties in a less than favorable light. Even after speaking with Dominique Goupil directly (probably a year or two ago), about the state of affairs with regards to how FileMaker approaches their third party supporting sites, there was no change. It was simply business as usual. I heard ABSOLUTELY nothing about 8.5 or 9 prior to its release - despite the fact that I personally know the folks responsible for PR. This wasn’t always the case. Trying to get pre-release copies of the software is almost unheard of unless you’re MacWorld or some other larger company. I’ve known a good number of people at FileMaker who have tried to make a difference and they’re not working for FileMaker now - myself included. Boil it down for meSo, Matt, did this one piece of news about Leopard compatibility cause you to break down and start this rant about FileMaker Inc and how they operate? Nope. Quite simply, it’s been on my mind for a number of years now. I think FileMaker needs a wake up call. Sure, they’ll always get feedback from users requesting features they think will make FileMaker better. But what will they do when a top FileMaker web site has something to say? My guess. Not much. Every company and the products they provide can be improved. It’s what humans do. They move forward. While FileMaker has added new features to the software it doesn’t quite feel like it’s moved forward as a whole - at least to me. It feels like it’s hobbled along with the addition of some nice features. What other well used applications still use patterns from 1980’s MacPaint, doesn’t support gradients and doesn’t provide OS native interface widgets. What it boils down to is this “FileMaker, are you listening?” So are you giving up on FileMaker?Criticism and open comment about what you feel about how a company operates can be a double-edged sword. You can fear you won’t ever get invited to speak at Devcon because you publish information such as this or that the company won’t license your products out of spite. Or you can feel that your market is deserving of the information that you have to share. They may not like it, but is it true? And who is “they” anyway? It’s people, not companies, who make decisions and maybe there’s someone or multiple people who simply don’t like this website, or even myself, over at FileMaker Inc. What I do know is that it’s the FileMaker market, you, my reader, who is supporting my efforts regarding FileMaker informational resources. I still like the software, what it can do and how it can be used. I’ll always be honest about where FileMaker fits and I won’t shove it into a round hole when I know it’s a square peg. There are plenty of places that need square pegs. The moral of the storyI remember first getting started with FileMaker. You may be where I was in 1991. I was starry-eyed and quite hopeful that the world of FileMaker (more specifically the company) was going to treat me right. In many ways it has. In other ways it’s been disappointing. It turns out that it’s the market itself that has always been there the most - not the company that makes the software. No, I’m not giving up on FileMaker. I’m getting older and wiser and learning to set your expectations low while relishing the highs is the best way to approach anything you do - be it working with FileMaker, raising kids or making a peanut butter sandwich. Much luck, and as always Happy FileMaking! Filed under: opinion
. The reason I have never registered as a developer.
. unhinged said this on Saturday, October 27, 2007 - 11:37pm.
. There are very few areas where people point to Microsoft as an example of good practice, but I have to say that their attitude to their developers shines when compared to that of FileMaker. FileMaker requires examples of your work to be approved in addition to payment of a quite hefty fee before you can be part of the FSA. This attitude I can actually agree with, because high entrance requirements usually lead to better quality developers - or at least motivated developers, which will probably provide better results for the end customers. It is a terrible shame that FMI does not hold its own behaviour to similar standards. The one time I succumbed to asking a question of the company's tech support I received a "We'll get back to you" response. AFAIK that ticket from 2002 is still open; I certainly have not to this day received a solution to the issue. FileMaker Pro is today a product that has fewer and fewer reasons for me to spend time with it or to recommend it to new users. The product changes that have been implemented are almost entirely copied from MS Access in order to "ease" the conversion path for Access users and developers. Having used Access 2000 for the past 18 months, I have to say that a user might possibly benefit but a developer will not. A developer expects certain tools to be available (code respositories, object triggers and preferably the automatic logging of all transactions) and a somewhat familiar event model to be in evidence - I have used FMP since 1996 and I still cannot tell you how a "paused script" interface needs to be built to ensure proper script execution at all times! FMP will probably continue to grow market share at the expense of MS Access, but it seems that FMI is completely failing to recognize that (a) developers provide value for the company by helping to grow the market, and (b) FMP as a product has grown so complex that its learning curve is too steep for the average workgroup member. I would be willing to bet $20 that new users today take longer to hack something together than the new users of, say, version 6. FMI relies on the free community resources to provide tech support and cashes in on the people who want to be recognized as official developers, providing them with minimal extra benefits (warning: opinion based on hearsay evidence from aforementioned free community resources). Why promote a site such as this one when it is a better value proposition that the company's official resources? I think FMI's strategy is part of Apple's strategy - they are building a tool to migrate Windows users to the Mac. At the moment FMI thinks that they can treat the Mac version as a lower priority because most of the userbase is operating under Windows. Ever noticed how much trouble you have when you take a solution developed on a Mac and drop the files onto a Windows box? Ever noticed how the reverse doesn't seem to happen? FMI is working to a particular plan, and the plan is dictated by Apple, and the plan has no room for dissenting voices or modification by people who are outside the cathedral. I am happy enough with FMP as a product, for the uses it is suited to, and I am indebted to everyone in the community who has improved my knowledge by either asking or answering questions (including Dave McKee and Jimmy Jones, who frequent the community areas on their own time - and doesn't that say something about FMI?), and I will continue to develop solutions for others using FMP - but I have already chosen to relegate FMP to the same status as the other tools I use. It is no longer the best of breed that it once was, and I find that a bit sad. At least I can draw inspiration from Bob Cusick. :/ . . Couldn't agree more!.
. hucom said this on Wednesday, October 31, 2007 - 5:27pm.
. I sometimes HATE FileMaker. Yes, that's right: I'm using the word hate. Innovation??? I've been using it since FileMaker Pro 1.0, and I can't believe for what sort of lame updates they are charging us nice chunks of money every year. The latest release was a prime example. SQL, great, but those who don't rely on it get virtually no value for their money. All the improvements are long overdue enhancements other companies wouldn't even dare to make a fuss about. I have nothing against building on established features. Apple is simplistic in their approach to applications and new features. But those are convenient and efficient to use! Tabs... great idea, but it feels like the feature is "alpha". I've never seen a less thought-out and inconvenient implementation of a great idea. Are they even thinking of HOW people are using their stuff? The outdated user interface aggravates me every day I'm working with it. Maybe they're just after the money. If I had the knowledge, I'd develop a competing product with an easy way to migrate existing FM Files. These guys need some serious competition. HELLO FILEMAKER???!!! ***Mat, your site is amazing. I love it. I wish the idiot's over at FIleMaker would listen to you. - sorry to speak plainly. . . Awful, Awful Policy.
. aflgenx said this on Saturday, November 3, 2007 - 5:07am.
. Lol, its funny, they tested both FM 8.5 and 9 on Leopard: FileMaker 8.5 has the exact same issues as FileMaker 9.0 has with Leopard (IWP, Region settings). It's just great how they decide to patch FM 9 and not 8.5 when the additional work would be minimal. @Hucom: "Maybe they're just after the money" ... Hehehe, yeh, that could just be it ;) . . . Give me more dialog boxes!.
. tgantos said this on Thursday, January 31, 2008 - 1:15pm.
. Matt- I am flaming you because I love dialog boxes. My memory is beginning to fail me as an aging 50+ developer I need to have my development platform constantly remind me to give it all the data it needs one item at a time. Give me more inane dialog boxes! Who wants to type their code when you can warm your wrists up by mousing around all day? Builds hand and finger strength too! Smirk... Theo . . Apple Corporate Motto.
. tgantos said this on Thursday, January 31, 2008 - 1:17pm.
. Repeat after me the Apple new hire employee chant... "We shall admit no bug until we fix it, and then only when absolutely necessary..." . |
Be notified!Sign up for any of our notification lists for the quickest notification of new items! FileMaker Reference Tool10 Most Recent Videos
|
Absolute Agreement
I agree with absolutely everything you just said. And what's more I would say that these are the complaints that arise most when it comes to FileMaker - the 80's style GUI tools, a lagging level of usability and extreme lack of support.
I mean honestly, who immediately stops supporting their applications when they release a new version, especially given the cost of said application and the time within which these new versions are released... Further, most companies would not dignify these minor updates with an entirely new version - they would actually just be updates for the software (FileMaker's updates are bug fixes, not updates despite what they may call them and even these don't fix half the bugs). But apparently FileMaker considers any new feature to require a new version - the web viewer and variables with 8.5 .. honestly? They admit with the .5 that just adding a web viewer shouldn't require an entirely new version, but still they charged the full upgrade cost. Further, how the massive issues with FMS 9 slipped by I don't know but the reports of the number of crashes of the CWP engine is frightening - these systems were deployed into live production environments... not to mention they were forced to be deployed because of a time bomb located in the PHP API Beta code that almost no one was aware of.
Nor can I say that I've ever... EVER... been happy with the support that FileMaker provide. I somehow managed to waste 14 support phone calls by calling twice to report really annoying bugs with 8.5 only to be on the phone with those wonderful level 19 support personnel who barely know how to put fields on a layout, let alone help you with any technical issues you may have.
And charging membership costs to have access to white paper's... I mean... seriously?
At least they're finally removing "FM Mobile" from the market... I don't know where they got the nerve to charge what they did for those licenses.
The only reason FileMaker is as good as it is is because we as developers find work arounds to deal with its shortcomings. I like FileMaker, really I do, but sooner or later that ever increasing gap between it and the rest of the market is going to get too large for it to be able to compete, and at that point I think that even those of us who have been with it for a long time will forsake it.
ARGH, end rant.