Google I/O- Day 2

I felt so much better and I was couldn’t wait to get started.

We started with the “Accessibility is My Favorite Part of the Platform.” Rob talked about the importances of building applications with accessibility in mind, diversity of accessibility needs, guidelines and tricks. He covered different large categories of accessibility and how it can be short term, long term or permanent. Rob shared ARIA and how he uses it. For early sign up for Web Accessibility Udacity Course, go to

The next session we went to was “Deep Dive into the Realtime Database.” It was more like an overview of Firebase. David East went into how Firebase handles the concepts of being realtime and offline simultaneously.  He explained how Firebase is a noSQL and uses JSON data structure, connecting several users to a single database. Each user can add, delete and  modify data and when this happens, it pushes from the user that made the change to the sever and the sever send the updated information to all the users that are connected.

Then it was lunch time. During lunch I played tetherball with James and checked out some booths:


After lunch we went to “Search and the Mobile Content Ecosystem.” Richard Gingras talked about how search has evolved and what the future looks like. He started with how google searches looked before, just blue links, to now having content that is richer and faster. He shared that using Accelerated Mobil Pages (AMP) can increase the load time, improve user experience and proved in search results richer content.


The Mobile Web: State of the Union” was the next session! Rahul Roy-chowdhury talked about Progressive Web Apps and how there are four categories for great mobil access: accelerate, engage, convert & retain. He shared that using Accelerated Mobile Pages and Progressive Web Apps increase the load speed for applications by allowing users to be able to scroll immediately through passive event listeners. It keeps the user engaged by using service workers (which install small portions of the app that is need for that particular content). They can also be used offline, through access to cache content and it pre-caches content as well. By having a better user experience, users are more likely to use complete transactions and Rahul introduced Credential Management API, which when credentials are saved in chrome, they can be accessed into apps, allowing fewer steps for users.
Then it was all about Polymer at the “Polymer and Progressive Web Apps: Building on the modern Web” by Taylor Savage. He went through how polymer can support Progressive Web Apps by limiting the amount of meta frameworks. Polymer is designed to be components based and that allows customization and ability to use parts or all for your web app. He also shared that with polymer the components that are written can be used again versus using another framework in which those components are only viable within that framework.

The last session was “Instant Loading: Building offline-first Progressive Web Apps.” This session was on the same topic, but with a different approach. Jake Archibald shared that by starting off with designing web apps to used (or at least, what happens) when it is off line, lie-fi (spotty wi-fi) and online. He went step by step on his decisions of how he wanted his app to respond in the three situations. He was hilarious, because he had epic music and great gifs. He talked about service workers, home screens, indexing and background syncs.

Then it was dinner time and I/O after hours. I need to collect a few resources from other people for this post, but it’ll be up as soon as possible.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s