On Wednesday, Google teased developers and enthusiasts by officially announcing Lollipop, but chose to delay the release of anything substantial for another two days. Well, we've waited for the obligatory 48 hours, and the SDK is finally available, just in time for the weekend. (Yay?) Developers can finally abandon the interim SDK and move on to the real thing. There's no more pretending 'L' counts as an API Level, Android 5.0 is officially numbered 21.
Back in June, Google announced Android was destined to gain 64-bit support in the coming L release. A few weeks later, Revision 10 of the Native Development Kit (NDK) was posted with support for the three 64-bit architectures that would be able to run the new version of Android: arm64-v8a, x86_64, and mips64. As we close in on the official release of Android L, Google has updated the NDK to revision 10b and added an emulator image developers can use to prepare their apps to run on devices built with Intel's 64-bit chips.
Whenever we post a story about a new app or game that has had a considerable delay in coming from iOS to Android, we get commenters asking us what took so long, or even saying that they won't download it because of the delay. We get it, and it's no less frustrating on our side. But despite Android's market share and sales dominance, developers continue to prioritize iOS. Various studies and statistical presentations say (with increasing repetition) that this is because people spend more money on the App Store than on the Play Store.
Excitement over products like the Ouya, nVidia's Shield line, and even numerous gamepads proves that gaming on Android has entered the mainstream. Developers have been jumping at the opportunity to build games that work across many of the different operating systems; and thanks to the Cross-Platform SDK, they're able to integrate most of the Play Games services into their products on Windows, Mac, and Linux. Until now, this SDK has lagged behind the SDKs for Android and iOS on one specific feature: real-time multiplayer support.
The other half of Google's Play Store policy changes looks to be going into effect alongside the new in-app purchase price ranges. Developers who have added their addresses to the dev console will now see them posted on the public Play Store page for all to see. This bit of info is in the expanded information section with the changelog and IAP prices. It's currently only showing up in the Android client, but the web store probably won't be far behind.
Though Google officially announced Android Auto back at Google I/O, we didn't get to see much of the car initiative at the show itself. A recent update to the Developer.Android.com page shows off a lot more of the system, primarily in how the usual Android apps on a phone interact with a dash unit in a car or truck. The updated page includes screenshots of the app launcher (such as it is), Google Play Music, and some basic menus.
Developers are understandably upset about the new requirement that they provide a publicly visible address for paid apps in Google Play, but another interesting (and much more positive) tidbit has surfaced in relation to that change. The developer of the GoneMAD Music Player contacted Google to ask about the new policy. In addition to confirming address requirement, Google support says the Play Store will also start listing in-app purchase price ranges.
Google is set to institute a new policy in the Play Store, and it has some developers up in arms. A message in the developer console (seen below) has appeared asking developers to add a physical address to their account profile. For those offering paid apps and in-app purchases, this is mandatory as of September 30th. Failing to do so could result in Mountain View pulling the apps.
If you're a Norwegian Android developer, you might want to consider attending JavaZone, an independent Java programming and development conference being held in Oslo from September 9th through the 11th. If you're not, you can still enjoy this parody trailer for the event posted to the group's YouTube page. If you're at work or in public, heads up: the video below has some mild swearing.
To get all the in-jokes here you'd probably need a programming undergrad degree, a passing knowledge of George R.