How Dynamic Web TWAIN HTML5 Edition Works

Aug 03, 2014

With 72.19% of Dynamic Web TWAIN customers having the requirement of supporting Chrome and Firefox in their application, the importance of Dynamic Web TWAIN HTML5 Edition is clearer than ever.

Start your Free 30-day Trial

Google is dropping support for NPAPI-based plugins

As is well known by now, Google is dropping support for NPAPI-based plugins for its Chrome browser. Many NPAPI plugins have already been dropped. A complete phase out is expected by the end of 2014. In addition, Firefox developers are imposing new security features. With the latest version of Firefox Aurora, a user needs to manually enable a plugin on a site to get it to work.

Reasons such as these are why many of our users are upgrading from our Plugin Edition to HTML 5 Edition add-on.

The APIs of the HTML5 Edition will stay the same as the Plugin Edition

For those that are pondering the switch, it’s important to note the Dynamsoft SDK and add-on working environments are pretty much unchanged. For example, the API list and everything else in the HTML 5 Edition is almost the same as with our Plugin edition. We realized keeping a very similar environment to the Plugin Edition would be important to ease migration.

Similar user experience for your end users

For end users of the HTML5 version, when they visit a scan page for the first time, this is when embedding of the ‘Web TWAIN for Chrome’ component must occur. It’s at this point the browser will prompt the user to install the service. Outside of any updates, this installation is only necessary once.

dynamsoft online demo

After this installation users will be able to perform scanning operations within the browser. They will be able to open local images, edit images, save them to local and network locations, and more.

The migration experience for how end users interact with our HTML5 solution was just as important to us as how developers experience a migration to using our HTML5 SDK add-ons. In a nutshell, we also designed it so your end users experience a straightforward upgrade too.

HTML5 Edition technical mechanism

Still, the technical mechanism of our HTML5 add-on is quite different from the Plugin Edition. Here is an illustration outlining the HTML5 architecture:

While the previous Plugin Edition is a browser extension, the new HTML 5 Edition involves Dynamsoft service. You can see from the illustration there are two core modules in Dynamic Web TWAIN for Chrome. These are:

  • JavaScript Client: this is the Dynamic Web TWAIN JavaScript library. It communicates with the Dynamsoft service. It accepts the operation requests from users and sends them to the service. It also handles the UI display.
  • Dynamsoft Service: this module accepts user operation commands from a JS client and performs scanning and file operations including load/save files from/to a local disk in a separate process.

Extensibility to other browsers and OS

Because Dynamic Web TWAIN HTML5 Edition is built using HTML5 technology, it can be easily extended. This includes to IE® and other HTML5-compatible browsers on Windows. And, it includes mobile platforms such as iOS and Android tablets and phones. Here is a simple illustration of how it might work:

As illustrated, when a client – be it a tablet, phone, or computer – initiates a scanning request, the Dynamsoft service will communicate with a specified scanner to finish the job. Scanned images will be transferred back to the client through the Dynamsoft service.

Image editing, uploading, loading from local are also supported, as well as the barcode reader SDK add-ons.

Try for free

If you have any questions or need assistance in determining a proper Dynamsoft SDK for your image capture development needs, please contact sales support.

Related Resources:

Press release about our new HTML5 Add-On

Details on Chrome NPAPI Phase Out

Subscribe Newsletter

Subscribe to our mailing list to get the monthly update.