0 Replies Latest reply on May 1, 2013 9:04 AM by Joe Licari

    SB1 BEst Practices

    Joe Licari

      SB1 Best Practices

       

      Scanning

      •       Scanning with the SB1 smart badge is easy to use. Hold the SB1 in your hand with the top of the device pointed toward a bar code. With your thumb, press the scan button.

      •       The SB1 projects a red rectangular target for positioning over bar codes.

      •       Instead of aiming directly at the barcode (i.e. 90 degrees), it is best to tilt the device and scan at a slight angle to minimize reflection.

      •       Its omni-directional barcode reader allows the user to position this target at any angle – it doesn’t need to align horizontally.

      •       Successful decode distance from the bar code is dependent upon the type of bar code. Generally a distance in the range of 3 to 8 inches works best for most bar codes.

      •       If you have trouble scanning. Place the top of the SB1 against the bar code and pull away until a decode beep is heard.

       

      Usability

      ·         To make a selection on the SB1 touch screen, it’s sometimes best to use your finger nail vs. your full finger, especially for small selections. This is due to the SB1’s highly sensitive resistive touch panel, which also allows the use of gloves.

      ·         Touch the middle of any button on the screen to get the best response. You may find you have to press slightly harder than you would on a consumer smart phone display.

      ·         Any touch on the screen generates a click sound even if it is not on a button or text field. This is normal.

       

      Accessories

      ·         The lanyard is adjustable, and should be adjusted to the shortest length that is comfortable to minimize bouncing or risking the device falling off the J-Hook. 

      o   The J-Hook has been designed for easy one-hand operation to take the SB1 device off for scanning and placing it back when not in use.

      ·         The Belt Holster is designed to be worn on a belt or over the edge of slacks. It can also be used with the Arm Band.

      o   This accessory is designed to protect the SB1 screen – the device screen should face inward when placed in the holster.

      o   Also, the tether is designed to keep the SB1 connected to the employee so he/she does not lose or misplace it, while providing a long enough length to reach the farthest possible scanning points. Note the tether is neither strong enough nor short enough to keep the device from hitting the floor if dropped – that’s not its purpose. 

      o   The SB1 in a belt holster may appear to reduce the loudness of beeper for notifications.  The beeper duration and frequency can be modified if needed (See Programmers Guide)

      Network

      •       Sometimes a performance issue may appear to be due to the SB1 or application, but may actually be a result of a network issue. The SB1 requires high quality, reliable WLAN connectivity between the application server and the SB1.

      •       MTU (Maximum Transmission Unit) settings may impact perceived device performance.

       

      Configuration and Application Development

      •       Use application cache to reduce the amount of time lost on network transaction and application. The files are not downloaded or checked on each page.

      •       Resources on application cache can be found at:

      o   http://diveintohtml5.info/offline.html

      o   http://www.html5rocks.com/en/tutorials/appcache/beginner/

      •       Badge Mode can be disabled if desired.

      •       Beeper Notifications: You can change the beep duration and frequency settings to make the beeper more noticeable. This requires settings in the config.js file. 

      •       Avoid double redirects.

      •       Remove the white space in the javascript files. Use a tool such asyuicompressor.

      o   Go to: http://yui.github.com/yuicompressor/

      •       Put all the sprite images in one image and then slice the image using CSS.

      •       All images should be grayscale png format. Do not use jpg format.

      •       Display a notification on the screen when performing functions that might take some time. This avoids the user from thinking the device locked up.

      •       When the user selects an input box, loads the keyboard and does not enter text, the input box may appear to disappear and the user cannot see it. So that the input box does not disappear,  change the color of the text input box borders to black rather than grey so that it still shows through when the keyboard is closed.

      •       Minimize or avoid frequent page transitions.

      •       Avoid apps that require a lot of keyboard entry.  Instead of pop-up keyboard entry consider using scanning, voice input or selecting on-screen data which may be easier for the user” 

      •       Avoid moving graphics – these will not render well on the E Ink display.

      •       Use large buttons and input boxes for finger friendly usage

      •       Consider a Single Page Architecture (SPA) that uses AJAX to dynamically change contents of the page. This will avoid unnecessary re-processing of Javascript and other resources.

      •       Consider an alternative way of disabling the barcode scanner as noted in this blog instead of using the Scanner.disable() method.

      •       Although any graphic will be rendered on the E Ink display, only 256 shades of grey are used. You may wish to resize/recolor any used images so that the file size is optimized.

      •       Avoid pages that require scrolling. Implement a paging mechanism instead.

      •       Avoid CSS3 properties like gradients, shadows, rgbA transparency, rounded corners.

      •       Use browser developer tools like Chrome Dev tools to detect if your page is performing unnecessary reflows/repaints. Watch this webinar to learn about this topic.