Introduction to Google Developer Relations

transcript

Developer Relations

Patrick ChanezonDeveloper Advocatechanezon@google.comhttp://twitter.com/chanezon London, June 2011

Introduction to

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

DevRel’s Mission

Make Android, HTML5, and the

Google developer platform the ecosystem of choice for the

global developer community

Google Developer Products History

Google APIs Grandfather: Vint Cerf

Chief Internet Evangelist

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

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

Google APIs MapMaker: Bret Taylor

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

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

Google APIs Guide: Hal Varian

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

• Lock-In and Switching Costs

• Standards

Google Developer Platform VP: Vic Gundotra

Innovation in the Open

Google Developer Relations Director: Michael Winton

History: 2006

• DevRel was founded (US-only)

• Developer Support Engineers

• Checkout, Ads, GWT, GData APIs

• Geo Developer Day

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

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

History: 2009

• Continued global and partner outreach

• Developer Program Managers

• GTUG program launched

• 2nd Google I/O

• features Android, Wave

History: 2010

• DevRel expands globally

• 164 GTUGs in 58 countries

• 3rd Google I/O

• features HTML5, Android, Google TV, App Engine

History: 2011

• Tech Writers join DevRel

• 4th Google I/O

• features Android, Chrome

Where are we now?

Current and pending starts through end of 2011

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

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

• High: Ads, Google TV

• Medium:

• Enterprise Platform

• Cloud Platform

• Geo

• YouTube

• Commerce

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

Another way to look at itReach the Plateau of productivity

Gartner Hype Cycle

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.

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

What are our roles?

• Developer Advocates

• Developer Programs Engineers

• Developer Program Managers

• Technical Writers

Developer Advocates create momentum

through “poster child” competitive wins

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

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

Ahhhh... So they are “Evangelists”?

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)

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)

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

A “Poster Child” is...

• Compelling, core use case

• Best in class

• Recognized name

• Has a large user base

• Press darling

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!

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!

Developer Programs Engineers grow and

support the community

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

Developer Programs Engineers grow and

support the community

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

Developer Program Managers run global,

scalable evangelism and support programs

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

Developer Program Managers run global,

scalable evangelism and support programs

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!

Technical Writers create content to

support Google's most strategic APIs and

developer products

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

Technical Writers create content to

support Google's most strategic APIs and

developer products

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

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

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

GoogleDeveloper

DevFests and xDLs

GTUG and community

Google IO

Google IO Extended

Google Developer Days

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

Google Devfests

• 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

GTUG London

Developer Labs

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

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

What can we do for you?

• Technical help

• Trusted Testers Programs

• Marketing: blog, videos, events

• Connections

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

Technical Help & Early Access

Marketing

• Blog / video interviews

• Case Studies

• Press contacts

• Invite you to speak at our events

• Or do joint talks at 3rd party events

Marketing

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

Twitter @GoogleCode

Devrel in Europe

Work with US!

Devrel Circa 2010, Credits Bill Luan

Google Cloud Services

Developer DayGoogle 2010

Google Storage Prediction API

BigQuery

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

Google App Engine

Google's Cloud Offerings

Google Storage Prediction API

BigQuery

Your Apps

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

Google App Engine

Google's Cloud Offerings

Enterprise Firewall

Enterprise Data Authentication Enterprise Services User Management

Buy from Google

Google Apps for Business

Build and Buy all your enterprise cloud apps...

Enterprise Application Platform

Buy from others

Google Apps Marketplace

Enterprise Firewall

Buy from Google

Build your own

Google App Engine

Buy from others

Google Apps Marketplace

Enterprise Firewall

Buy from Google

Google App Engine

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

App Engine Growth

App Engine LaunchPython

DatastoreMemcachelogs export

2008 2009 2010

JavaDB Import

Batch write/readHttps

Status-Dashboard

Task QueuesXMPP

incoming email

MultitenancyInstance Console

Always Onhi-perf imag

10 min tasks

BlobstoreAppstats

cursorsMapper

Hi-ReplicationDatastore

Channel APIFiles API

Remote APIProsp Search

100,000+ Active Developers per Month

By the Numbers

200,000+Active apps per week

By the Numbers

1.5B+Pageviews per day

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

Questions?