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/
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.
8. 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.
9. the maturing ecosystem a history lesson insights from the ecosystem iterating the developer mindset
10. history of the ecosystem what is past is prologue maturation of the Twitter ecosystem
11.
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
13. 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.
14. 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
15. the pioneers early applications of the API maturation of the Twitter ecosystem history of the ecosystem
40. 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
41. 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
42. 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?
43. 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?
62. concept: city mosaic Bloomington, Indiana 57 followers | following 94 Indiana professor technology student business marketing fun single happy cow Hoosier basketball
64. 1) be secure expect the unexpected maturation of the Twitter ecosystem the developer’s mindset
65.
66. 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
67. 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
68. 2) know your impact your use is not their use maturation of the Twitter ecosystem the developer’s mindset
79. appropriate to audienceJoshua 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/
80. 4) iterate designs are never finished maturation of the Twitter ecosystem the developer’s mindset
94. 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/
Editor's Notes
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.