89
Developer Relations 2 Patrick Chanezon Developer Advocate [email protected] http://twitter.com/chanezon London, June 2011 Introduction to

Introduction to Google Developer Relations

Embed Size (px)

DESCRIPTION

Introduction to the Google Developer Relations team: who we are, what we do, what we can do for you, how to work with us.This was presented at the Google European Executive Briefing at The Royal Society in London June 29th 2011

Citation preview

Page 1: Introduction to Google Developer Relations

Developer Relations

2

Patrick ChanezonDeveloper [email protected]://twitter.com/chanezon London, June 2011

Introduction to

Page 2: Introduction to Google Developer Relations

P@ in a nutshell

• French, based in San Francisco

• Developer Advocate, Google Cloud & Apps

• Software Plumber, API guy, mix of Enterprise and Consumer

• 18 years writing software, backend guy with a taste for javascript

• 2 y Accenture (Notes guru), 3 y Netscape/AOL (Servers, Portals), 5 y Sun (ecommerce, blogs, Portals, feeds, open source)

• 6 years at Google, API guy (first hired, helped start the team)

• Adwords, Checkout, Social, HTML5, Cloud

Page 3: Introduction to Google Developer Relations

DevRel’s Mission

Make Android, HTML5, and the

Google developer platform the ecosystem of choice for the

global developer community

Page 4: Introduction to Google Developer Relations

Google Developer Products History

Page 5: Introduction to Google Developer Relations

5

Google APIs Grandfather: Vint Cerf

Chief Internet Evangelist

Page 6: Introduction to Google Developer Relations

6

Google APIs Pioneer

Nelson Minar

Created APIs at Google

Search API 2002

AdWords API 2005

2006, blog post

“Why SOAP Sucks”

http://tinyurl.com/ykdy32

Page 7: Introduction to Google Developer Relations

7

Google APIs RESTful Standardizer

“'Google Data APIs Protocol' is a horrible name. You can tell that ex-Microsoft employees had a hand in this effort. :)”

Dare Obasanjo (Microsoft)

Adam Bosworth on a bike

Page 8: Introduction to Google Developer Relations

8

Google APIs MapMaker: Bret Taylor

+ =+

+ =

Created the Google Maps API in 2005Starting the trend of Ajax APIs:• Ajax Search• Ajax Feed• Ajax Language• OpenSocial

Page 9: Introduction to Google Developer Relations

9

Google APIs Godfathers: Chris DiBona and Greg Stein

http://code.google.com/opensource/

Google Open Source Program office• Summer of Code

• Project Hosting

• Over 1M lines of Google code open sourced in more than 100 projects

Page 10: Introduction to Google Developer Relations

10

Google APIs Guide: Hal Varian

“Standards change competition for a market to competition within a market”• Network Effects

• Lock-In and Switching Costs

• Standards

Page 11: Introduction to Google Developer Relations

11

Google Developer Platform VP: Vic Gundotra

Innovation in the Open

Page 12: Introduction to Google Developer Relations

12

Google Developer Relations Director: Michael Winton

Page 13: Introduction to Google Developer Relations

History: 2006

• DevRel was founded (US-only)

• Developer Support Engineers

• Checkout, Ads, GWT, GData APIs

• Geo Developer Day

Page 14: Introduction to Google Developer Relations

History: 2007

• DevRel expanded to EMEA and India

• OHA and Android SDK launched

• First Google Developer Day

• features mashups, gadgets, GWT, gears

• 24 hours of around-the-world events

Page 15: Introduction to Google Developer Relations

History: 2008

• DevRel expanded to APAC and LatAM: 7 locations, 4 countries, 3 continents

• Developer Advocates

• First Google I/O

• features OpenSocial, GWT, App Engine, and an Android phone demo

• First DevFest APAC events

Page 16: Introduction to Google Developer Relations

History: 2009

• Continued global and partner outreach

• Developer Program Managers

• GTUG program launched

• 2nd Google I/O

• features Android, Wave

Page 17: Introduction to Google Developer Relations

History: 2010

• DevRel expands globally

• 164 GTUGs in 58 countries

• 3rd Google I/O

• features HTML5, Android, Google TV, App Engine

Page 18: Introduction to Google Developer Relations

History: 2011

• Tech Writers join DevRel

• 4th Google I/O

• features Android, Chrome

Page 19: Introduction to Google Developer Relations

Where are we now?

Current and pending starts through end of 2011

Page 20: Introduction to Google Developer Relations

We’re hiring Worldwidehttps://sites.google.com/site/googdevreljobs/

Page 21: Introduction to Google Developer Relations

Current Priorities• Highest: Android, Chrome, HTML5, Social

• High: Ads, Google TV

• Medium:

• Enterprise Platform

• Cloud Platform

• Geo

• YouTube

• Commerce

Page 22: Introduction to Google Developer Relations

Our Challenge: Crossing the Chasm

Picture from Wikimedia Foundation http://en.wikipedia.org/wiki/File:Technology-Adoption-Lifecycle.png

Help Google Developer Products Cross the Chasm

Page 23: Introduction to Google Developer Relations

Another way to look at itReach the Plateau of productivity

Gartner Hype Cycle

Page 24: Introduction to Google Developer Relations

When are we done?

• When there’s so much energy and momentum that developers just assume they’ll use our platform.

• When there’s a thriving ecosystem of tools, consultants, trainers, and others that we’ve never even spoken to.

• When the voice of unpaid advocates for our platform is so strong ours isn’t needed.

Page 25: Introduction to Google Developer Relations

We provide 2-way communication

• Critical bugs, feature requests

• API design, consistency, and stability

• Strategies, roadmaps, timelines

• Transparency

In addition to being advocates to developers, we are advocates for developers internally

Page 26: Introduction to Google Developer Relations

What are our roles?

• Developer Advocates

• Developer Programs Engineers

• Developer Program Managers

• Technical Writers

Page 27: Introduction to Google Developer Relations

Developer Advocates create momentum

through “poster child” competitive wins

Page 28: Introduction to Google Developer Relations

Developer Advocates Are

• Developers themselves

• Trusted faces of Google in the community

• People who care about developers’ needs

• Deeply passionate about the products they represent

Page 29: Introduction to Google Developer Relations

Developer Advocates Are Not...

• Biz Dev or Sales

• Developers don’t trust Biz Dev

• They definitely do not trust Sales

... and platform decisions in IT are made by developers

Page 30: Introduction to Google Developer Relations

Ahhhh... So they are “Evangelists”?

Page 31: Introduction to Google Developer Relations

It’s in the Name

“Evangelist” (noun)*

1. a writer of any of the four Gospels

2. a person who evangelizes

3. an enthusiastic advocate

* Merriam-Webster’s Online Dictionary (http://www.merriam-webster.com)

Page 32: Introduction to Google Developer Relations

It’s in the Name

“Advocate” (noun)*

1. one that pleads the cause of another

2. one that defends or maintains a cause or proposal

3. one that supports or promotes the interests of another

* Merriam-Webster’s Online Dictionary (http://www.merriam-webster.com)

Page 33: Introduction to Google Developer Relations

Names change the tone

Dion Almaer summarized it the best

“Then you put it together: Developer Advocate and a funny thing happens. What does that mean? At first people think that you are advocating to developers, but it is also very important to think about the other connotation. You think about being an advocate of the developer”Developer Advocate versus Technical Evangelist; When names change the tone

http://almaer.com/blog/developer-advocate-versus-technical-evangelist-when-names-change-the-tone

Page 34: Introduction to Google Developer Relations

Developer Advocates create momentum

through “poster child” competitive wins

Page 35: Introduction to Google Developer Relations

A “Poster Child” is...

• Compelling, core use case

• Best in class

• Recognized name

• Has a large user base

• Press darling

Page 36: Introduction to Google Developer Relations

What Do We Want Them to Do?

• Launch their app!

• Even better, launch it at our event

• Talk to the press & analysts

• Tell the world how we enabled their success!

Page 37: Introduction to Google Developer Relations

Developer Advocates create momentum

through “poster child” competitive wins

Page 38: Introduction to Google Developer Relations

Tell These Stories

• Use them as examples in our talks

• Bring these developers on stage with us

• Talk about them in blog posts and tweets

• Feed the stories to our PR team and press

• Get them to tell the world themselves!

Page 39: Introduction to Google Developer Relations

Developer Programs Engineers grow and

support the community

Page 40: Introduction to Google Developer Relations

They’re engineers

• DPEs actively develop code samples, libraries, and reference apps

• DPEs engage internally with the Eng product teams

• DPEs engage in deeply technical, thorny problems with external developers

Page 41: Introduction to Google Developer Relations

Developer Programs Engineers grow and

support the community

Page 42: Introduction to Google Developer Relations

They’re involved and supportive

• DPEs are involved with the community online - in our forums and across the web

• DPEs engage with developers at GTUG events

• DPEs support developer through posts and tickets

Page 43: Introduction to Google Developer Relations

Developer Program Managers run global,

scalable evangelism and support programs

Page 44: Introduction to Google Developer Relations

They’re Program Managers

• Developer PMs organize, prioritize, analyze, and provide infrastructure

• Developer PMs optimize: they make sure initiatives execute smoothly and efficiently

• Developer PMs connect: they bring together people, resources, and ideas

Page 45: Introduction to Google Developer Relations

Developer Program Managers run global,

scalable evangelism and support programs

Page 46: Introduction to Google Developer Relations

The programs are global and scalable

• Developer PMs tackle programs that cut across multiple products

• Developer PMs lead initiatives that have world-wide reach and leverage massive community support

• They focus on programs that reach the most people with the fewest resources

• They’re global - from China to Africa to Tel Aviv to Brazil, and everywhere in between!

Page 47: Introduction to Google Developer Relations

Technical Writers create content to

support Google's most strategic APIs and

developer products

Page 48: Introduction to Google Developer Relations

They love to write!

• Technical writers focus on the written word as their means to educate developers

• They write reference docs, articles, how-to guides, tutorials, books, and presentations

• Technical writers focus on the user, making complex technology easy to understand

Page 49: Introduction to Google Developer Relations

Technical Writers create content to

support Google's most strategic APIs and

developer products

Page 50: Introduction to Google Developer Relations

Writers provide strategic, proactive

support• Technical writers provide great bang-for-

the-buck by scaling out support proactively to users globally

• Our most strategic developer products are only useful if developers understand how to use them

Page 51: Introduction to Google Developer Relations

What programs do we run?

• Tons! We focus on highly-scalable programs that can be run with minimal resources

• Scrappy, but touches tens of thousands of developers

• Work closely cross-functionally with other groups across Google

Page 52: Introduction to Google Developer Relations

Example of our shared ecosystem of programs:

• External developer events are key to driving momentum and adoption

• We share responsibility with Marketing (IO and GDD) and with the external community

IO

GoogleDeveloper

Days

DevFests and xDLs

GTUG and community

Page 53: Introduction to Google Developer Relations

Google IO

Page 54: Introduction to Google Developer Relations

Google IO

Page 55: Introduction to Google Developer Relations

Google IO Extended

Page 56: Introduction to Google Developer Relations

Google IO Extended

Page 57: Introduction to Google Developer Relations

Google Developer Days

Page 58: Introduction to Google Developer Relations

Google Developer Days

Page 59: Introduction to Google Developer Relations

DevFests

• Global, scrappy events of a few hundred devs

• Single track, focuses on a handful of products

• Engagement from community volunteers for execution and speaking

Page 60: Introduction to Google Developer Relations

Google Devfests

Page 61: Introduction to Google Developer Relations

Google Devfests

Page 62: Introduction to Google Developer Relations

GTUGs

• Google Technology User Groups: independent, community-led groups of 10s to 1000s, holding regular in-person events

• 253 chapters in 77 countries held 483 events in the past 6 months, 2+ events per day

Page 63: Introduction to Google Developer Relations

GTUGs

Page 64: Introduction to Google Developer Relations

GTUGs

Page 65: Introduction to Google Developer Relations

GTUG London

Page 66: Introduction to Google Developer Relations

Developer Labs

• Single-product labs with targeted attendees (for example, ADL = Android Developer Lab)

• Global reach, involves partner companies and high-profile developers

Page 67: Introduction to Google Developer Relations

What can we do for you?

• Technical help

• Trusted Testers Programs

• Marketing: blog, videos, events

• Connections

Page 68: Introduction to Google Developer Relations

Technical Help & Early Access

• Provide Technical help

• Direct relationship with a Developer Advocate

• Architecture recommendations

• Involve you in Trusted Tester programs

• Early Access to features and products

• We want your feedback

Page 69: Introduction to Google Developer Relations

Technical Help & Early Access

Page 70: Introduction to Google Developer Relations

Marketing

• Blog / video interviews

• Case Studies

• Press contacts

• Invite you to speak at our events

• Or do joint talks at 3rd party events

Page 71: Introduction to Google Developer Relations

Marketing

Page 72: Introduction to Google Developer Relations

Marketing

Page 73: Introduction to Google Developer Relations

How to Reach us?http://code.google.com/team

Page 74: Introduction to Google Developer Relations

Twitter @GoogleCode

Page 75: Introduction to Google Developer Relations

Devrel in Europe

Page 76: Introduction to Google Developer Relations

Work with US!

Devrel Circa 2010, Credits Bill Luan

Page 77: Introduction to Google Developer Relations

Google Cloud Services

Page 78: Introduction to Google Developer Relations

Developer DayGoogle 2010

Google Storage Prediction API

BigQuery

1. Google Apps2. Third party Apps: Google Apps Marketplace3. ________

Google App Engine

IaaS

PaaS

SaaS

Google's Cloud Offerings

Page 79: Introduction to Google Developer Relations

Developer DayGoogle 2010

Google Storage Prediction API

BigQuery

Your Apps

1. Google Apps2. Third party Apps: Google Apps Marketplace3. ________

Google App Engine

IaaS

PaaS

SaaS

Google's Cloud Offerings

Page 80: Introduction to Google Developer Relations

Developer DayGoogle 2010

Enterprise Firewall

Enterprise Data Authentication Enterprise Services User Management

Buy from Google

Google Apps for Business

Build and Buy all your enterprise cloud apps...

79

Enterprise Application Platform

Page 81: Introduction to Google Developer Relations

Developer DayGoogle 2010

Buy from others

Google Apps Marketplace

Enterprise Firewall

Enterprise Data Authentication Enterprise Services User Management

Buy from Google

Google Apps for Business

Build and Buy all your enterprise cloud apps...

79

Enterprise Application Platform

Page 82: Introduction to Google Developer Relations

Developer DayGoogle 2010

Build your own

Google App Engine

Buy from others

Google Apps Marketplace

Enterprise Firewall

Enterprise Data Authentication Enterprise Services User Management

Buy from Google

Google Apps for Business

Build and Buy all your enterprise cloud apps...

79

Enterprise Application Platform

Page 83: Introduction to Google Developer Relations

Google App Engine

-Easy to build-Easy to maintain-Easy to scale

80

Page 84: Introduction to Google Developer Relations

App Engine Growth

App Engine LaunchPython

DatastoreMemcachelogs export

2008 2009 2010

JavaDB Import

cron

Batch write/readHttps

Status-Dashboard

Task QueuesXMPP

incoming email

MultitenancyInstance Console

Always Onhi-perf imag

10 min tasks

BlobstoreAppstats

cursorsMapper

2011

Hi-ReplicationDatastore

Channel APIFiles API

Remote APIProsp Search

Page 85: Introduction to Google Developer Relations

100,000+ Active Developers per Month

By the Numbers

Page 86: Introduction to Google Developer Relations

200,000+Active apps per week

By the Numbers

Page 87: Introduction to Google Developer Relations

1.5B+Pageviews per day

By the Numbers

Page 88: Introduction to Google Developer Relations

By the Numbers

Official Royal Wedding on App Engine

On Wedding day, served: • Up to 32k requests per second• 37.7 million pageviews • 13.7 million visitors

Page 89: Introduction to Google Developer Relations

Questions?