![]() ![]() The decision to change the company name to FileMaker back in the day made sense when Claris was forced by Apple to stop work on all the other products (rumour has it that FileMaker Pro remained by the skin of its teeth because of the revenue it generated) and it makes sense to have the company and product names be the same thing. I think this Claris re-branding is at least partially an attempt to create a clean break on the licensing side of things the industry (and parent company Apple!) is using metrics of monthly active users and a new subscription model would make it far easier for Claris to generate that information. ![]() ![]() The backlash has been so strong that some customers have grandfathered license plans going back more than a decade, which adds to the company’s problem. Historically, FileMaker/Claris has always had trouble with defining and implementing licensing changes. Claris Studio is making use of custom web authoring tools and MongoDB and is undergoing MASSIVE development to be ready for prime time - it’s in private beta right now, and the feature set growth in the last six months has been satisfying. The codebase for FileMaker Pro and Claris Pro is going to be exactly the same, but I believe integration with Claris Studio will be enabled in Claris Pro using a connector (same as ODBC). The tech stack for the FileMaker platform continues to include the Draco database engine, the scripting engine and the interface management tools. As a long-time FileMaker developer, I have to say it’s not unusual for the information released by the company to be confusing. ![]()
0 Comments
Leave a Reply. |