In a rare (and very amusing) fireside chat between Matias Duarte and Joshua Topolsky, we heard that I/O 2014 might put significantly more attention on great design as a topic. Today, a post on Google's Developer Blog is here to back up that declaration and adds that there will be sessions and workshops geared for designers and developers interested in improving their products. While there still hasn't been an official session list posted, this is surely meant to encourage designers to apply for registration before the window closes on Friday.
"Because the history of computing has taught us is that data will not be contained. Data breaks free. It expands to new media, crashes through barriers; painfully, maybe even dangerously. But, uh, there it is… Data finds a way." - Jeff Goldblum as Jeff Goldblum (Jurassic Gift Shop)
When we last left our favorite removable storage device, OEMs had begun adopting Google’s policy for restricting write access to SD cards.
Developers have certainly made great use of the Alpha and Beta distribution channels in the Play Store since they became available last summer. There was one glaring oversight: developers could only write a single block of text for the "What's New" section. This often led to changelogs that left beta testers in the dark about changes or confusing regular users with promises of new features and fixes that hadn't yet materialized in the stable channel.
Last December, Google announced LiquidFun, a cross-platform physics engine developers could use to create realistic gaming experiences. Now, as a part of Google Developer Day at this year's Game Developers Conference, the company has released version 1.0 out into the wild. It's also provided no shortage of videos demoing what the project is capable of.
When Samsung announced the Gear 2 and the Gear 2 Neo last month, the news came with the confirmation that the company was dropping Android from both devices. Instead, both smart watches are powered by Tizen. This may not mean all that much for consumers in the short term, but it does impact developers. For you, Samsung has just shared the first version of the Tizen SDK aimed at wearables. This is what you need to grab if you intend to build apps for the company's two intelligent wristwatches.
It's no mystery that Google has been poking around wearable gadgets for quite some time. The list of projects seems to keep growing as we hear about rumors of an LG-made smartwatch, another prototype watch designed by Motorola, and of course, Google's own Glass. Earlier today at SXSW, Sundar Pichai took to the stage to announce plans to release a brand new SDK for Android-based wearable devices in about two weeks.
Intel's progress into the Android ecosystem hasn't exactly been earth-shattering. The number of high-end and mid-range smartphones equipped with an ATOM CPU still number in the single digits, making the x86 architecture a fairly low priority for app developers. In addition, Intel's emulator images have always lacked support for the Google APIs, leaving developers without the ability to test common staples like Google Maps or push messaging. Fortunately, that issue was recently rectified with KitKat as Google and Intel have finally shipped an x86 system image with Google API support.
If you're a fan of source code (and who isn't?), you might be excited to know HTC has released the code for Power To Give. The Power To Give initiative was officially announced a few days ago at MWC with its corresponding app in the Play Store. Today, the HTC Dev portal posted a full source drop of the project, including the app and various platform-specific versions of the server code.
The recent release of Google Play Services 4.2 brought with it some exciting additions like the official Cast API and significantly improved support for Google Drive. One of the lesser publicized additions is the official launch of GoogleApiClient, a new component intended to simplify setting up and managing connections to Google's assorted API endpoints. Additionally, there is now support for queuing up read-only queries and a choice of executing calls synchronously or asynchronously.
It was only 3 months ago when we first met the brand new Android Runtime, dubbed ART. In that time it has gained a substantial following by enthusiasts throughout the Android community. Given its "preview" status and warnings from the Android team that ART wasn't ready for the general population, it appeared unlikely that it would officially take the place of Dalvik anytime soon. However, a new commit to the Android Open Source Project (AOSP) is strong evidence that ART may become the default runtime in the next version of Android.