The Inline Interface
0 likes709 views
The document discusses the evolution of user interface interactions, emphasizing the need for social, collaborative tools that allow users to arrange and share information dynamically. It critiques traditional desktop metaphors and suggests that future interfaces should promote community and fluid information sharing. The author advocates for increased transparency and privacy considerations as technology advances, highlighting the importance of integrating information openly within these interfaces.
![[assemble][things][into][flows] user created. pseudo-coding onscreen. some tools exist for this. Yahoo! Pipes Ning](https://image.slidesharecdn.com/the-inline-interface-42/85/The-Inline-Interface-20-320.jpg)
The Inline Interface
- 1. The Inline Interface Peter Brantley May 2007 DLF
- 2. our ui interaction is simple. static request, render, read repeat
- 3. we’ve used metaphors. like libraries. putting things together. on the shelf of the browser. collecting things. my stuff.
- 4. user can arrange data with local tools. zotero.org but stuck locally. not portable. not network centric. no feedback.
- 5. not the way we think. thinking: jumble, all the time. moving, stream, wandering, often in flood prone channel through the work of others.
- 6. periodic interrogation is not natural. we are a moving network of thought. digg. del.icio.us. river of news. they be good. people use them. they are fundamentally social. social is good.
- 7. the desktop is not about selection. it needs to be about using things, community, and collaboration. OLPC is moving to a new desktop metaphor for this very reason.
- 8. src : IEEE Spectrum , “The Laptop Crusade,” April 2007
- 9. way we work. stick things here or there. try new things. keepnotestalkaboutideasputstufftogether. then we make something. share it. repeat.
- 10. how we add “we” now: mash ups. combining things in a single place. like Google’s MyMaps. » people create their own maps. » back into main search results. » distribute or publish urls.
- 12. public data. uploading datasets. like simple spreadsheets. or variety of documents. linkable. shareable.
- 16. always hard issues (that are) related dmca / rights. authorization. lock < in via aggregation.
- 17. publishers will also offer this drawing from external datasets + body of texts in their own corpus re-defines the object published. dynamic. not just “extra” content. living content. mutable content.
- 18. the ui goes social. browsers: flock. firefox (maybe). are my colleagues online? I want to share with them. (and firefox wants me too).
- 19. firefox coop (test software)
- 20. [assemble][things][into][flows] user created. pseudo-coding onscreen. some tools exist for this. Yahoo! Pipes Ning
- 23. but something more is coming. increasingly people have a different understanding of privacy want to share wide open
- 25. how we do our work transparency will increase privacy will often be absent more things will be shared
- 26. most of all people will be able to access all of it loss of privacy means more access to information more ability to conjoin it more ability to create dynamic resources
- 27. down s i d e information use is tracked advantage adheres to others inserting a few select dams in the flow of information
- 28. assume all these this: will be then what we need to build toward information integration inline with the interface and openly as possible
- 29. no answers only imaginings how can we work better ... openly & in-line
- 30. thanks !