Follow

How to optimize scanning workflow depending on the use case?

The general rule is the following: 

  1. Low battery consumption is not a key requirement: 

  2. Low battery consumption is a key requirement (and scanner is not used very often):

  3. When needed (not recommended if not really required): 

 

WebSDK 5.X(Legacy)

 

Please note that the destroy method should only be used if needed as it removes all HTML elements added to the page, destroy the internal Scanner and the barcode picker itself; ensuring complete cleanup. This method should be called after you don't plan to use the picker anymore, before the object is automatically cleaned up by JavaScript. The barcode picker shouldn't be used in any way after this call. 
 
We recommend reusing the existing picker and related HTML elements to achieve better loading time. More details can be also found here: https://support.scandit.com/hc/en-us/articles/115003182931-How-can-I-optimize-the-loading-time-of-the-Web-SDK-.  

 

The general rule is the following: 

  1. Low battery consumption is not a key requirement: 

  2. Low battery consumption is a key requirement (and scanner is not used very often):

  3. When needed (not recommended if not really required): 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request