In an interesting bit of news this evening, it looks like Google has opened up merchant support to China, allowing developers to distribute free or paid apps, in-app purchases, and subscriptions in over 130 countries.
The news comes in a post to Google's official Android Developers blog, which goes on to explain that Chinese developers distributing paid apps through the Play Store will receive payment via wire transfer to a Chinese bank account in USD.
It's not unusual to see slightly customized builds of Android rolling out to Nexus devices shortly after the release of a new version. It certainly happened a few times with KitKat, and it looks like Lollipop is on track to do the same. As the rush of factory images and OTAs roll out, AOSP is also receiving commits for the new device-specific builds; and Al Sutton was quick to put out changelogs for each version.
We've all seen it happen. A great technology, service, or platform comes out, but without a solid base of users and apps, it fails to gain traction. Google wants to see the Fit API work out, and developers have been called upon to help make that happen. If you know how to write an Android app, and you've got a great idea for something that will get people off the couch and into the gym, you're invited to join the Google Fit Developer Challenge.
Google hasn't had much to say about Android Auto since it previewed the platform back at I/O in June. Now there's some movement as we wait on Android Auto to show up in vehicles. The Google Developers blog has posted an introduction to Android Auto and announced that the final APIs are ready for developers to get to work.
When it comes to software development, there are two very distinct camps on the subject of tools: those who prefer to keep it simple with just a text editor and a compiler, and then those who go straight for a fully-featured IDE with all the bells and whistles. For more than a decade, the undisputed champion of IDEs is Microsoft with its assorted versions of Visual Studio. Having come from years of work on Visual Studio, nothing pained me more than the first (several) times I started up Eclipse.
People all over the world can create apps and get them into the Play Store, where millions of users can potentially download their software. The thing is, not everyone is able to get paid for their work. To charge money for an app, you need to live in one of the supported places. Today seven areas have joined the list. This brings the number up to just over sixty.
Jordan (US Dollars)
Lebanon (Lebanese Pounds)
Oman (US Dollars)
Pakistan (Pakistani Rupees)
Puerto Rico (US Dollars)
Qatar (US Dollars)
Venezuela (US Dollars)
For clarification, residents could already download and pay for content in these areas.
Have you felt the draw to get into app development, but didn't really know how to get started? Google wants to make things a little easier with a brand new guidebook that's meant to get developers on the right path. The Secrets to App Success on Google Play is an 81-page eBook that outlines the process and best practices for developing and submitting your software to the Play Store, and hopefully make some money on it.
This one's for you developer-types. Google has just pushed the Android 5.0 kernel sources for the Nexus 9 and Nexus Player. Head over to the Android Open Source Project (AOSP) and poke around at your leisure. For non developers: a thing happened that is good, but it's not something you personally need to worry your pretty little head over.
Google's developers are notorious for including little jokes and easter eggs throughout all of their products. When your job consists of writing thousands of lines of code and testing obscure bugs, you're going to lose your mind without some kind of outlet. We usually see their sense of humor show up in Google Doodles, easter eggs, and even in the occasional bug report.
This time we're diving straight into the Android SDK to check out a function called isUserAGoat.
Over the last few years, few topics have been more hotly contested by Android users and developers than how SD cards are handled by the OS. Back in February, I discussed some of Google's changes during the transition from Android 2.3 to 4.0, and then how more recent policy changes ultimately led to 3rd-party applications losing most of their access to removable storage. By the time I/O came around, Google acknowledged that KitKat's newly added Storage Access Framework still didn't offer enough range for apps to get their work done.