Published on September 24, 2007
Designing for Hackability
What is scary?
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.
Co-create. Faster. More creative. Truer audience ﬁt.
It’s a View Source world.
Mods signal intense user connection. Co-ownership. Health.
This will happen with or without you.
It already is.
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 trafﬁc 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? Efﬁcient?
Social networking fatigue.
Don’t make me repeat myself. Proﬁle 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.
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://ﬂickr.com/photos/ethomsen/42547012/ http://ﬂickr.com/photos/mohawk/13599814/ http://ﬂickr.com/photos/peterjlambert/97671748/ http://ﬂickr.com/photos/eti-eti/697542248/ http://ﬂickr.com/photos/grantneufeld/249572562/ http://ﬂickr.com/photos/nez/381560748/ http://ﬂickr.com/photos/technicolorcavalry/96348192/ http://ﬂickr.com/photos/freudianslip/129612709/ http://ﬂickr.com/photos/oskay/265899784/ http://www.ﬂickr.com/photos/lantzilla/244589400/ http://www.ﬂickr.com/photos/youngblog/904472102/ http://www.ﬂickr.com/photos/nic/506055341/ http://www.ﬂickr.com/photos/tcmhitchhiker/697631047/ http://www.ﬂickr.com/photos/bru/129437516/ http://www.ﬂickr.com/photos/sidehike/207826371/ http://www.ﬂickr.com/photos/estherase/13553883/ http://www.ﬂickr.com/photos/eole/380316678/ http://www.ﬂickr.com/photos/factoryjoe/26967479/ http://www.ﬂickr.com/photos/beija-ﬂor/194900377/ http://www.ﬂickr.com/photos/vj_pics/623553390/
Panel: Design for Hackability Moderator: Anne Galloway Carleton University ... Designing for this kind of hackability implies considering aspects of urgency,
Brian Oberkirch has a great article about designing for "hackability" - the article tends to focus on software, but it's equally applicable for (some) hard
Design for hackability encourages designers and non-designers to critically ... designing for hackability means allowing and encouraging people to make ...
Read "Design for hackability" on DeepDyve - Instant access to the journals you need!
Dan Hill email@example.com BBC/cityofsound.com. Designing for Hackability. Context. Context. BBC Radio & Music. Hackability. Hackability. A ...
Official Full-Text Publication: Design for hackability on ResearchGate, the professional network for scientists.
I'll be part of the panel for a session called 'Design for hackability' at this year's Designing Interactive Systems conference in Cambridge, Mass. this ...
Dan Hill firstname.lastname@example.org BBC/cityofsound.com. Designing for Hackability. Context. Context. BBC Radio & Music. Hackability. Hackability. A definition.
Design for Hackability. Galloway, A., Brucker-Cohen, J., Gaye, L., Goodman, E. and Hill, D. 2004. Design for Hackability. In Proc DIS ’04: 363-366.