This document discusses how Google is working to make the client, connectivity, and cloud more powerful and accessible through open technologies. It focuses on three areas: 1) Making the cloud more accessible through technologies like Google App Engine and data APIs. 2) Keeping connectivity pervasive through open platforms like Android and social APIs. 3) Making the client more powerful through technologies like Google Web Toolkit, Gears, and social platforms like OpenSocial. The goal is to advance an open web that empowers both users and developers.

2. Client, Connectivity,
and the Cloud
Vic Gundotra
Engineering VP, Google Inc.
May 28, 2008

3. Mainframe
computation &
storage
1
0
-1
accessibility
ease of
deployment
1
0
-1
functionality
3

4. Personal Computer
computation &
storage
1
0
-1
accessibility
ease of
deployment
1
0
-1
functionality
4

5. Internet
computation &
storage
1
0
-1
accessibility
ease of
deployment
1
0
-1
functionality
5

6. Internet
computation &
storage
1
Make the cloud more accessible
0
-1
accessibility
ease of
deployment
1
Make the client more powerful
0
-1
functionality
6

7. Internet
computation &
storage
1
Make the cloud more accessible
0
-1
accessibility
Keep connectivity pervasive
ease of
deployment
1
Make the client more powerful
0
-1
functionality
7

8. What? Why? How?
Make the cloud more accessible
1
Keep connectivity pervasive
2
Make the client more powerful
3
8

9. What? Why? How?
“The industry is going
to develop as a
partnering industry;
not as a monopoly
industry… likewise,
[Google’s] culture is
one of consensus.” innovate in the open
Eric Schmidt, on the Internet and Google
9

10. What? Why? How?
Richer More More More
web apps users usage revenue
open web platform
10

11. What? Why? How?
Latency Authentication
Security Many devices
Scalability Storage
Distribution
Internationalization Browser compatibility
Programming languages Deployment User administration
Monetization Debugging Analytics
AJAX
11

12. Client Connectivity Cloud
make it more powerful
12

13. User Experience
Proprietary Platforms v. Open Web
?
user experience
Canvas
XHR
CSS
DOM native (windows, OS X)
HTML flash, air, silverlight
open web
13

14. Gears
Extending the Browser – Enabling Rich Web Apps
• LocalServer: offline access
• Database: local, relational DB
• WorkerPool: asynchronous
threads
code.google.com/apis/gears 14

15. Gears
Standards-Driven and Open Source
HTML 5 Gears
database
localserver
15

16. Allen Hurff, Engineering SVP
MySpace

17. MySpace Mail
Powered by Gears
• Available to everyone today!
• Committed to open web standards
• Technical session with Owyn Richen, Wed 3-4pm
17

18. Client Connectivity Cloud
keep it pervasive
18

19. Operator/Mkt Requirements Operator Client/Server APIs
Language, Presentation, Branding Billing, Game Servers, Messaging
Java Virtual Machine (JVM) Proprietary APIs
MIDP 1.0, MIDP 2.0, CDLC, JSR 120, JSR 135, JSR 185 Nokia UI API, Motorola GPS, etc.
Operating System Characteristics
Access to Camera, Address Book, IR, Bluetooth, Telephony
Physical Device Characteristics
Heap, Screen size, RMS, Key Mapping, Processor
(JavaWorld.com, 2004)
19

20. Steve Horowitz, Engineering Director
Android

21. Android
Opening Up the Mobile Software Stack
• Open source mobile
platform & key applications
• WebKit browser
• Raise the bar of baseline
mobile functionality
code.google.com/android 21

22. Client Connectivity Cloud
make it more accessible
22

23. Kevin Gibbs, Tech Lead
Google App Engine

24. Google App Engine
Running Web Apps on Google’s Infrastructure
• Fully-integrated
application environment
• Python Runtime
• Free quota of 5M
pageviews per month
code.google.com/appengine 24

25. Google App Engine
Technical Challenges
25

26. Google App Engine
Financial Challenges
26

27. Google App Engine
Administrative Challenges
27

28. Google App Engine
Easy to Start, Easy to Scale
28

29. Develop locally. Deploy to Google. Launch.
29

30. Develop locally. Deploy to Google. Launch.
Deploy
30

31. Develop locally. Deploy to Google. Launch.
31

32. Find out which of your Twitter
friends know each other!
32

33. 33

34. 34

35. “We got a prototype of our new ‘Pix Chat’
OpenSocial app running in App Engine and the
Hi5 sandbox this morning. It took about 3 hours to
get the app serving and our db code converted.”
Pixverse
35

36. Google App Engine
Areas of Work, Including…
• Offline Processing
• Rich Media Support (e.g., large file UL / DL)
• Add’l Infrastructure Services
36

37. Google App Engine
Areas of Work, Including… Two New APIs
• Offline Processing
• Rich Media Support (e.g., large file UL / DL)
• Add’l Infrastructure Services
• Memcache
• Image Manipulation
37

38. Google App Engine
Free Quota and Expected Pricing
Resource Free Quota Additional
CPU 10-12¢ / core-hour
Storage 15-18¢ / GB-month
Equivalent to 5M
pageviews / month
for a typical app
Bandwidth, Outgoing 11-13¢ / GB transferred
Bandwidth, Incoming 9-11¢ / GB transferred
38

39. Google App Engine
Announcing Open Signups
39

40. Client Connectivity Cloud
make it more accessible
40

41. Mark Lucovsky, Technical Director
Google Data and AJAX APIs

42. Google Data APIs
Read / Write Access To Google Services
YouTube
Notebook Health
AtomPub
Calendar Code Search
Blogger
<your web apps>
Docs
Picasa
Contacts Base
Spreadsheets Apps
code.google.com/apis/gdata 42

43. AJAX APIs and Controls
Sprinkle the Web Onto Your Applications
Maps
Videos Blogs
REST
News Books
Images
<your web apps>
RSS
Listings
Atom
YouTube Search
code.google.com/apis/ajax 43

44. Client Connectivity Cloud
make development easier
44

45. Bruce Johnson, Engineering Manager
Google Web Toolkit

46. Google Web Toolkit
Java Development, JavaScript Deployment
Optimizing
Cross-compiler
Java Compiled
source JavaScript
code.google.com/webtoolkit 46

47. Google Web Toolkit
Develop With <Your Favorite Java IDE>
47

48. Google Web Toolkit
Announcing 1.5 Release Candidate
• Java 5 language features
• Performance, performance,
performance
* Thank you, open source
contributors!
48

49. Client Connectivity Cloud
make the web more social
49

50. David Glazer, Engineering Director

51. 51

52. 52

53. 53

54. “There are cries from the heart for my
friendship, that relationship to another
person, to transcend documents and sites.”
Tim Berners-Lee, on the “Giant Global Graph”
54

55. Identity OpenID
Authorization OAuth
Apps OpenSocial
55

56. OpenSocial
Making the Web More Social
• A family of APIs
• A reference implementation
• A community of developers,
containers and apps
opensocial.org 56

57. OpenSocial
A Family of APIs
57

58. OpenSocial
A Reference Implementation
58

59. OpenSocial
A Community
59

60. Nat Brown, CTO
iLike

61. iLike on hi5
61

62. iLike on MySpace
62

63. iLike on orkut
63

64. iLike on ingridmichaelson.com
64

65. OpenSocial
By The Numbers – November 2007
0M 0K 0M
total reach developers app installs
65

66. OpenSocial
By The Numbers – May 2008
275M 20K 50M
total reach developers app installs
66

67. OpenSocial
Container Status
67

68. OpenSocial
Container Status
friendster
®
68

69. OpenSocial
Container Status
friendster
®
69

70. OpenSocial
What’s Next
• RESTful (v0.8) # Description: People API
• Template language personFeed = element atom:feed {
( element atom:author { personConstruct
}+
& personEntry*
& generator
& id
& itemsPerPage?
& peopleLink*
& startIndex?
& element atom:title { textConstruct }
& totalResults?
& updated )}
70

71. OpenSocial
What’s Next
• RESTful (v0.8) <Template name=quot;my:Gamequot;>
<os:Page>
• Template language <os:Title>The Game</os:Title>
<os:Body>
<my:FriendScores />
<my:LinkToClick />
<my:InviteFriends />
</os:Body>
</osPage>
</Template>
<Template name=quot;my:FriendScoresquot;>
<os:Headers>
<os:Header>Friend</os:Header>
<os:Header>Score</os:Header>
71

72. Google Friend Connect
Bringing Friends to Every Website
• Built on open standards
• Copy & paste functionality
• Additional reach for
OpenSocial containers and
developers
google.com/friendconnect 72

73. 73

74. Client Connectivity Cloud
open web platform
74

75. Thank You
vicg@google.com
75