Hasta La Gadget!

Google’s 2013 developer conference this year didn’t give immediate attention to Glass, at least not at its one and only keynote address – but behind the scenes, development ran deep. Speaking together at a developer chat session centered on “Building Glassware” with what the company calls its Google Mirror API, Jenny Murphy and Alain Vongsouvanh made the case for the future.

Alain Vongsouvanh is a Developer Programs Engineer on Google Glass and the Google Mirror API. Jenny Murphy is also a Developer Programs Engineer for Glass with Google and both of these folks help developers work with the code that brings Google Glass apps to life.

Timeline and Menu

“The Mirror API is one managed through requests made through connections. The main one is a Timeline text card.” This connection is separate from a Gmail connection and separate from a Map connection – it exists as its own element unique to Glass. The most basic setup here is with text and an image.

Customizing these cards are as simple as writing HTML code, but it’s not as all-inclusive as, say, a Chrome web browser-displayed webpage. Google provides a Playground where tests and development can be done, offering here basic templates for developers and allowing them to start from scratch.

This system offers a variety of basic menu items like back and send, and developers are able to create custom menu items like “Complete!” The theme here is simplicity – this development environment is as simple as writing a bit of Java – not something someone off the street will be able to pick up in no time without any knowledge of creating with code, but certainly something that’s simple for a web developer or creator of apps for smart devices.

Contacts

Contacts is a system that a user will share to – just like they are on an Android smartphone. Developers can create a Contact Resource where they’ll have to set an ID that corresponds to a user, users, or a third party app. By default, a shareable element will trigger a list of apps and elements that are compatible with sharing.

Subscriptions and Locations

With Subscriptions, developers will be bringing forward notifications about changes. Instead of you posting to the API, the API will post to the device – input rather than output, so to speak. The developer will specify elements like Collection, User Token, Token Verification, and a Callback URL where needed.

A developer working with Subscriptions in Glass will be working with Timeline as well as Locations – this means they’ve got to account for both how the element is posted and what’s being posted, where it came from and what it’s doing.

Cat Facts

With an extremely simple Glassware app by the name of Cat Facts, Vongsouvanh showed how each of the five different elements in the Mirror API. Below you’ll see his explanation of how it’s not always necessary to work with all five of these bits and pieces, but how even something so simple as this app will be working with more than one.

Google Glass developers make Mirror API simple with Cat Facts is written by Chris Burns & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

This week we were treated to a rather unexpected surprise: Google’s one and only I/O 2013 keynote address revealed a faux-Nexus edition of the Samsung GALAXY S 4. As luck would have it, we caught up with Google’s Vice President of Android Product Management Hugo Barra last night – and he happened to have one of these devices in his pocket. Being the friendly fellow that he is, he have us a brief once-over with the device to show how Nexus-like it really was.

This device is, more or less, the equivalent of a hacked Samsung GALAXY S 4 for AT&T/T-Mobile. Inside you’ll find an unlocked system displaying Android 4.2.2 Jelly Bean without any additions from any carrier or Samsung itself, coming only with the basics issued by Google.

In this device we’re seeing a unique new chapter in Google history. Where previous to this week, any release of a device with as stripped-down and pure as this one pushed by Google was labeled with a Nexus brand name. Here with the Samsung GALAXY S 4, the company has made clear their acceptance of the dominance of Samsung in the Android device-sphere, keeping the GALAXY branding (as they did with the Galaxy Nexus), this time kicking out the Nexus name altogether.

Barra had presented this device on-stage earlier in the day with the following words:

“We continue to be blown away by the hardware that’s coming out of our partners — the HTC One, and the Samsung Galaxy S4. Like this Galaxy S4. There’s something unique about this S4, that’s not available elsewhere. Take a look at my homescreen.

This version of the Samsung Galaxy S4 will be available directly through Google Play, unlocked for both ATT and T-Mobile with LTE support, 16GB internal storage, bootloader unlocked, and it’ll receive prompt system updates with every new release.” – Hugo Barra

What we’ve seen up close is a pure Google experience that’s as swift or swifter than the original GALAXY S 4 with Samsung’s TouchWiz user interface. Barra’s device is likely an early build, but we’re expecting the final product to be essentially the same: home button, 1080p display, Qualcomm Snapdragon 600 quad-core processor and all.

And for those of you wondering: no, he doesn’t use any magical super-secret Google-only apps that only the bosses get. Unless, of course, he was using super-secret Android powers to hide them.

You never know!

The device will be available on June 26th for $649 USD without a contract, compatible with T-Mobile USA and AT&T micro SIM cards, 4G LTE and all. Sound like a value proposition to you? This is one of those situations where we’re guessing developers will find the build to be best – it’s going to be difficult for this device, no matter how neat – to compete with the Nexus 4 already up for $299, also without a contract. That’s hard to argue with.

GALAXY S 4 Nexus edition eyes-on: Hugo Barra’s got it is written by Chris Burns & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

Announcing a product during a major event like Google I/O takes some real courage, especially when you’re revealing a device that’s extremely similar to a product Google is headlining with. That’s what Recon is doing with the Jet, a wearable device that’s drawn instant comparisons to Google Glass. This device works with a virtual widescreen display that sits below the left eye of the wearer and utilizes Android as a basis for its user interface.

Recon Jet is not in a place where it’s able to be sold at the moment – the version we’re having a peek at here at the Google developer event is a pre-production item – but once it’s ready, it’ll be largely the same as what we’re seeing on the inside. Inside this device works with a dual-core mobile processor (the name of which we’re not allowed to speak of quite yet) powering Android 4.2 Jelly Bean with a custom Recon-made user interface over the top.

You’ll control this machine with a miniature touch-sensitive optical pad that sits on the side of the device near the display. Touching this pad as well as swiping left and right, up and down will allow you access to the device’s abilities and settings.

Inside you’ll be working with GPS, wi-fi connectivity for web, Bluetooth 4.0, and ANT+. With ANT+ you’ll be able to connect to a variety of other sports sensors – this device is, after all, made for hardcore sporting enthusiasts, after all. All of this connects to an HD camera the megapixels of which are not yet available as well.

You’ll be working with “gaze detection” for instant access to the machine’s abilities, its display turning off and on when you want or do not want to work with it. Your eyes will decide.

Have a peek at our brief adventure with this device and note that the main aim of revealing this device this week is to find developers that want to work with the SDK for the device in advance of its final release. This machine will be released to the public before the end of the year – we’ve confirmed this specifically once again in-person with Recon – making its appearance fall well before Google Glass hits the streets in a consumer edition. Pricing and release dates will be coming soon.

Recon Jet hands-on is written by Chris Burns & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.

As expected, there was nothing revolutionary about the boatload of upgrades introduced at today’s Google I/O conference, but that doesn’t mean there wasn’t a whole lot of very cool stuff announced.

This weeks’ Google I/O developer conference was the first in several years where the company limited its keynote appearance to a single day. In this single 3-hour session, what Google abstained from speaking about may very well have been more telling than what they did announce – Android, Chrome, Google Services, and everything in-between. Because this now-yearly event is a very special time in which Google’s words mean as much spoken as unspoken, it’s become just as important to discuss what we’ve seen as it is chatting about what we didn’t.

Android OS Updates

As it was last year, so it was expected to be again here in 2013. Google didn’t make an update to Android itself in any grand way, instead issuing updates to services like Google Play for developers on its back end, and updates to Apps for Android, Chrome, and even iOS. While Android 4.3 may still be on the horizon, (coming up quick, you can bet), it’s not been mentioned here on the first day of I/O.

This speaks volumes about Google’s approach with the conference, letting the world know that they’re not about to be pigeon-holed as a company that relies on updates to its operating systems and devices as major announcement fodder while they’ve got perfectly good app releases and service updates to shout about. As Apple’s new operating system update is rumored to be right around the corner, it’s possible that Android is simply fulfilling the suggestions made by Larry Page at the end this one-off keynote:

“Every story I read about Google is about us vs some other company, or something else, and I really don’t find that interesting. We should be building great things that don’t exist. Being negative is not how we make progress.” – Larry Page

Smartphones and Tablets for Developers

In 2012, Google gave away a Samsung Galaxy Nexus smartphone, a Google Nexus 7 tablet, and a Chromebox. The year before, they gave away a mobile hotspot from Verizon as well as a Galaxy Tab 10.1 tablet – and a voucher for one of the first model Chromebooks too. This year developers are being given a Chromebook Pixel, the highest-end device on the market running this operating system. Google was expected to give away an LG-made Nexus 4, a Nexus 10 tablet, and other goodies, but they’ve sent one, single, crystal clear message instead.

Google’s message is that the most important services they’ve got to offer are on Android devices so abundant in the market that they’re inevitably already in developers’ hands OR are on Chrome OS. With the finest delivery vehicle for this operating system in the world thus far, Google is encouraging developers – pushing them, basically – to get Chrome on their radar, and to keep it there.

Google Glass Development

There’ve been no shortages of appearances by Google Glass this week at the Moscone Center, each of these happening with devices made available to developers at Google I/O 2012, shipped in the weeks coming up to this 2013 edition of the event user by user. Though there is a massive showing for Glass on one of two levels of developer-aimed presentations here at I/O 2013, there was no mention of development for Glass in the keynote.

Glass was mentioned by Larry Page in his question and answer session at the end of the keynote, but it certainly wasn’t in any way that was planned beforehand. Glass is not, it seems, at a place where it makes sense for Google to make a big deal of it to developers the same way new services announcements are being pushed. It wouldn’t make a lot of sense to continue to update the public on Glass at this moment either since final market-ready units are still a far way off.

Results

The re-adjustment of the aim of this developer conference is clear. It’s here that Google re-humanizes the way they approach public relations, at least through the developers that make this ecosystem so healthy. While in years past it may have seemed that Google was aiming over the heads of developers, exciting the public with massive consumer-based keynotes to encourage these creators of software and services by default, Google is returning to a more solid spot here in 2013.

What do you think? Did you expect to see anything that didn’t end up appearing in the first and only keynote session of the week? It’s without a doubt a turning point – however subtle – for the company, and it’s exciting – among other things – to see the company’s ability to keep their aims diverse.

What Google DIDN’T announce at I/O 2013 is written by Chris Burns & originally posted on SlashGear.
© 2005 – 2012, SlashGear. All right reserved.