Last week James Swinton-Bland, Darryn Campbell & Rabeb Othmani (Bibi) had the privilege to once again represent Zebra at Droidcon London 2019.
Darryn Campbell's blog
Zebra’s series of developer conferences for 2019 has recently concluded with our AppForum event in Las Vegas. During the year we also visited Warsaw, Sydney and Beijing and it was great to meet so many of our developers and discuss ideas, solutions and use cases. One consistent theme across all 4 events was the proliferation of DataWedge as the recommended way of interfacing with the device scanner on our Android devices so I thought it made s
Starting with Android Pie (API level 28), Android will start restricting which APIs your application can call if they are not part of the public API. These restrictions apply whenever an app references a non-SDK interface or attempts to obtain its handle using reflection or JNI but do not affect calls to the EMDK or other third-party APIs.
By Darryn Campbell
Many customers adopting GMS in an enterprise environment will be moving from non-GMS (or AOSP) devices and for many customers making that transition it can be a daunting leap.
October 24th – 25th sees the annual Droidcon London event taking place at the city’s Business Design Centre in Islington. Yet again, Zebra will be sponsoring the event giving us a booth and the opportunity to speak with and get feedback from event attendees. It is always good to meet existing or new developers targeting Zebra hard
Zebra’s GMS Restricted Mode is a device state that provides complete control over which GMS applications and services are available on a Zebra device.
Please be aware that the following article only applies to our devices running the SD660 chipset and some other select devices running other chipsets. If you have DataWedge 7.3 and do not see the Keyevent options page in DataWedge as described then unfortunately this feature is not available on your device.