• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

Google I/O 2012 |OT|

Status
Not open for further replies.
ijgombVJOTb6W.png


Two more, first come first serve.

Yoink!
 
iEzLRsoPqZjOB.png


The next livestreamed Android session is focused on performance too, which makes three in a row. Google is really hunkering down on the butter this year.
 
7:00 to 8:00 Eastern · 4:00 to 5:00 Pacific

* What I'll be watching.


I didn't understand a thing they said but somehow I feel smarter

I think I got like 15% of it myself.

I'm flabbeghasted their dim view solution wasn't a transparent bitmap overlay to begin with. wtf.

The "default" method is a bit more powerful, I believe (you can do a bit more with it.) But yeah, I did find it odd too.
 
ibpKn362GqZ8rE.png


ibkSQ7IESWhSny.png


ix80m3Uy9JJ1F.png


"CSS animation is your get out of jail free card." Wow, nice! Chrome for Android doesn't interrupt CSS animations for JavaScript (coming soon to desktop versions they said.) Makes it much easier to prevent "hitching."
 
9:30 to 10:30 Eastern · 6:30 to 7:30 Pacific

  • (Tech Talk) Ignite
    Richard Warp, Thomas Park, Peter Norvig, David Weekly, Chris Vein, Amy Jo Kim, Chiu-Ki Chan, Jon Vlachogiannis, DJ Patil, Chris Branch, Chris Marks
 
You missed an awesome session! Really informative.

Updating the OP... Adding the correct schedule for today, and clearing out Day Three since it's almost entirely inaccurate. I'll add it back with the YouTube recordings tomorrow night.
 
None of the remaining sessions on the schedule have a little video icon... no livestreams on the last day? :(

On the good news front, some presentations seem to have been uploaded that weren't livestreamed:


I'll be adding those back into the OP at the right times. If you stumble on any other presentations that are missing, please post what they are. Thanks. :)

Goodnight everyone! See you in six hours!
 
Did I miss any comments about the competition from the top guys at Google? Did they even mention anyone? Apple, MS?

I think the only snap was at Nintendo during the Tegra 3 demo.

"Who says mobile gaming has to be casual?"

Article talking about the skydive jump:

http://techcrunch.com/2012/06/28/how-google-pulled-off-their-live-video-skydiving-with-glasses-demo/

Interesting tidbit, makes my mind race about Google using Perlmans MIMO tech, they are hooking up with onlive for some stuff...

One big technology hurdle was connectivity, which was needed to get the live video signal. It’s not easy to get Internet bandwidth for a skydive nearly a mile up in the air. It’s too high for cell coverage and regular WiFi isn’t reliable enough. Google says their team tried several approaches. They tested using a wok (that’s not the name of a special antenna, they are talking about the cooking tool) with a mifi 4G LTE hotspot connected to it. But that wasn’t used during the live demo. Google hasn’t revealed what their solution was, but they say it was very much cheaper than high-end professional equipment.
 
Will the sessions or any part of Google I/O be streamed live via the Internet?
We will be streaming the Google I/O keynote and many of the sessions. We will also be recording all of the sessions and making them available online. Please check back after the event to view the recorded sessions or follow us on the Google Developers Google+ page where we will announce when recordings are available.

Hope it's true :(
 
I'm not a developer myself, but it seems like they're really providing a ton of support with this O_O Is this standard for a company like this to do or?

Depends on what you mean by "standard." Most of the big companies (Microsoft, Apple, Oracle I think) do have developer events in the vein of this, but Google I/O is unique because of the YouTube factor -- not only are the keynotes livestreamed and put up later, but many of the sessions as well. I know many developer events have, in the past, discouraged that because it's "proprietary knowledge" and they want you to buy tickets in order to access it. Google knows it doesn't have that problem, in fact I/O is probably too popular for its own good. :P

Besides that, Google has a lot of APIs and platforms and most of them are generally held in high regard by actual consumers, as well as developers (Android, Maps, YouTube, Chrome.) This means that: 1. their APIs are constantly evolving and Google has to brief current developers on the key additions and updates, 2. their APIs are exceedingly deep, requiring tutorials and "how to's" for new developers with an interest in them, and 3. developers are attracted to the APIs because the services and products are so well liked by consumers.

Google is also a massive company with many products too, which sort of amplifies things. Like I said in the OP, the technical knowledge on display is staggering and unprecedented.
 
I'm not a developer myself, but it seems like they're really providing a ton of support with this O_O Is this standard for a company like this to do or?
Standard for big tech companies. Microsoft has BUILD/TechEd and Apple has WWDC. Both are multi day developer conferences that have 100+ sessions provided for attendees at the conference and developers online.

Google focuses on Android, Chrome, and their cloud services. Apple focuses on iOS, OS X, and iCloud. Microsoft focuses on Windows, Windows Phone, and their cloud services.

By the way, did anyone catch the I/O session on Maps to see if they hinted at a new SDK for iOS devs since MapKit won't be using Google Maps anymore in iOS 6+? They still link to MapKit on the Maps API site: https://developers.google.com/maps/mobile-apps
 
Has anyone gotten to the code of the Q yet? It'd be cool to run on my HTPC. I have an Airplay type thing set up, but I don't like that it has to stream from my specific device. I think pulling content from the server is a much better idea.
 
The session on the Web Audio API is really cool if you're interested it making web apps with audio. You can do some pretty sweet stuff using the API, much of which is demoed during the talk. Then you can go here (if you've got Chrome) and play with all the stuff he talks about.
 
I promise I'll finish adding the vids to the OP eventually.

Until then, the notifications portion of the What's New in Android talk was very insightful:


Apps can now tell the system which priority they should be. The lowest, PRIORITY_MIN, won't even display an icon in the status bar. (The notification itself will still be there when you pull the shade down, but otherwise you're not alerted to its presence.) Great win for UX and not overcluttering the status bar.


Buttons and other views can be added to notifications via the new .bigContentView() API call.


They field tested a variety of methods for expanding the notifications, and Pulldown is what they decided to show off. However, all four of these will still work.


Smartly, they knew the priority system might be abused so they added the ability to block individual apps' notifications in JB.

Now it's time for some third party apps and how they're using the new notifications API:









"That's still true today." Wow, that takes me back. I remember downloading the m3 SDK when Android was first announced... seems like forever ago.


The key points.

The dude also admitted they had changed the notification icon design guidelines several times and said, "Send me the bill for your latte sipping designers." Lol.
 
Too much going on in the notification bar could get annoying quickly. I like the idea of quickly doing things in the notification bar without exiting my app. That's brilliant. But that's a fairly small, limited, precious space. At least Google is allowing the user to identify which app is harassing them. Draw Something is already harassing me and I'm still on ICS.

And all those different gestures to expand a notification? I should only have to use a one finger gesture.
 
Too much going on in the notification bar could get annoying quickly. I like the idea of quickly doing things in the notification bar without exiting my app. That's brilliant. But that's a fairly small, limited, precious space. At least Google is allowing the user to identify which app is harassing them. Draw Something is already harassing me and I'm still on ICS.

And all those different gestures to expand a notification? I should only have to use a one finger gesture.

swipe down to expand, up to contract, and right or left to dismiss...would be nice.
 
Too much going on in the notification bar could get annoying quickly. I like the idea of quickly doing things in the notification bar without exiting my app. That's brilliant. But that's a fairly small, limited, precious space. At least Google is allowing the user to identify which app is harassing them. Draw Something is already harassing me and I'm still on ICS.

And all those different gestures to expand a notification? I should only have to use a one finger gesture.

Since Zynga bought Draw Something, a very specific one-finger gesture is the appropriate response to it.
 
Since Zynga bought Draw Something, a very specific one-finger gesture is the appropriate response to it.

Too true. I can't believe how quickly it turned from nice distraction to super annoying thing distracting you.
 
Too true. I can't believe how quickly it turned from nice distraction to super annoying thing distracting you.

I uninstalled Drawsomething. Too many annoying notifications. Plus, the game requires too much input for my taste.

Anyways, watching the "For butter or for worst " video makes my head hurt. So much going on. Didn't know making the OS smooth required so much work.
 
I uninstalled Drawsomething. Too many annoying notifications. Plus, the game requires too much input for my taste.

Anyways, watching the "For butter or for worst " video makes my head hurt. So much going on. Didn't know making the OS smooth required so much work.

Its just a triple buffered v sync with their own parallel running processors on an iterative scale in order to synchronize the surface flinger inputs with the display output in order to minimize the latency in the GUI that's created in visual basic so they can track down the IP.
 
Its just a triple buffered v sync with their own parallel running processors on an iterative scale in order to synchronize the surface flinger inputs with the display output in order to minimize the latency in the GUI that's created in visual basic so they can track down the IP.

Yup...JUST.
 
Its just a triple buffered v sync with their own parallel running processors on an iterative scale in order to synchronize the surface flinger inputs with the display output in order to minimize the latency in the GUI that's created in visual basic so they can track down the IP.

I feel like you'd have to be a graphics programmer to understand most of it. I know V-Sync and (triple) buffering are terms tossed around by PC gamers with graphic fetishes. :P
 
Nope, but until 2.2 android was an incredibly sloppy os, so It doesn't surprise me they had to do some major rewriting. (for example iOS was GPU accelerated super buttery since 1.0)

You have to remember that the only important metric when guaging OSs is smoothness.
 
Status
Not open for further replies.
Top Bottom