For those of you who are not familiar with WebKit, it is the common core between Safari and Chrome (up until the most recent versions of Chrome that are now running on a WebKit fork known as “Blink”). According to StatCounter, the web traffic analysis tool, WebKit is the most widespread web browser engine in use on the internet – ahead of both the IE and Firefox engines.
This means that integration flows based on WebKit have a very high likelihood of being compatible with the websites in use around the world. For old legacy systems that you wouldn’t expect to work in Chrome or Safari, we recommend that you continue to use our classic browser engine that is IE-compatible. Having both engines in our product gives you the maximum flexibility in integrating with both cutting-edge web applications as well as those legacy applications that still hold important information and functionality, but are no longer updated to support modern browsers.
Making browsers that are created for human interaction controllable by an integration flow isn’t the easiest thing in the world. It often requires a lot of scripting, trial-and-error and can be hard for others to read and maintain.
But we’ve taken our knowledge of how browsers work, including algorithms to determine when the time is right to take the “next step” (clicking a link or entering data into a form) and wrapped the WebKit engine in this logic, making it easy for you as a user to build integration flows using point-and-click development. These flows are quick to create and easy to maintain over time, providing stable Synthetic APIs so data can be rapidly integrated from applications and data sources that do not have APIs.
Authored by: Anne-Sofie Nielsen, Vice President of R&D, Kapow Software – A Kofax Company