Próximos SlideShares
Maturation of the Twitter Ecosystem
- 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: kmakice<br />
- 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 understanding of why you are designing in the first place.<br />
- 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 />April ~5,000 applications with the API<br />May ~10,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 />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 />
- 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 />
- 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<br />
- 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<br />
- 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 />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 />
- 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 />
- 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 />
- 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 />
- local twittersphere<br />applications helping to highlight local use<br />maturation of the Twitter ecosystem<br />insights from the ecosystem<br />
- discovering opportunity<br />using valueless factors to identify gaps<br />maturation of the Twitter ecosystem<br />insights from the ecosystem<br />
- 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 properties of the design.<br />
- 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<br />Stream<br />
- 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 />Aggregate<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 />NearbyTweets<br />Stream<br />Profile<br />Single<br />
- 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 />
- 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 />
- 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'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 />
- best practices<br />don'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 />
- 2) know your impact<br />your use is not their use<br />maturation of the Twitter ecosystem<br />the developer’s mindset<br />
- 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 />√<br />Male<br />√<br />
- 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<br />
- 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
- 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=aAb7hSCtvGw<br />http://www.webresourcesdepot.com/how-to-create-an-api-10-tutorials/<br />
- 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)<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 />
- 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 />NearbyTweets<br />Stream<br />Profile<br />Single<br />
- change your mind(set)<br />
- justify design decisions<br />
- 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 />
- questions?<br />Thanks!<br />Kevin Makice<br />blog: http://www.blogschmog.net<br />email: kevin@makice.net<br />twitter: kmakice<br />
- 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 />
Entre para ver os comentários