For general development, the Concierge SDK provides access to the public APIs for our CC5000-specific value adds. For integration with barcode scanners, DataWedge is the preferred method going forward. While it is possible for DataWedge to be disabled in the event that the integrated barcode scanners are going to remain in HID keyboard mode because they're already deployed, newer devices running 1.2 from the factory will have barcode scanners which are already provisioned to work with DataWedge.

I've attached a snippet of code that shows a method we've used in the past for adding support for DataWedge. We would set up a service with an intent-filter that we could target with a DataWedge profile. The service intents from DataWedge would start the IntentService which would then be responsible for grabbing the scan data and passing it in the format a previously existing service already expects. This allowed us to integrate DataWedge into an application without adding breaking changes in the implicit API of its manifest file. The source code would still work as it did in 1.1.