10 Rules for Evaluating Web TWAIN Components – for 2015 and Beyond

In 2011, we published a great article called 10 Rules for Evaluating Web TWAIN Components. It helped many software developers with understanding their scanning project needs and getting perspective to evaluate TWAIN SDKs for web applications.

But, quite a few things have changed since 2011.

Quite a few.

Since 2011, the TWAIN standard has been updated from version 2.1 to version 2.3, with more scanning capabilities supported.

Computer hardware continues getting better and better. You have got more RAM, faster CPU and higher bandwidth. This has allowed software size to grow, to some degree.

On the other hand, software user interfaces have also evolved in this era of HTML5. A 2011 GUI just doesn’t cut it in 2015. Also, software user experience has never been so important. You don’t want “difficult to use” software any more – the software must be powerful AND simple to use. That’s also the direction we push ourselves to improve on Dynamic Web TWAIN. We strive to make it really simple for software developers to integrate into their projects. In fact, using the latest version, software developers only need about 10 lines of code to build a simple scanning web page.

Among all the changes, the most important one comes from a change in web browser technology. NPAPI is now considered to be a legacy technology. As such, Firefox has made it more difficult to use NPAPI by enabling Click to Play for all plugins by default (except the latest Flash version). Chrome takes things one step further: it will completely drop NPAPI support in 2015.BTW, Dynamic Web TWAIN has perfectly coped with this issue by using HTML5 technology.

As you see all these changes, you may be wondering:

“So, TODAY what should we consider when choosing a web TWAIN component?”

The good news is the old 10 rules still work. However, these changes compel some new content to be added. Also, the priority of each rule should be adjusted.

For you convenience, I made the infographic below that updates these 10 golden rules. Please share me any thoughts you might have about it, in the comments section.

Cheers.

Conclusion

Some of the information within the infographic may seem basic, but following those rules will save you a lot of trouble. Among all the rules, you need to especially take into account the technology changes on the web browser side and server side, to make sure your application can function with the latest technology.

So, do you have some other perspective when evaluating a web TWAIN component?

P.S. If you liked this post, check out the one I released on document scanning protocols.

Embed This Image On Your Site (copy code below):

<iframe style="overflow-y: hidden;" src="https://magic.piktochart.com/embed/5543144-10-rules-for-web-twain" width="800" height="2766" frameborder="0" scrolling="no">
</iframe>

OR

<div class="piktowrapper-embed" pikto-uid="5543144-10-rules-for-web-twain" >
    <div class="pikto-canvas-wrap">
        <div class="pikto-canvas"></div>
    </div>
</div>
<script>
    (function(d){
        var js, id="pikto-embed-js", ref=d.getElementsByTagName("script")[0];
        if (d.getElementById(id)) { return;}
        js=d.createElement("script"); js.id=id; js.async=true;
        js.src="https://magic.piktochart.com/assets/embedding/embed.js";
        ref.parentNode.insertBefore(js, ref);
    }(document));
</script>

 

Subscribe Newsletter

Subscribe to our mailing list to get the monthly update.

Subscribename@email.com