Maturation of the Twitter Ecosystem

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

2 comments

Comments 1 - 2 of 2 previous next Post a comment

  • + DamienGuinet Damien Guinet 4 months ago
    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 !
  • + kmakice Kevin Makice 5 months ago
    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.
Post a comment
Embed Video
Edit your comment Cancel

Notes on slide 1

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.

17 Favorites

Maturation of the Twitter Ecosystem - Presentation Transcript

  1. maturation of the Twitter ecosystem
    kevinmakice (@kmakice)wednesday, july 22, 2009
  2. this is me
  3. this is me
    10 tweets
    5 tweets
    my wife
  4. this is also me
    Kevin Makice
    blog: http://www.blogschmog.net
    email: kevin@makice.net
    twitter: kmakice
  5. this is what i do
    The Explanation for Design Ex-plan-ationsEli Blevis and Martin A. Siegel (2004)
  6. conceptual design
    The Explanation for Design Ex-plan-ationsEli Blevis and Martin A. Siegel (2004)
  7. It is no longer sufficient to simply master the technical.
    More and more, successful design requires a grounded understanding of why you are designing in the first place.
  8. the maturing ecosystem
    a history lesson 
    insights from the ecosystem 
    iterating the developer mindset
  9. history of the ecosystem
    what is past is prologue
    maturation of the Twitter ecosystem
  10. growing
    November (2008) ~1,000 applications with the API
    February (2009) ~2,000 applications with the API
    April ~5,000 applications with the API
    May ~10,000 applications with the API
  11. growing
    November (2008) ~1,000 applications with the API
    February (2009) ~2,000 applications with the API
    April ~5,000 applications with the API
    May ~10,000 applications with the API
    Most ideas are not unique. Design is about improving upon the existing foundation of ideas.
  12. growing
    November (2008) ~1,000 applications with the API
    February (2009) ~2,000 applications with the API
    April ~5,000 applications with the API
    May ~10,000 applications with the API
    Most ideas are not unique. Design is about improving upon the existing foundation of ideas.
    Twitter Ecosystem Twinehttp://bit.ly/16Q7LP
  13. the pioneers
    early applications of the API
    maturation of the Twitter ecosystem
    history of the ecosystem
  14. the innovators
    applications that found a niche
    maturation of the Twitter ecosystem
    history of the ecosystem
  15. the future
    areas of current interest
    maturation of the Twitter ecosystem
    history of the ecosystem
  16. insights from the ecosystem
    we know what we are, but know not what we may be
    maturation of the Twitter ecosystem
  17. interaction cycle
    follow network
    me
    stream
    tweet
    profile
    aggregate
  18. interaction cycle
    follow network
    me
    stream
    tweet
    profile
    aggregate
  19. properties
    Code
    ActionScript/Flash
    C++
    C#/.NET
    Java
    Objective-C/Cocoa
    Perl
    PHP
    PL/SQL
    Python
    Ruby
    Scala
    JavaScript
    Eiffel
    Systems
    GoogleMaps
    Flickr
    YouTube
    Amazon
    Twitter
    VirtualEarth
    eBay
    YahooMaps
    delicious
    Google
    Domain
    Artisans
    Business
    Clergy
    Construction
    Design
    Education
    Engineering
    Farming
    Government
    Journalism
    Legal
    Manufacturer
    Medical
    Merchant
    Students
    Unskilled Workers
    Platform
    Browser
    Desktop
    Mashup
    Mobile
    Web
    Widget
    Most popular APIs
  20. properties
    Code
    ActionScript/Flash
    C++
    C#/.NET
    Java
    Objective-C/Cocoa
    Perl
    PHP
    PL/SQL
    Python
    Ruby
    Scala
    JavaScript
    Eiffel
    Systems
    GoogleMaps
    Flickr
    YouTube
    Amazon
    Twitter
    VirtualEarth
    eBay
    YahooMaps
    delicious
    Google
    Domain
    Artisans
    Business
    Clergy
    Construction
    Design
    Education
    Engineering
    Farming
    Government
    Journalism
    Legal
    Manufacturer
    Medical
    Merchant
    Students
    Unskilled Workers
    Platform
    Browser
    Desktop
    Mashup
    Mobile
    Web
    Widget
    The ecosystem is a multiverse.
    Most popular APIs
  21. valueless questions
    How much does the application need context?
    How quickly is the outcome from the interaction enjoyed?
    Is value created individually or through contributions of a user community?
    How open is the access to the interface (public vs. private)?
    How much does the application focus on Network, Content, or Profile?
    Is the intended use of the application Casual or Professional?
    Is value created from a single tweet or an aggregation of posts?
    Is the valued information reflected or calculated?
  22. valueless questions
    Does the application maintain a historical context?
    How much does this tool support anonymity?
    Are users inherently part of other groups, such as by industry or geography?
    How visible is the process?
    Does the application service developers, authors, or consumers?
    What are the metrics needed to determine the value of use?
    How do those metrics influence use of Twitter and suggest behavior?
  23. local twittersphere
    applications helping to highlight local use
    maturation of the Twitter ecosystem
    insights from the ecosystem
  24. discovering opportunity
    using valueless factors to identify gaps
    maturation of the Twitter ecosystem
    insights from the ecosystem
  25. n-factor diagrams
    Good
    Evil
    Red
    Green
  26. n-factor diagrams
    Good
    Evil
    Red
    Green
    Small
    Big
  27. n-factor diagrams
    Good
    Evil
    Red
    Green
    Small
    Big
    Valueless terms do not judge the properties of the design.
  28. content
    Where is the content focus of the tool?
    Profile
    Stream
  29. content
    Twellowhood
    Local Chirps
    TwitterLocal
    Happn.in
    chirpcity
    NearbyTweets
    Profile
    Stream
  30. dataset
    What is the range of the data set needed to create value?
    Single
    Aggregate
  31. dataset
    Twellowhood
    Local Chirps
    TwitterLocal
    Happn.in
    chirpcity
    NearbyTweets
    Single
    Aggregate
  32. content-dataset
    Aggregate
    Stream
    Profile
    Single
  33. content-dataset
    Twellowhood
    Aggregate
    Local Chirps
    TwitterLocal
    Happn.in
    chirpcity
    NearbyTweets
    Stream
    Profile
    Single
  34. content-dataset
    Twellowhood
    Aggregate
    Local Chirps
    TwitterLocal
    Happn.in
    chirpcity
    NearbyTweets
    Stream
    Profile
    Single
  35. concept: city mosaic
    Bloomington, Indiana
    57 followers | following 94
    Indiana professor technology student business marketing fun single happy cow Hoosier basketball
  36. the developer’s mindset
    in the heart of in the head
    maturation of the Twitter ecosystem
  37. 1) be secure
    expect the unexpected
    maturation of the Twitter ecosystem
    the developer’s mindset
  38. best practices
    don't store passwords (use OAuth)
    validate incoming data / FIEO (Filter Input, Escape Output)
    make requests over SSL
    let your users talk to you (security@yourapp.com)
    consider use of random tokens to prevent forgery (CSRF)
    cap repetitious interactions (i.e. logins)
    make use of activity logs
  39. best practices
    don't store passwords (use OAuth)
    validate incoming data / FIEO (Filter Input, Escape Output)
    make requests over SSL
    let your users talk to you (security@yourapp.com)
    consider use of random tokens to prevent forgery (CSRF)
    cap repetitious interactions (i.e. logins)
    make use of activity logs
    Twitter Security Best Practiceshttp://apiwiki.twitter.com/Security-Best-Practices
  40. 2) know your impact
    your use is not their use
    maturation of the Twitter ecosystem
    the developer’s mindset
  41. developer demographics
    may 2009
    18-50
    Children
    Married
    Male
  42. developer demographics
    may 2009
    18-50

    Children

    Married
    http://bit.ly/tHork

    Male

  43. Developers are rarely an example of a typical user.
  44. one man’s treasure…
  45. 3) share
    if you create new data, create an API
    maturation of the Twitter ecosystem
    the developer’s mindset
  46. pay it forward
    people invest heavily in APIs (learning)
    you have one chance to make a good API and many opportunities to make bad (inheritance)
    • easy to learn
    • easy to use / hard to misuse
    • sufficiently powerful
    • must be able to evolve
    • appropriate to audience
    Joshua Bloch’s talk, “How to Design a Good API”
    http://www.youtube.com/watch?v=aAb7hSCtvGw
    http://www.webresourcesdepot.com/how-to-create-an-api-10-tutorials/
  47. 4) iterate
    designs are never finished
    maturation of the Twitter ecosystem
    the developer’s mindset
  48. people change
  49. 5) ask & answer
    be a part of the community
    maturation of the Twitter ecosystem
    the developer’s mindset
  50. resources
    Twitter API Wikihttp://apiwiki.twitter.comhttp://apiwiki.twitter.com/REST+API+Changelog (55 fixes & changes)
    Twitter Fan Wikihttp://twitter.pbworks.com
    Twitter Blogs:http://blog.twitter.com, http://apiblog.twitter.com
    Twitter Developer Communityhttp://groups.google.com/group/twitter-development-talkhttp://groups.google.com/group/twitter-api-announce
    Follow: @twitterapi, @tweetreport, @Twitter_Tips, and @the_api_book
  51. summary
    final thoughts on the ecosystem
    finding design opportunities in the Twitter ecosystem
  52. understand the past
  53. look for opportunity
    Twellowhood
    Aggregate
    Local Chirps
    TwitterLocal
    Happn.in
    chirpcity
    NearbyTweets
    Stream
    Profile
    Single
  54. change your mind(set)
  55. justify design decisions
  56. We need food and Legos. Please give our dad a job.
    We need food and Legos. Please hire dad to do research.
    I’m new.
  57. questions?
    Thanks!
    Kevin Makice
    blog: http://www.blogschmog.net
    email: kevin@makice.net
    twitter: kmakice
  58. 10,000 apps
    Twitter Fan Wikihttp://twitter.pbworks.com/Apps
    Twitdomhttp://twitdom.com/
    Go2Webhttp://www.go2web20.net/#tag:twitter
    Twitter Little Starhttp://twitterlittlestar.com/
    140 Characters Conferencehttp://www.140conf.com/application-directory
    Twapplicationshttp://www.twapplications.net/
SlideShare Zeitgeist 2009

+ Kevin MakiceKevin Makice Nominate

custom

1954 views, 17 favs, 7 embeds more stats

Presentation (via pre-produced video and a Skype co more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 1954
    • 1835 on SlideShare
    • 119 from embeds
  • Comments 2
  • Favorites 17
  • Downloads 83
Most viewed embeds
  • 108 views on http://blog.programmableweb.com
  • 4 views on http://www.adrianeden.com
  • 2 views on http://static.slidesharecdn.com
  • 2 views on http://feeds.feedburner.com
  • 1 views on http://www.slideshare.net

more

All embeds
  • 108 views on http://blog.programmableweb.com
  • 4 views on http://www.adrianeden.com
  • 2 views on http://static.slidesharecdn.com
  • 2 views on http://feeds.feedburner.com
  • 1 views on http://www.slideshare.net
  • 1 views on http://coptest.conseq.org.uk
  • 1 views on file://

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories