0
maturation of the Twitter ecosystem<br />kevinmakice (@kmakice)wednesday, july 22, 2009<br />
this is me<br />
this is me<br />10 tweets<br />5 tweets<br />my wife<br />
this is also me<br />Kevin Makice<br />blog:	 	http://www.blogschmog.net<br />email:	kevin@makice.net<br />twitter: 	kmaki...
this is what i do<br />The Explanation for Design Ex-plan-ationsEli Blevis and Martin A. Siegel (2004) <br />
conceptual design<br />The Explanation for Design Ex-plan-ationsEli Blevis and Martin A. Siegel (2004) <br />
It is no longer sufficient to simply master the technical. <br />More and more, successful design requires a grounded unde...
the maturing ecosystem<br />a history lesson  <br />insights from the ecosystem  <br />iterating the developer mindset<br />
history of the ecosystem<br />what is past is prologue<br />maturation of the Twitter ecosystem<br />
growing<br />November (2008)	~1,000 applications with the API	<br />February (2009)	~2,000 applications with the API<br />...
growing<br />November (2008)	~1,000 applications with the API	<br />February (2009)	~2,000 applications with the API<br />...
growing<br />November (2008)	~1,000 applications with the API	<br />February (2009)	~2,000 applications with the API<br />...
the pioneers<br />early applications of the API<br />maturation of the Twitter ecosystem<br />history of the ecosystem<br />
the innovators<br />applications that found a niche<br />maturation of the Twitter ecosystem<br />history of the ecosystem...
the future<br />areas of current interest<br />maturation of the Twitter ecosystem<br />history of the ecosystem<br />
insights from the ecosystem<br />we know what we are, but know not what we may be<br />maturation of the Twitter ecosystem...
interaction cycle<br />follow network<br />me<br />stream<br />tweet<br />profile<br />aggregate<br />
interaction cycle<br />follow network<br />me<br />stream<br />tweet<br />profile<br />aggregate<br />
properties<br />Code<br />ActionScript/Flash<br />C++<br />C#/.NET<br />Java <br />Objective-C/Cocoa<br />Perl<br />PHP<br...
properties<br />Code<br />ActionScript/Flash<br />C++<br />C#/.NET<br />Java <br />Objective-C/Cocoa<br />Perl<br />PHP<br...
valueless questions<br />How much does the application need context?<br />How quickly is the outcome from the interaction ...
valueless questions<br />Does the application maintain a historical context?<br />How much does this tool support anonymit...
local twittersphere<br />applications helping to highlight local use<br />maturation of the Twitter ecosystem<br />insight...
discovering opportunity<br />using valueless factors to identify gaps<br />maturation of the Twitter ecosystem<br />insigh...
n-factor diagrams<br />Good<br />Evil<br />Red<br />Green<br />
n-factor diagrams<br />Good<br />Evil<br />Red<br />Green<br />Small<br />Big<br />
n-factor diagrams<br />Good<br />Evil<br />Red<br />Green<br />Small<br />Big<br />Valueless terms do not judge the proper...
content<br />Where is the content focus of the tool?<br />Profile<br />Stream<br />
content<br />Twellowhood<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />NearbyTweets<br />Profile<b...
dataset<br />What is the range of the data set needed to create value?<br />Single<br />Aggregate<br />
dataset<br />Twellowhood<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />NearbyTweets<br />Single<br...
content-dataset<br />Aggregate<br />Stream<br />Profile<br />Single<br />
content-dataset<br />Twellowhood<br />Aggregate<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />Near...
content-dataset<br />Twellowhood<br />Aggregate<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />Near...
concept: city mosaic<br />Bloomington, Indiana<br />57 followers | following 94<br />Indiana professor technology student ...
the developer’s mindset<br />in the heart of in the head<br />maturation of the Twitter ecosystem<br />
1) be secure<br />expect the unexpected<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
best practices<br />don&apos;t store passwords (use OAuth)<br />validate incoming data / FIEO (Filter Input, Escape Output...
best practices<br />don&apos;t store passwords (use OAuth)<br />validate incoming data / FIEO (Filter Input, Escape Output...
2) know your impact<br />your use is not their use<br />maturation of the Twitter ecosystem<br />the developer’s mindset<b...
developer demographics<br />may 2009<br />18-50<br />Children<br />Married<br />Male<br />
developer demographics<br />may 2009<br />18-50<br />√<br />Children<br />√<br />Married<br />http://bit.ly/tHork<br />√<b...
Developers are rarely an example of a typical user.<br />
one man’s treasure…<br />
3) share<br />if you create new data, create an API<br />maturation of the Twitter ecosystem<br />the developer’s mindset<...
pay it forward<br />people invest heavily in APIs (learning)<br />you have one chance to make a good API and many opportun...
easy to use / hard to misuse
sufficiently powerful
must be able to evolve
appropriate to audience</li></ul>Joshua Bloch’s talk, “How to Design a Good API”<br />http://www.youtube.com/watch?v=aAb7h...
4) iterate<br />designs are never finished<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
people change<br />
5) ask & answer<br />be a part of the community<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
resources<br />Twitter API Wikihttp://apiwiki.twitter.comhttp://apiwiki.twitter.com/REST+API+Changelog (55 fixes & changes...
summary<br />final thoughts on the ecosystem<br />finding design opportunities in the Twitter ecosystem<br />
understand the past<br />
look for opportunity<br />Twellowhood<br />Aggregate<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br /...
change your mind(set)<br />
Upcoming SlideShare
Loading in...5
×

Maturation of the Twitter Ecosystem

3,841

Published on

Presentation (via pre-produced video and a Skype connection) to July 22, 2009 Tweetup in Mountain View, California.

http://www.meetup.com/TwitterMeetup/calendar/10647920/

Published in: Technology, Spiritual
2 Comments
16 Likes
Statistics
Notes
  • Great presentation! I'm the dev of a Twitter mashup (boarding.fr, I let you check!) and I learned a lot of good thing here! Thanks a lot !
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I'm having some trouble moving the middle slides in this presentation to match the audio. Apparently, once you hit save, it's difficult to get the sync editor to take your edits. It should be all better now, though.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
3,841
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
119
Comments
2
Likes
16
Embeds 0
No embeds

No notes for slide
  • Introduction* about me* Twitter API: Up and Running* Conceptual Design- UX Research (advance of product)- PRInCiPleS* Preview: History, Opportunities, Mindset
  • In The Tempest by William Shakespeare, Act II, scene i, the character of Antonio utters the phrase “what’s past is prologue”.  In Antonio’s speech, he was trying to convince the character of Sebastian to murder his sleeping father so that Sebastian could become king.  All that had happened up until then – their past – was merely a prologue to the great things to come if they went through with the deed.  A prologue was a preface to a play or novel that “set the scene” and provided some background information.
  • Transcript of "Maturation of the Twitter Ecosystem"

    1. 1. maturation of the Twitter ecosystem<br />kevinmakice (@kmakice)wednesday, july 22, 2009<br />
    2. 2. this is me<br />
    3. 3. this is me<br />10 tweets<br />5 tweets<br />my wife<br />
    4. 4. this is also me<br />Kevin Makice<br />blog: http://www.blogschmog.net<br />email: kevin@makice.net<br />twitter: kmakice<br />
    5. 5. this is what i do<br />The Explanation for Design Ex-plan-ationsEli Blevis and Martin A. Siegel (2004) <br />
    6. 6. conceptual design<br />The Explanation for Design Ex-plan-ationsEli Blevis and Martin A. Siegel (2004) <br />
    7. 7.
    8. 8. It is no longer sufficient to simply master the technical. <br />More and more, successful design requires a grounded understanding of why you are designing in the first place.<br />
    9. 9. the maturing ecosystem<br />a history lesson  <br />insights from the ecosystem  <br />iterating the developer mindset<br />
    10. 10. history of the ecosystem<br />what is past is prologue<br />maturation of the Twitter ecosystem<br />
    11. 11.
    12. 12. growing<br />November (2008) ~1,000 applications with the API <br />February (2009) ~2,000 applications with the API<br />April ~5,000 applications with the API<br />May ~10,000 applications with the API<br />
    13. 13. growing<br />November (2008) ~1,000 applications with the API <br />February (2009) ~2,000 applications with the API<br />April ~5,000 applications with the API<br />May ~10,000 applications with the API<br />Most ideas are not unique. Design is about improving upon the existing foundation of ideas.<br />
    14. 14. growing<br />November (2008) ~1,000 applications with the API <br />February (2009) ~2,000 applications with the API<br />April ~5,000 applications with the API<br />May ~10,000 applications with the API<br />Most ideas are not unique. Design is about improving upon the existing foundation of ideas.<br />Twitter Ecosystem Twinehttp://bit.ly/16Q7LP<br />
    15. 15. the pioneers<br />early applications of the API<br />maturation of the Twitter ecosystem<br />history of the ecosystem<br />
    16. 16.
    17. 17.
    18. 18.
    19. 19.
    20. 20.
    21. 21.
    22. 22. the innovators<br />applications that found a niche<br />maturation of the Twitter ecosystem<br />history of the ecosystem<br />
    23. 23.
    24. 24.
    25. 25.
    26. 26.
    27. 27.
    28. 28.
    29. 29.
    30. 30.
    31. 31.
    32. 32. the future<br />areas of current interest<br />maturation of the Twitter ecosystem<br />history of the ecosystem<br />
    33. 33.
    34. 34.
    35. 35.
    36. 36.
    37. 37. insights from the ecosystem<br />we know what we are, but know not what we may be<br />maturation of the Twitter ecosystem<br />
    38. 38. interaction cycle<br />follow network<br />me<br />stream<br />tweet<br />profile<br />aggregate<br />
    39. 39. interaction cycle<br />follow network<br />me<br />stream<br />tweet<br />profile<br />aggregate<br />
    40. 40. properties<br />Code<br />ActionScript/Flash<br />C++<br />C#/.NET<br />Java <br />Objective-C/Cocoa<br />Perl<br />PHP<br />PL/SQL<br />Python<br />Ruby<br />Scala<br />JavaScript<br />Eiffel<br />Systems<br />GoogleMaps<br />Flickr<br />YouTube<br />Amazon<br />Twitter<br />VirtualEarth<br />eBay<br />YahooMaps<br />delicious<br />Google<br />Domain<br />Artisans <br />Business<br />Clergy <br />Construction<br />Design <br />Education<br />Engineering<br />Farming<br />Government<br />Journalism<br />Legal <br />Manufacturer <br />Medical<br />Merchant <br />Students<br />Unskilled Workers <br />Platform<br />Browser<br />Desktop<br />Mashup<br />Mobile<br />Web<br />Widget<br />Most popular APIs<br />
    41. 41. properties<br />Code<br />ActionScript/Flash<br />C++<br />C#/.NET<br />Java <br />Objective-C/Cocoa<br />Perl<br />PHP<br />PL/SQL<br />Python<br />Ruby<br />Scala<br />JavaScript<br />Eiffel<br />Systems<br />GoogleMaps<br />Flickr<br />YouTube<br />Amazon<br />Twitter<br />VirtualEarth<br />eBay<br />YahooMaps<br />delicious<br />Google<br />Domain<br />Artisans <br />Business<br />Clergy <br />Construction<br />Design <br />Education<br />Engineering<br />Farming<br />Government<br />Journalism<br />Legal <br />Manufacturer <br />Medical<br />Merchant <br />Students<br />Unskilled Workers <br />Platform<br />Browser<br />Desktop<br />Mashup<br />Mobile<br />Web<br />Widget<br />The ecosystem is a multiverse.<br />Most popular APIs<br />
    42. 42. valueless questions<br />How much does the application need context?<br />How quickly is the outcome from the interaction enjoyed?<br />Is value created individually or through contributions of a user community?<br />How open is the access to the interface (public vs. private)?<br />How much does the application focus on Network, Content, or Profile?<br />Is the intended use of the application Casual or Professional?<br />Is value created from a single tweet or an aggregation of posts?<br />Is the valued information reflected or calculated?<br />
    43. 43. valueless questions<br />Does the application maintain a historical context?<br />How much does this tool support anonymity?<br />Are users inherently part of other groups, such as by industry or geography?<br />How visible is the process?<br />Does the application service developers, authors, or consumers?<br />What are the metrics needed to determine the value of use?<br />How do those metrics influence use of Twitter and suggest behavior?<br />
    44. 44. local twittersphere<br />applications helping to highlight local use<br />maturation of the Twitter ecosystem<br />insights from the ecosystem<br />
    45. 45.
    46. 46.
    47. 47.
    48. 48.
    49. 49.
    50. 50.
    51. 51. discovering opportunity<br />using valueless factors to identify gaps<br />maturation of the Twitter ecosystem<br />insights from the ecosystem<br />
    52. 52. n-factor diagrams<br />Good<br />Evil<br />Red<br />Green<br />
    53. 53. n-factor diagrams<br />Good<br />Evil<br />Red<br />Green<br />Small<br />Big<br />
    54. 54. n-factor diagrams<br />Good<br />Evil<br />Red<br />Green<br />Small<br />Big<br />Valueless terms do not judge the properties of the design.<br />
    55. 55. content<br />Where is the content focus of the tool?<br />Profile<br />Stream<br />
    56. 56. content<br />Twellowhood<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />NearbyTweets<br />Profile<br />Stream<br />
    57. 57. dataset<br />What is the range of the data set needed to create value?<br />Single<br />Aggregate<br />
    58. 58. dataset<br />Twellowhood<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />NearbyTweets<br />Single<br />Aggregate<br />
    59. 59. content-dataset<br />Aggregate<br />Stream<br />Profile<br />Single<br />
    60. 60. content-dataset<br />Twellowhood<br />Aggregate<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />NearbyTweets<br />Stream<br />Profile<br />Single<br />
    61. 61. content-dataset<br />Twellowhood<br />Aggregate<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />NearbyTweets<br />Stream<br />Profile<br />Single<br />
    62. 62. concept: city mosaic<br />Bloomington, Indiana<br />57 followers | following 94<br />Indiana professor technology student business marketing fun single happy cow Hoosier basketball<br />
    63. 63. the developer’s mindset<br />in the heart of in the head<br />maturation of the Twitter ecosystem<br />
    64. 64. 1) be secure<br />expect the unexpected<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
    65. 65.
    66. 66. best practices<br />don&apos;t store passwords (use OAuth)<br />validate incoming data / FIEO (Filter Input, Escape Output)<br />make requests over SSL<br />let your users talk to you (security@yourapp.com)<br />consider use of random tokens to prevent forgery (CSRF)<br />cap repetitious interactions (i.e. logins)<br />make use of activity logs<br />
    67. 67. best practices<br />don&apos;t store passwords (use OAuth)<br />validate incoming data / FIEO (Filter Input, Escape Output)<br />make requests over SSL<br />let your users talk to you (security@yourapp.com)<br />consider use of random tokens to prevent forgery (CSRF)<br />cap repetitious interactions (i.e. logins)<br />make use of activity logs<br />Twitter Security Best Practiceshttp://apiwiki.twitter.com/Security-Best-Practices<br />
    68. 68. 2) know your impact<br />your use is not their use<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
    69. 69. developer demographics<br />may 2009<br />18-50<br />Children<br />Married<br />Male<br />
    70. 70. developer demographics<br />may 2009<br />18-50<br />√<br />Children<br />√<br />Married<br />http://bit.ly/tHork<br />√<br />Male<br />√<br />
    71. 71.
    72. 72. Developers are rarely an example of a typical user.<br />
    73. 73. one man’s treasure…<br />
    74. 74. 3) share<br />if you create new data, create an API<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
    75. 75. pay it forward<br />people invest heavily in APIs (learning)<br />you have one chance to make a good API and many opportunities to make bad (inheritance)<br /><ul><li>easy to learn
    76. 76. easy to use / hard to misuse
    77. 77. sufficiently powerful
    78. 78. must be able to evolve
    79. 79. appropriate to audience</li></ul>Joshua Bloch’s talk, “How to Design a Good API”<br />http://www.youtube.com/watch?v=aAb7hSCtvGw<br />http://www.webresourcesdepot.com/how-to-create-an-api-10-tutorials/<br />
    80. 80. 4) iterate<br />designs are never finished<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
    81. 81.
    82. 82.
    83. 83. people change<br />
    84. 84. 5) ask & answer<br />be a part of the community<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
    85. 85.
    86. 86. resources<br />Twitter API Wikihttp://apiwiki.twitter.comhttp://apiwiki.twitter.com/REST+API+Changelog (55 fixes & changes)<br />Twitter Fan Wikihttp://twitter.pbworks.com<br />Twitter Blogs:http://blog.twitter.com, http://apiblog.twitter.com<br />Twitter Developer Communityhttp://groups.google.com/group/twitter-development-talkhttp://groups.google.com/group/twitter-api-announce<br />Follow: @twitterapi, @tweetreport, @Twitter_Tips, and @the_api_book<br />
    87. 87. summary<br />final thoughts on the ecosystem<br />finding design opportunities in the Twitter ecosystem<br />
    88. 88. understand the past<br />
    89. 89. look for opportunity<br />Twellowhood<br />Aggregate<br />Local Chirps<br />TwitterLocal<br />Happn.in<br />chirpcity<br />NearbyTweets<br />Stream<br />Profile<br />Single<br />
    90. 90. change your mind(set)<br />
    91. 91. justify design decisions<br />
    92. 92. We need food and Legos. Please give our dad a job.<br />We need food and Legos. Please hire dad to do research.<br />I’m new.<br />
    93. 93. questions?<br />Thanks!<br />Kevin Makice<br />blog: http://www.blogschmog.net<br />email: kevin@makice.net<br />twitter: kmakice<br />
    94. 94. 10,000 apps<br />Twitter Fan Wikihttp://twitter.pbworks.com/Apps<br />Twitdomhttp://twitdom.com/<br />Go2Webhttp://www.go2web20.net/#tag:twitter<br />Twitter Little Starhttp://twitterlittlestar.com/<br />140 Characters Conferencehttp://www.140conf.com/application-directory<br />Twapplicationshttp://www.twapplications.net/ <br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×