Live blogging Google I/O: HTML5 status update
May 20, 2010 | Posted by Jeffrey Barke | Add a Comment
Ian Fette
Jeff Chang
Search Results for 'google i/o'
May 20, 2010 | Posted by Jeffrey Barke | Add a Comment
Ian Fette
Jeff Chang
| Posted by Jeffrey Barke | Add a Comment
Bryan McQuade
Richard Rabbat
| Posted by Jeffrey Barke | 8 comments
Matt Cutts
Greg Grothaus
Evan Roseman
| Posted by Jeffrey Barke | Add a Comment
Nick Mihailovski
First time GA has done anything at Google I/O.
Four components
* Processing
* Management
* Data collection
* Data exporting
Dimensions: Strings (80 dimensions)
Metrics: Numeric values (95 metrics)
1. Logs (collection)
2. Goals, filters, profile settings (management)
3. Data structure (processing)
4. Functions (processing)
5. Tables (processing)
6. Query engine (export)
Visitor/session/hit levels
1×1 tracking pixel with a number of parameters appended. Three of these parameters relate to visitor, session, hits.
Their back end parses their logs and sorts and stores based on parameters.
ga:visits
int visits(Session session, int index) {
}
[Too quick to get these code snippets]
Data types (several)
Protocol (_utm.gif)
Client libraries:
* JavaScript (ga.js)
* Android SDK
* iPhone SDK
* Mobile websites
** PHP/JSP/ASP/Perl
* ActionScript 3
** Flash/Flex/Air
* Silverlight
Account Management
Data types:
* Accounts
* Web properties
* Profiles
* Goals
* Advanced segments
Protocol:
* Google data
Data export API
Protocol: Google Data
Client libraries:
* Java
* JavaScript
* Python
* .Net (C#)
* Ruby
* Perl
* PHP
Use the Data feed query explorer (in Google Labs)
Using visitor behavior to optimize user experience: ranking a number
Start with a list of unordered links. Can use GA to track the number of times people click on these links.
Demo is powered by MAMP; hopefully the code will be made available. (Definitely need this code)
Two parts to the demo:
1. How to send data explicitly to GA
2. How to retrieve data from GA
Part one was implemented with PHP and JS
Part two is a scheduled .Java application
Recently introduced asynchronous tracking (to avoid blocking the browser).
Working on a better developer ecosystem:
http://google.com/analytics/apps
Working on a better turn-around time than 24-hours.
Working on complete data export, but difficult because they store it as a cube. The current export API is actually more of a query API.
| Posted by Jeffrey Barke | Add a Comment
Vic Gundotra
Opens with an anecdote of how he got involved with Android at Google.
In 18 months, 60 compatible devices. Q408 to Q210.
21 OEMs, 48 countries, 59 carriers.
A review of the accomplishments/adoption numbers of Android.
50,000 applications in the Android marketplace.
5x growth in mobile search ‘08-’10 (all phones)
Android 2.2 Froyo announced. JiT compiler. 2x-5x speed up in applications.
Microsoft Exchange friendly:
* auto-discovery
* security policies
* GAL lookup
New SDK features:
Application Data Backup API
Cloud-to-device messaging API (this is impressive)
** From desktop, driving directions sent to phone. Phone picks up message not as text, but as “intent,” immediately launches navigation application.
Tethering & portable hotspot
The Froyo browser has a 2x-3x increase in JS performance. Doing laps around Eclair and the iPad.
Amazing voice recognition capabilities! Voice input will be a first-class means of interacting with Android.
Android will support Flash and AIR. Digs at Apple.
Improvements to marketplace:
* Easier to search/find apps
* Search inside apps
* Move to SD cards
* Allow automatic updating
Application error reports: on crash user can send error report to the application developer.
Developers can see the entire stack-trace of what happened.
Can search the marketplace via the PC. If logged in and purchase an app, app will be sent to device instead of having to tether and sync device with PC.