Here’s a quick reminder to let you all know that registration has opened for Google I/O 2015. Beginning today (12PM EST) and running through 5PM (PDT) on March 19, you can sign up for a chance to attend the annual developer’s conference.
As was the case last year, this is a no-hassle, no-hurry way to get yourself signed up for the lottery. Tickets are $900 for the two day event; students can register for $300.
Should you not make the cut to attend in person, Google does a wonderful job of broadcasting the keynote and showcasing sessions over the few days. It’s not the same as being there in person, rubbing elbows and all, but it still allows for excellent know-how and insight into the future of Google endeavors.
Google has not yet outlined the schedule of events for the conference however we’re expecting plenty of coverage on Android, Android Wear, Android TV, Android Pay, Chrome OS, and a little bit of everything else. We’re also anxious to see whether Google is ready to pull the trigger on its “Project NOVA” MVNO plans.
If you’re ready to sign up for a chance to attend Google I/O 2015, head to the website between now and March 19 5:00PM PDT.
The post Reminder: Google I/O 2015 registration is now open; closes on March 19 appeared first on AndroidGuys.
Behind closed doors in Mountain View, California, hard working Googlers bring to life all manner of cool services and Android apps. We are seeing one of these new Android apps today, but we are not sure we were supposed to. Introducing Interactive Events by Google.
A first glance, Interactive Events looks like an amazing tool to find and navigate events in your area, presumably providing vendor lists and floor plans for that comic-con or RV convention, you know, whichever you are into. Functionality we’ve seen out of the Google I/O apps of years past. However, Interactive Events does not actually do any of these things at this time.
Whether left in place accidentally, or the slip up was in actually publicly launching the app, Interactive Events immediately greets new installs with Google’s dogfood warning. Apparently, the app is not meant for non-Googlers, you know, not meant for you or I to see or use. As such, we expect an update really soon, or to see the app removed from the Google Play Store.
One thing is for sure, if this somewhat outdated looking app goes live with local event information, we will have plenty more to say about it, but for now, unless you have a valid event code, or event QR Code to scan, we can only explore the first few screens of Interactive Events.
Check out Interactive Events in the Google Play Store for more details. It’s free.
What would you say to a local events calendar and guide from Google – would you use an app like Interactive Events?
Google’s annual developer conference, Google I/O will return to San Francisco on May 28-29. As evidenced by the newly launched website, the two-day event will take place at the familiar Moscone Center West.
Google I/O is for developers—the creative coders who are building what’s next. Together we’ll explore the latest in tech, mobile & beyond.
Registration takes place between March 17 and 19 so there’s enough time for developers and interested attendees to sign up. Google will randomly select applicants from the pool; it matters little when you get online to sign up. Like last year, this should alleviate the strains of racing to register in the mad dash for first come, first served.
Given that the site has just shaken to life there’s no indication as to what developer tracks will take place nor do we know what sessions are on the agenda. We ought to expect those sort of things to surface in the final weeks leading up Google I/O.
(function() var script = document.createElement(‘script’);script.src = ‘https://stacksocial.com/widget.js?publisher=androidguys&type=editorial_post_widget_preferences';script.async = true;var entry = document.getElementsByTagName(‘script’);entry.parentNode.insertBefore(script, entry);)();
At Google I/O the Android and Google community were in awe at Google’s plans for the future. We saw Android L, Material Design, screen mirroring for Chromecast, Android TV and Android Auto. Something else that came out of the Google I/O conference was the long-awaited hope and dream of Android apps on Chrome OS, Chromebooks to be more precise.
After just a few months, Google has started to make that a public reality. The flood gates aren’t opening just yet, but Google is making a select number of apps available. Those apps are Duolingo, Evernote, Sight Words, and Vine. Oddly enough Flipboard was mentioned during Google I/O but didn’t make the initial cut. Moving forward Google will be working with a handful of developers to start moving their apps over and making sure they work as they are supposed too.
“Over the coming months, we’ll be working with a select group of Android developers to add more of your favorite apps so you’ll have a more seamless experience across your Android phone and Chromebook.”
So, does this mean you need some sort of new install, or a special emulator of sorts installed? Nope. Ars Technica plugged Google for a little more detail in terms of how it all runs.
The app code is all running on top of the Chrome platform, specifically inside of Native Client. In this way the ARC (Android Runtime for Chrome) apps run in the same environment as other apps you can download from the Chrome Web Store, even though they are written on top of standard Android APIs. The developers do not need to port or modify their code, though they often choose to improve it to work well with the Chromebook form factor (keyboard, touchpad, optional touchscreen, etc).
Quick and simple. You don’t need anything nor do you need to do anything. All you need to do is grab the app from the Chrome Web Store and use it. You do need to be on Chrome OS version 37 though. Hit up the links below to go grab each of the specific apps from the Chrome Web Store mentioned and let us know what you think.
The post Google brings Android apps to Chrome OS, starts off slow appeared first on AndroidSPIN.
Google announced lots of stuff on this year’s Google I/O. Android Wear was one of the most interesting for sure, considering this is Google’s shot at wearables, only smartwatches for now though. As a part of the I/O, Google briefly announced 3 smartwatches, LG G Watch, Samsung Gear Live and Motorola’s Moto 360. First 2 are already up for sale while the last one will be sometime this summer.
Different people like different things, but I’m gonna go ahead and say Moto 360 is definitely the best designed out of the bunch. That smartwatch looks just beautiful with its circular design. Well, PhoneArena’s source claims that Moto 360 will launch alongside Moto X+1, which is also one of the most expected devices this year. That would mean we’ll see Moto X+1 smartphone launch this summer as well. Oh yeah, the same source says that Moto 360 will be included in Motorola’s Moto Maker, in other words you’ll be able to customize that thing before you buy it. We don’t know how will that work, what exactly would you be able to customize, other than choosing the color of the watch and the bands included in the deal. Either way we spin it, those are some great news.
Are you going to buy one of the already available Android Wear smartwatches or are you going to wait for the Moto 360? If you’re not buying anything feel free to tell us your opinion in general of course.
The post Moto 360 will launch alongside Moto X+1 and will be a part of Moto Maker, report says appeared first on AndroidGuys.
I’m a big proponent of the stock feel, in terms of the UI of any device I use. On my iPhone i jailbreak to get tweaks, and change little things here or there, but never anything major, because I just don’t like it. With the exception of a couple of manufacturers, most Android devices today have some type of OEM Skin over top of the Android OS. Samsung has TouchWiz (don’t get me started), HTC has Sense, and then you have companies like Kyocera or LG who have unnamed skin overlays. I won’t go on a random tangent about TouchWiz, but just know that I despise it, and I’m kind of loving Sense on my HTC One M8, but have been contemplating throwing a GPE ROM on there just for the stock experience on that device.
Fresh off the heels of Google I/O, where Google presented Android Wear, Android Auto, and reintroduced Android TV to the world, questions began springing up left and right. I saw the same question asked by different people all over social media. The question is, will OEM skins be used on these new platforms that Google has announced. This got me thinking a bit. Will Samsung really try and do something horrific with Android TV? What would happen to an OEM skin in any of the Android Auto participants?
Thankfully, Google has come out and stated that OEM skins will not be allowed for Android Wear, Auto, or TV. This has me, and many others rejoicing. The biggest issue that I have is the same issue that I have with TouchWiz. If I purchase an Android TV, or in the future, Android TV is built into whatever TV I’m purchasing, what is going to happen to the Android UI? How bad will it become? Yes, I know I’m being pessimistic, and someone could come out and build something great to go over the Android UI, but I don’t think it’s necessary, and I wouldn’t want to take the chance.
Google’s engineering director, David Burke, in an interview with Ars Technica, stated the following about Android TV specifically:
“The UI is more part of the product in this case. We want to just have a very consistent user experience, so if you have one TV in one room and another TV in another room and they both say Android TV, we want them to work the same and look the same… The device manufacturers can brand it, and they might have services that they want to include with it, but otherwise it should be the same.”
This right here is EXACTLY how I feel about Android as a whole. Why have two different manufacturers, with two different skins on top of the same base? Nine times out of 10, the devices will not work cohesively, and it will end having a negative impact on the consumer, which is bad for everyone. Another worry that I had was that Samsung was going to try to do too much with their Samsung Gear Live, and make it an unusable experience for someone who wants to get that watch, specifically.
Source: Ars Technica
po.src = 'https://apis.google.com/js/platform.js';
var s = document.getElementsByTagName('script'); s.parentNode.insertBefore(po, s);
The post No OEM Skins Allowed For Android Wear, Android Auto, or Android TV appeared first on AndroidGuys.
There was much announced at the Google I/O 2014 keynote, and one of the perhaps less glamorous announcements was for Android One, a program where even emerging markets, like India, will have access to phones with Android on them for around $100. While this isn’t going to tickle everyone’s fancy, it’s an undeniable fact that despite […]
Razer are creating a micro-console that will be powered by Android TV, allowing users to stream movies, music, and other apps for entertainment on the large-screen, the company announced today.
Android TV was announced at Google I/O and Razer have jumped straight on the ship with their Razer console. You’ll be able to navigate around the UI with a special companion app on the phone and tablet, together with the native voice control built into Android TV.
“This is a console of the future,” says Min-Liang Tan, Razer co-founder and CEO. “Built on Google’s incredible Android TV platform, the Razer micro-console incorporates not only hardcore and casual gaming, but music, movies and other entertainment and social applications, all on an affordable system.”
The Razer console is scheduled to be released in fall 2014.
There were plenty of rumors suggesting that HTC is working on a new Nexus tablet, dubbed Nexus 9. We’ve even had a detailed leak regarding the device which included not only a render of the device but its specifications as well. Well, something interesting happened on Google I/O which might suggest that the leak was true, to some extent at least.
If you look at the picture Google used at this year’s I/O, you’ll notice a weird look tablet in the middle which is not the Nexus 7 (2013) (it is not Samsung’s Nexus 10 either, you can tell that on a first glance). I’ll tell you why:
- The camera is on the middle of the tablet (from portrait perspective), while the one on the Nexus 7 is on the right side of it, not completely, but still, it’s not centered.
- You’ll notice the front facing speaker on the render, next to a front facing camera. Well, Nexus 7 doesn’t have a front facing speaker. On the other hand the leaked HTC Volantis doesn’t either, as far as we can tell by the render linked above at least.
- The tablet on this render is in landscape while the Nexus 5 (on the right) is in portrait. You can see that the tablet is taller in landscape than Nexus 5 is in portrait, which also doesn’t match up to Nexus 7′s proportions. Nexus 5 is 137.9mm tall while the Nexus 7 (2013) is 114mm wide.
This really doesn’t have to mean anything, maybe Google is playing with us. Be it as it may, we do think this is for real and that Google wanted to tease us a bit, in other words we don’t think it’s their way of trolling us or that it was an accident. What do you think?
The post Did Google show us HTC Nexus 9 render on Google I/O? appeared first on AndroidGuys.
Google released a promo video showing off Android “L” on various devices and situation as a part of Google I/O
Google really had lots to say at this year’s Google I/O. We definitely expected a promo video for it and Google delivered.
Video runtime is around 2 minutes and it shows most of what Google has been talking about, or better, presenting at Google I/O this year. This promo video is tracking a guy and his dog in different situations, from waking up and running to a dog show and chillin’ in the living room. Throughout the video you can see Google’s new Android Wear in action on a LG G Watch and Android “L” on a Nexus 5 and Nexus 7, they even included Android TV and Android Auto in the story. Oh well, see it for yourself:
Source: Google (YouTube)