Designing for Hackability
sr   bna
What is scary?
Attention scarcity.
Web apps
 are the new
screenplays.
The Internet is smarter than you are.
It’s ok if you’re not the Master of Your Domain.
Design the sandbox. Let them play.
via PeterMe
Co-create.
Faster. More creative. Truer audience fit.
It’s a View Source world.
Mods signal intense user connection.
Co-ownership. Health.
This will happen with or without you.
It already is.
scrAPIs
Users want to customize. View ads, or
not. Shift time & place. Personal mash.
Internal team hacks for speed, creativity.
Other devs want to hack. Just because.
Not a Web site.
A light-weight (like, really light)
message delivery infrastructure.
10x traffic from the API over the .com
Fan wikis. A good sign.
Some people are really, really into it.
Growth + diversity =
new monetization options.
Initial site focused on destination search.
Current site promotes tools.
How can we make social networks more
hackable? Portable? Efficient?
Social networking fatigue.
Don’t make me repeat myself.




Profile information


Friend networks.


Preferences.
Could these sites work together?
We have the technology:
Small pieces. Loosely joined.
rel = “me”
One piece at a time.
So what tools do we have to work with?
Build on open platforms & standards.
Use microformats.
Set content free.
Think multi-modal. Widgetize.
Build, document and champion uses of your APIs.
Design hackable URLs.
Teach & model the behaviors you want.
Celebrate & nourish creative hacks.
Many thanks to:
http://flickr.com/photos/ethomsen/42547012/
http://flickr.com/photos/mohawk/13599814/
http://flickr.com/photo...
brianoberkirch.com
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Designing For Hackability
Upcoming SlideShare
Loading in...5
×

Designing For Hackability

8,732

Published on

Threading API thinking throughout your Web app.

Published in: Technology, Business
4 Comments
38 Likes
Statistics
Notes
No Downloads
Views
Total Views
8,732
On Slideshare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
375
Comments
4
Likes
38
Embeds 0
No embeds

No notes for slide

Designing For Hackability

  1. 1. Designing for Hackability
  2. 2. sr bna
  3. 3. What is scary?
  4. 4. Attention scarcity.
  5. 5. Web apps are the new screenplays.
  6. 6. The Internet is smarter than you are.
  7. 7. It’s ok if you’re not the Master of Your Domain.
  8. 8. Design the sandbox. Let them play.
  9. 9. via PeterMe
  10. 10. Co-create. Faster. More creative. Truer audience fit.
  11. 11. It’s a View Source world.
  12. 12. Mods signal intense user connection. Co-ownership. Health.
  13. 13. This will happen with or without you.
  14. 14. It already is.
  15. 15. scrAPIs
  16. 16. Users want to customize. View ads, or not. Shift time & place. Personal mash.
  17. 17. Internal team hacks for speed, creativity.
  18. 18. Other devs want to hack. Just because.
  19. 19. Not a Web site. A light-weight (like, really light) message delivery infrastructure.
  20. 20. 10x traffic from the API over the .com
  21. 21. Fan wikis. A good sign.
  22. 22. Some people are really, really into it.
  23. 23. Growth + diversity = new monetization options.
  24. 24. Initial site focused on destination search.
  25. 25. Current site promotes tools.
  26. 26. How can we make social networks more hackable? Portable? Efficient?
  27. 27. Social networking fatigue.
  28. 28. Don’t make me repeat myself. Profile information Friend networks. Preferences.
  29. 29. Could these sites work together?
  30. 30. We have the technology:
  31. 31. Small pieces. Loosely joined.
  32. 32. rel = “me”
  33. 33. One piece at a time.
  34. 34. So what tools do we have to work with?
  35. 35. Build on open platforms & standards.
  36. 36. Use microformats.
  37. 37. Set content free.
  38. 38. Think multi-modal. Widgetize.
  39. 39. Build, document and champion uses of your APIs.
  40. 40. Design hackable URLs.
  41. 41. Teach & model the behaviors you want.
  42. 42. Celebrate & nourish creative hacks.
  43. 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. 44. brianoberkirch.com
  1. Gostou de algum slide específico?

    Recortar slides é uma maneira fácil de colecionar informações para acessar mais tarde.

×