Today in APIs: Deeplink Launches API for Better Mobile App Interoperability

Deeplink launches tools to make it easier to jump between mobile apps. Khronos publishes new specification for mapping vision apps for front end processing. Plus: Gigaom to hold event on IoT and automotives, and businesses plea for hackathon to solve U.S./Canada border delays.

Deeplink Creates SDK and API for Mobile Apps

Deeplink has released an SDK and API to allow developers to integrate deep linking to improve user experience and their own revenue stream. Deeplinking means users can tap between apps using links, just like on the links that function on the web.
 
As Sarah Perez reports in Techcrunch, competitors are also after creating that same experience, but Deeplink may well be the first to enable developers to integrate the functionality quickly:

What this means, from a practical standpoint, is the potential for highly personalized applications whose recommendations are customized based on the apps a user has on their phone. For example, a movie app like Fandango (not a Deeplink.me customer, to be clear), could help users book a restaurant after the movie ticketing process was completed. But instead of just pointing to one app that a customer may or may not use, it could allow consumers to query against those you have installed, whether that’s OpenTable, Yelp, Foursquare, UrbanSpoon or others. The search results – e.g. sushi near your location – would come from the apps on your phone, and, when tapped, would launch those apps directly.

This works using a large database that Deeplink has compiled, that includes most of the apps in the app store. Ultimately, the company hopes, this will lead to apps understanding the workflow of the user, and anticipating where she should go next.

Khronos Replaces OpenCV with OPenVX

Khronos, the standards body for OpenGL and other open source tools, is releasing OpenVX for mapping vision apps onto chipsets, optimized for low power situations, principally mobile. Companies announcing support for the new standard include AMD, Nvidia, Cadence, Imagination Technologies, Intel, and Samsung. As Rick Merritt reports in EE Times, the key to improving speed is reducing the load on the CPU, which is especially important for mobile:

The interface lets developers handle front-end processing of computer vision data without waking up a CPU or graphics core. “That enables low-power operation for virtual and augmented reality wearables that want to continuously scan the environment -- a very battery sensitive use case,” said Neil Trevett, president of Khronos Group, in an interview with EE Times.

OpenCX promises to be compatible with the previous OpenCV API that is less power efficient. The efficiency is achieved by breaking operations into steps that can be run serially or in parallel, avoiding the continuous memory round trips of past versions.

API News You Shouldn't Miss

Greg Bates A writer for Programmableweb since 2012, Greg is a freelance writer and a maniacal editor of dissertations and term papers. - Follow me on Google+

Comments