With Edge being the engine used by Google Chrome and a distant cousin to Apple Safari, this makes building cross-platform solutions easier as all the browser engines follow web standards (where IE 11 had to be manually placed into a lackluster “standards” mode). In interactive container fields, PDF files are also displayed using the Microsoft Edge engine so web browser PDF plugins are not required. This provides much better support for web standards enabling JavaScript and CSS to be simplified in web viewers. Microsoft EdgeįileMaker now uses Microsoft Edge (which uses the same Chromium as Google Chrome) to render web content in custom apps instead of Internet Explorer on Windows. fmFlare and fmIgnite require no changes as they are based on FileMaker scripts that automatically benefit from the speed updates of native M1 processing. Get(ApplicationArchitecture) will return arm64 on Macintosh computers with Apple Silicon.įileMaker plug-in support for the M1 chip have been released by most major plugin vendors including 360Works, MonkeyBread, Base Elements, and Actual Technologies. The native M1 FileMaker client alone shows significant gains in several scripting situations. Some performance tests show up to a 200% increase in speed in some operations, and a general speed bump on most functions (which is to be expected when the overhead of machine translation is not present). This change optimizes the FileMaker application for Apple Silicon. Although this may be too fast for the rate of change in larger organizations, it is a welcome change for more agile companies that can take advantage of the new features as quickly as they are released.įileMaker version 19.3 has introduced some significant changes under the hood for developers.

Claris continues to update FileMaker at a faster pace than they used to, releasing new features every 3-4 months.

Filemaker apple m1