Designing For Hackability

  • 8,465 views
Uploaded on

Threading API thinking throughout your Web app.

Threading API thinking throughout your Web app.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • hey there,could you please mail this across to me,it will truly assist me for my function.thank you really much.
    Sharika
    http://winkhealth.com http://financewink.com
    Are you sure you want to
    Your message goes here
  • one of the best slideshows I've seen - really learned from it.<br /><br/>
    Are you sure you want to
    Your message goes here
  • awesomest
    Are you sure you want to
    Your message goes here
  • the slides look very well designed...any chance this could be turned into a slidecast?
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
8,465
On Slideshare
0
From Embeds
0
Number of Embeds
10

Actions

Shares
Downloads
375
Comments
4
Likes
38

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Designing for Hackability
  • 2. sr bna
  • 3. What is scary?
  • 4. Attention scarcity.
  • 5. Web apps are the new screenplays.
  • 6. The Internet is smarter than you are.
  • 7. It’s ok if you’re not the Master of Your Domain.
  • 8. Design the sandbox. Let them play.
  • 9. via PeterMe
  • 10. Co-create. Faster. More creative. Truer audience fit.
  • 11. It’s a View Source world.
  • 12. Mods signal intense user connection. Co-ownership. Health.
  • 13. This will happen with or without you.
  • 14. It already is.
  • 15. scrAPIs
  • 16. Users want to customize. View ads, or not. Shift time & place. Personal mash.
  • 17. Internal team hacks for speed, creativity.
  • 18. Other devs want to hack. Just because.
  • 19. Not a Web site. A light-weight (like, really light) message delivery infrastructure.
  • 20. 10x traffic from the API over the .com
  • 21. Fan wikis. A good sign.
  • 22. Some people are really, really into it.
  • 23. Growth + diversity = new monetization options.
  • 24. Initial site focused on destination search.
  • 25. Current site promotes tools.
  • 26. How can we make social networks more hackable? Portable? Efficient?
  • 27. Social networking fatigue.
  • 28. Don’t make me repeat myself. Profile information Friend networks. Preferences.
  • 29. Could these sites work together?
  • 30. We have the technology:
  • 31. Small pieces. Loosely joined.
  • 32. rel = “me”
  • 33. One piece at a time.
  • 34. So what tools do we have to work with?
  • 35. Build on open platforms & standards.
  • 36. Use microformats.
  • 37. Set content free.
  • 38. Think multi-modal. Widgetize.
  • 39. Build, document and champion uses of your APIs.
  • 40. Design hackable URLs.
  • 41. Teach & model the behaviors you want.
  • 42. Celebrate & nourish creative hacks.
  • 43. Many thanks to: http://flickr.com/photos/ethomsen/42547012/ http://flickr.com/photos/mohawk/13599814/ http://flickr.com/photos/peterjlambert/97671748/ http://flickr.com/photos/eti-eti/697542248/ http://flickr.com/photos/grantneufeld/249572562/ http://flickr.com/photos/nez/381560748/ http://flickr.com/photos/technicolorcavalry/96348192/ http://flickr.com/photos/freudianslip/129612709/ http://flickr.com/photos/oskay/265899784/ http://www.flickr.com/photos/lantzilla/244589400/ http://www.flickr.com/photos/youngblog/904472102/ http://www.flickr.com/photos/nic/506055341/ http://www.flickr.com/photos/tcmhitchhiker/697631047/ http://www.flickr.com/photos/bru/129437516/ http://www.flickr.com/photos/sidehike/207826371/ http://www.flickr.com/photos/estherase/13553883/ http://www.flickr.com/photos/eole/380316678/ http://www.flickr.com/photos/factoryjoe/26967479/ http://www.flickr.com/photos/beija-flor/194900377/ http://www.flickr.com/photos/vj_pics/623553390/
  • 44. brianoberkirch.com