Wednesday, November 11, 2009

defining hackable architecture

Hackable Architecture

How do you make architecture that is adaptable?

  • Think of platforms, not solutions - overbuild infrastructure, underbuild features
  • Build with an architecture of layers; enable fast layers to change rapidly (learning); slower layers enable stability
  • Create seamful experiences, based around behaviour not aesthetics; often includes modular design
  • Undesigned products, or rather not overdesigned; to invite the user in, to encourage evolution
  • Define vocabularies, or basic patterns of interaction
  • Leave space to evolve (if physical/spatial, build with modular shapes which can extend easily
  • Enable users to manage the at-hand information and interactions; the surface layers
  • Create an aesthetic of ongoing process
  • This process implies that the designer provides support, engagement over time etc.
  • No comments:

    Post a Comment