It has been almost a month since Google Play services 7.8 began rolling out to users, and as of yesterday, it is in wide release to everybody. A previous blog post by Google discussed the big new feature for developers would be the Nearby Messages API, but it turns out there are a couple of other additions worth checking out. In a new post on the Android Developers blog, Google announced a new Mobile Vision API with the ability to detect the presence, orientation, and some details of faces when they are in frame on an active camera.
Now, Google is taking the feature public. In a post over on its developers blog, the company details ways in which Nearby will make sharing information with someone nearby easier than exchanging account information or scanning QR codes.
IF This Then That, or IFTTT for short, lets you automate the way products and services interact with one another. Want to receive an email every time your camera uploads an image to Dropbox? Go right ahead. Want to adjust the thermostat when your car nears the home? You can do that too.
Now Sony and IFTTT have worked together to produce a new channel using the Lifelog API. The channel lets you integrate the activity tracking you've done from a SmartBand or the Sony app with other services to accomplish all sorts of things. Some of the examples provided include posting a Facebook status every time you take a certain amount of steps, automatically sharing calories burned to Google Drive, and receiving an email summary of your daily Lifelog activity.
Remember that "Voice Access" talk that was supposed to happen at I/O but was removed from the schedule? It turns out that, while it wasn't the full-on in-app voice craziness we had hoped for, Google did have some news about voice interactions to share.
Specifically, with Android M, Google has introduced the Voice Interaction API, which will allow apps to get a better handle on a user's voice-initiated requests. Check out the video below, by the leaders of a sandbox talk at I/O about voice actions.
The new API, as Google Search Developer Advocate Jarek Wilkiewicz explains, shouldn't be confused with custom voice actions.
The current trend with to-do managers is for them to integrate with note-keeping and/or calendars. After all, a task you need to finish before a deadline does deserve its spot in your schedule and a note you're adding may require a reminder and a to-do date. Todoist understands that and is thus expanding on its API, announcing a full-fledged Developer Platform with a global Developer Challenge, and launching integration with Evernote, GitHub, and Google Calendar among others.
First up, the new API and Developer Platform will allow devs to hook their services into Todoist or create extensions for the service, all with the benefits of synchronization and oAuth authentication out of the box.
Like it or not, CyanogenMod is one of the most popular and widely supported custom Android ROMs. With other projects you're lucky to see a handful of devices supported, but CM runs on dozens of phones and tablets. Users of those devices may soon have some new goodies to play with when the CM team releases the new Cyanogen Platform SDK, allowing app developers to integrate with various features in CyanogenMod.
Google Play services 7.3 started rolling out to Android devices a little less than 2 weeks ago, making some small, but much needed changes in the process. It turns out that wasn't the only purpose for that release, as it also brings some cool new capabilities developers can use in their apps. Now that the rollout is finished, Google has released an updated Play Services SDK with new capabilities for Android Wear, Google Fit, and Location Services. There's also an improvement to the GoogleApiClient class to handle situations when APIs aren't available on a given device.
Magnus is back!
We learned last week from an update to the Android Wear app that support for connecting multiple watches – and possibly other devices – had become reality.
Early this month, Google announced a major update to its Play services framework, which brings the version number up to 7.0 and adds several great new APIs. The SDK for this update was held back until the corresponding apk had time to make its way out to Android devices everywhere. The wait is now over, and the SDK is live. Developers are now free to incorporate all of the new APIs into their apps. For a quick summary of the new features in Play services 7.0, check out the DevBytes video below. Fair warning, the video is hosted by Magnus Hyttsen, so make sure you've had your morning coffee.
At South by Southwest, Aparna Chennapragada, Director of Product Management for Google Now offered a glimpse into the future of the feature which has become the heart of the search experience on Android. According to Chennapragada, the company plans to have a full API for Google Now cards ready soon. This will expand on the previously announced pilot program consisting of apps like Pandora, Lyft, and others.
One of the more interesting behind-the-scenes additions in Android 5.1 is a new carrier provisioning API that provides functionality which likely benefits carriers and customers alike. Any time you join a carrier, you get services along with your account, whether it's Play Store billing, visual voicemail, premium subscription services billed to your account, or any number of other things. For as long as Android has existed, the methods used to provision these services on a customer's account have varied widely from carrier to carrier, and there was no standard way of doing it.
While this normally wouldn't be an issue on carrier-branded phones or tablets, what happens when you bring an off-contract AT&T phone over to T-Mobile, or you buy a Nexus phone that doesn't have carrier-specific framework APKs installed?