In a post on the Android Developers Blog earlier today, Google has given us yet another indicator of upcoming changes to the Android platform. When KitKat launches, it will finally introduce a public API for the last remaining functions texting apps could not achieve without diving into private APIs. Developers are often advised to stay away from private APIs since they can change with each new version and may not be kept consistent across different OEMs.
Flash may have died a slow and agonizing death on Android, but it did not depart without leaving its heir apparent. Adobe's lighter-weight successor was built to better handle touchscreen interfaces, lower power processors, and to support applications living independently from a web browser. While the platform hasn't been a high-flying success on Android or iOS, it does play host to a few popular games like Machinarium. Exactly three years and one day after first appearing on the Android Market, Air has been updated to v3.9 and now includes support for multi-threading, background tasks, and xxhdpi icons.
I'll admit it - I tried to avoid signing into apps using Facebook back when doing so first became a thing. I figured the company already had enough information about me, and I didn't want them getting more. Now I wager that consolidating my information is probably no less safe (or unsafe?) than leaving my contact information scattered across many different servers, each maintained by scattered companies of varying size that may or may not exist this time next year.
These days, everyone want a platform and the developers that come with it. In the case of the consumer electronics giant that Samsung has become over the last few years, they've got several platforms, even if their most important one is standing on the shoulders of some giants in Mountain View. To expand the presence of Samsung in the developer community, the company has announced its very first developer conference, currently scheduled for October 27th, 28th, and 29th.
In our review of the Pebble SmartWatch, we only had two complaints about the software: a lack of apps, and a lack of utility. The second point stems from the fact that the Pebble can only receive alerts from your phone, and it can't send information back. Both issues have now been addressed by the Pebble SDK. Developers have been cranking away on watch apps for some time, but the latest SDK update adds AppMessage, a method of implementing bi-directional communication for Pebble.
Heads up, Google, Glass is about to get some serious competition. Recon Instruments, a Canadian technology company known for athlete-focused heads-up display products, is looking to expand into general-purpose HUD technology. The company's prototype device - dubbed Jet - was officially unveiled today, and Recon Instruments hopes to release a retail product by the end of this year.
At first glance, the Jet looks like little more than a pair of sunglasses with an attached LCD screen; you won't be mistaking Recon Instrument's HUD for Google's anytime soon.
Few things attract new users to an app more than the ability to interact with other people; gamers demand multi-player and socialites want instant photo sharing. To ease the burden of exchanging data fluidly, Samsung has released its new Chord SDK to make local peer-to-peer and group communication much easier for developers with little or no networking knowledge. It exposes features similar to Samsung's AllShare SDK, but makes it possible to broadcast data and share files with several devices at once.
For quite some time, we've been hearing about the potential advantages of the Bluetooth Low Energy (BLE) spec, and a seemingly endless list of gadgets that could benefit from it. Unfortunately, while many modern flagship devices are equipped with the necessary hardware, Google has allowed the Android OS to languish without official support for the standard. Most of the top OEMs have built their own proprietary versions for the energy efficient protocol, but until now, only Motorola has freely shared access to its API.
Google recently updated its SDK license terms for the first time in a long while. While most changes are minor, one change has been grabbing quite a few headlines – Google's proclamation that those using the SDK are disallowed from taking "any actions that may cause or result in the fragmentation of Android". Here's the full clause in question: