I'm blogging from the presentation designing for the personal infocloud
(my summary - . he mentions vocabulary a lot. re-use. syncing. I think an interesting thing is the granularity of content is where the design needs to happen. talk about site design, but actually each piece of content needs it's own design parameters...because more and more, structure is being applied externally, and the platform on/in which it is consumed cannot be known. Assumed but not known)
Externally structuring
(it's almost as if moving to a structure-less info space, where structure is applied externally and muteably.)
my comments in parens....
(the clickity click of people on their laptops is REALLY loud.)
the web was: navigation. proprietary. I go get.
but navigation is the wrong metaphor. we go nowhere - the information comes to us.
the personal infocloud is actually 4 clouds
global infocloud - the internet
local infocloud - community wikis, the walled AOL, location based search
external infocloud - the info you don't know - you need a problem solved but the answer is unaccessible
personal infocloud
key properties
person-centered
continuous access
organized for self
task, action and context aware.
delicious is restructuring the web based on personal vocabulary.
(de.li.ci.os is 2 for 2 in mentions in the presentations I've been in.)
seeking.recognizing.retaining.using/creating.following
focus on personal convergance
-build for use and re-use
-subscription models
-portability
-easing interaction between people and provider
(the presentations help set the context of an idea or topic. the networking that follows in the hallways and on bar stools is where the topic gets tweaked into your personal infospace, and becomes relevent through back and forth to each personal infospace.)
models of attraction - receptors
-intellectual
-perceptual
-physical
-mechanical (scraping, et. ICal, micro-formats)
Examination: Offerings
assess what you provide
Content inventory
-site structure
-page types and document types
-content object types on the pages
-related objects
-content volatility
he complains about the AIGA site's use of information being in images
(make all info scrapable)
he mentions greasemonkey
(It's interesting how all his examples have been business related 'consumer focused' sites - movies, cars.)
understanding use
Learn what people do with your information
want to do, or could do.
look beyond what people are doing and look for what people could do.
various use contexts
-what triggers use
-many environments
-actions for reuse
(actions for reuse...this seems crucial in looking for what people could do)
usable formats for content object type
what actions foollwos information use
(lots of date/time related discussion - everything so interconnected, reuse refind is crucial)
identify the gaps between what you provide and what people want
content -rss on a page rather than a site (i believe weblogs inc does this)
delivery - broadband v mobile
access
format -proprietary
notification -sms feed -( txt messaging -)(a lot of 'whats an sms feed' whispers)
gaps are opportunities to improve
current and future gaps
Design phase
Build personal scenarios
-models of attraction receptors
-location/environments
-user tasks/context
-across devices and software
Design for adaptability
-people have their own needs
Structure info for
-deep linking
(people may be dropped deep into your site)
-externally stored usage
-updates
-versioning
Externally structuring
(it's almost as if moving to a structure-less info space, where structure is applied externally and muteably.)
personal web components
-rss
-email
-sms/mms
-ical
-api
oops. too fast.
Summary -be friendly be simple. let it grow. listen, watch, embrace. get granular. test frequently.
(my summary - . he mentions vocabulary a lot. re-use. syncing. I think an interesting thing is the granularity of content is where the design needs to happen. talk about site design, but actually each piece of content needs it's own design parameters...because more and more, structure is being applied externally, and the platform on/in which it is consumed cannot be known. Assumed but not known)
Comments