Minimize or counter digital traces?

Younghee's post about surveillance techniques tackle a very important issues wrt to digital traces:

"How would people drop out of, or at least minimize their digital traces and minimize contributing to create others’? We are probably not expecting stickers and badges showing “this person does NOT have cameras” or “this person will NOT use cameras”. One of the memorable Ubicomp conference talks was on the interesting concept of creating capture-resistant environment, preventing camera phones to take photos by overexposing photos attempted in the region covered by this technology. While I am sure there are certain types of places this technology would be very useful, I do have my doubts if there would ever be any technology successfully controlling people’s digital behaviors."

Why do I blog this? that topic is interesting because it also connects with a phenomenon Genevieve Bell described at LIFT08: the "arms race of digital deception": for every device that claims to purport to tell the truth (e.g. GPS), there is another service that allows to lie, deceit or create alibi (which is actually coming from James Katz).

So there could be two sorts of behavior: - using tools to minimize digital traces (Younghee's argument) - using tools to create counter-traces (Bell's argument)

Skateboarding readings of space

The other day I mentioned this short article I wrote in JCDecaux trend report. It was about how skateboarders "read" space, make decision about where they do skateboard or to hang out with peers. In a sense, it's about "social navigation" and what sort of "footprints in the snow" matter for skateboarders. I dug up some examples from my city ventures below. Choosing a skateboard spot according to the physical aspect of the place

For instance, in Niteroi (Brasil), that curved sidewalk is definitely an invitation to skate it:

This bench in Zürich (Switzerland) is also an obvious point of interest (from the physical point of view) but the presence of wax also attests that OTHERS are using it as a spot. The place can also be more than a physical spot as the presence of wax indicates it marking by a community. It reveals the appropriation by a click of skateboarders (and the likelihood to find them here on saturday afternoon)

Skatespot approval or how places are validated for certain activities

This "thumb-up" stickers found in front the of the University of Geneva indicates the approval of the spot by a community of skater (in that case a local shop/community):

Skateboard map

The usual paper map, for example in Lyon (France) found in a shop called Wallstreet, that depicts interesting spots to do skateboarding:

And of course, there is an on-line/participatory version, named freeyourspot, see the example of London (which not really reveal about skateboarding potential there):

Why do I blog this? of course one could use lots of other examples but I find skateboarders a very interesting target group to study spatial behavior, and how they use various techniques (from wax to participatory websites or cell phones). In this post, I tried to update some examples of how skateboarders read/navigate in space.

I find them really interesting examples IMHO of what some would refer to as "situated technologies".

Today's urban computing versus "I just want to catch a bus"

Some tough but relevant issues presented in Backbone about how technology help solve the problems of city dwellers ("Or even just tell them when a bus is coming?). An excerpt that is particularly strong (about a Microsoft urban computing project)

" So what impact does this sort of thing really have on a city? Not much, according to Austin Williams, technical editor of the Architects’ Journal and director of Future Cities, a forum that critically explores city issues. Williams, who calls such technology-driven projects indulgent, points to more urgent urban problems awaiting solutions, such as the loss of social connections between city dwellers. “The people who are inventing these technologies are creations of this fragmented society. They don’t want to have a hard argument. You need a proper political analysis,” he said. “A lot of these things are public art projects. It relates to people on an individual emotional level rather than on a group political level.” (...) What irks Williams could be the sense of playfulness in many of these urban computing projects, which is at odds with the hardheaded policy building that is the mainstay of think tanks like Future Cities. But playfulness lies at the centre of Eric Paulos’ work. (...) A trash can that regurgitates its own garbage. Cute, but how useful is it? “You can look at some of the things you do as being efficient and productive and getting things done, while some things are about wondering and reflecting and daydreaming,” Paulos said. “I am fearful that ‘city’ plus ‘technology’ equates to Wi-Fi cafés. [It should be] more about letting us radically rethink what’s possible.” "

Why do I blog this? a very interesting and critical discussion of urban computing form different angles. Especially about the techno-driven argument. That said, I am not sure it's efficient to oppose two tracks (politics/instrumentality versus art/emotional/playful) in such a caricatural way. There are big problems but instrumentality is always relevant, and some urban computing projects tackle them as well.

Also there is this interesting issue in the conclusion:

" Pollution sensors bluejacked the Bluetooth radio interfaces of nearby cell-phones with unsolicited information and Web links on pollution levels in the surrounding area. (...) because people walk quickly through city streets, by the time the device set up a connection with a nearby phone, most people had already walked out of range, eager to reach their destination. And that is a reminder for urban technologists: the biggest challenge of all is to keep pace with a fast-moving and multitasking population."

How do people use manual?

Random street encounter tonight in Geneva:

A manual for a flat-screen LCD television, obviously tossed out in a trash. Made me think about the value of manuals from technological devices. It can also be a manual on one the 3 languages (+english) of Switzerland. We have often get 3 of 4 manuals for each technological good that we buy.

Delay in technological innovation: the "MS Surface" case

Glenn Derene in Popular Mechanics address the reasons why it took so long for Microsoft Surface to be "finally here":

"Microsoft's initial plan was to put a very limited number of Surface machines in stores and hotels with demonstration software just to show what the thing could do. But now AT&T has come along and leapfrogged over that demo mode to Surface on a larger scale—and in a much more useful way. (...) What struck me at the time was that the hardest part of the project seemed to be complete (...) All that was really left was for partners to design software customizing the Surface platform to their businesses. But that part of the equation seems to have taken forever. (...) What's ironic is that Microsoft has traditionally been a software company (Surface is one of the few pieces of hardware it actually makes), and it has all the necessary programming talent to build generic templates for Surface (...) it seems that Microsoft is more interested in launching what could be a breakthrough product solely with image-conscious partners who want to use the Surface as an attention-grabbing, brand-building device (...) this particular delay was probably more a result of the bureaucracy of complex business partnerships than of any defects in the design and engineering of Surface itself. But the end result is the same: Those of us who get excited about new technologies feel disappointed, and maybe even a bit embarrassed, for our own initial enthusiasm."

Why do I blog this? The article interestingly illustrated the gap between the glamorous projected at first by a technological innovation such as Microsoft Surface and where we stand one year after (" a classic example of how a lot of hoopla followed by a long delay can drain much of the excitement out of a technological innovation"). Especially when examined in the context of other interactive surface projects (also mentioned in the PM article). That's of course a common situation in the tech industry.

Location-awareness and automation

Mobile map interactions during a rendezvous: exploring the implications of automation by Dearman, Inkpen and Truong is an interesting paper, to be published in Personal and Ubiquitous Computing, about automation and mutual location-awareness, a topic I dealt with in my PhD research. The paper describes two studies where people engaged in a rendezvous task employ location-awareness features. The authors address the role of automation in that context, to investigate its efficiency with regards to the use of the display space and the amount of manual interaction that can be reduced.

Here's a summary of the results:

"Location awareness can help facilitate a rendezvous of two or more persons. To further enhance the rendezvous experience, we conducted two complementary field studies to identify what information in a location-aware map application is important to rendezvous individuals (study 1) and to explore the use of autofocus, our automation technique to reduce user interactions with the rendezvous application while still providing relevant information to assist users with their navigation task (study 2). Overall, our results highlight the importance of maintaining the visibility of the user’s location in relation to that of their partner(s) and rendezvous location. Additionally, we show that automation is useful in the context of a rendezvous application, but that the considerations are significantly more nuanced than originally conceived. We discuss unique instances when and why the automation process broke-down or did not perform as required by users. The results of this work demonstrate the potential for automation in a location-aware rendezvous application and identify important design considerations for future work in this area."

Also the conclusion offers very relevant insights:

"Our results suggest that the visibility of key landmarks can help facilitate navigations. Prominent landmarks could be flagged by the system, or users could define custom landmarks as focus locations. Additionally, we need to consider the importance of landmarks, buildings and structures surrounding our focus area because of their importance for how we navigate. Rather than positioning the map such that a structure is only partially visible on the screen, the automation could identify the outline of the structure and position the map so it is completely visible".

Why do I blog this? I am not surprised by the conclusion (and the discussion about the nuance of automation) since... it often leads to similar issues. Moreover, the insights provided in the conclusion are interesting form a design point of view (see more in the paper)

Contribution for urban trend-report

Recently wrote a short article for a trend report of urban company JCDecaux. The whole book is called Les Audiences dans la Ville (The Audiences of the City) and addresses the new practices of people in contemporary cities. Other writers include: Fabien, Adam Greenfield, Frederic Kaplan, Daniel Kaplan, Bruno Marzloff and lots of others interesting people from the media/design/urbanism community. It's in french though.

My contribution called "social navigation in urban space" starts by describing skateboarder as an interesting metaphor for making spatial decision in the city (i.e. choosing where to go, which area to visit and "do something there"). Skateboarder indeed rely on: looking for physical spots (implicit traces like grinded or waxed sidewalks/benches), active tagging (stickers which are explicit traces), social knowledge of spots or often maps found in magazines or on the Web (community traces). Looking for a spot is, in essence, looking at the physical environment, relying on one's community or finding resources. I then describe how technological devices (gps, cell phones, digital cameras...) allow the same functions as they produce electronic traces that we can read/analyse to make spatial decisions (through social navigation). We can use the same typology:

• the implicit traces: the one that appeared because of people's activity (doing skateboard results in grinded benches, using your cell phone allow to provide digital traces to some companies).
• the explicit traces: active tagging of the environment in its ecology (graffiti, yell arrow).
• community traces: active tagging or reference to the environment on an external resource (web).

The article goes on by discussing what does that mean to have traces and what sort of urban services we can think about that can take advantage of them.

Technology conservative of face

Wandering around Verone last week made me think of various things and the picture below reminded me of Thesis 75 in "Everyware: The Dawning Age of Ubiquitous Computing".

"About all that we can properly ask for is that our technology be designed in such a way that it is conservative of face: that ubiquitous systems must not act in such a manner as would unduly embarrass or humiliate users, or expose them to ridicule or social opprobrium, in the course of normal operations (...) But we are not talking about doing away with shame. The issue at hand is preventing ubiquitous computing systems from presenting our actions to one another in too perfect a fidelity - in too high resolution, as it were - and therefore keeping us from maintaining the beneficial illusions that allow us to live as a community."

Artifacts from the past like those scale on the street (rarely seen now, or they're often here for ages) is intriguing for that matter.

Towards the next step, leaving academia

Today was my last day at Media and Design Lab and consequently at EPFL. So, I leave academia and... here's the whole story. It's been 5 years that most of my time was spent there (although other ventures such as simpliquity, LIFT and the near future laboratory also took me some time) doing a PhD in Human-Computer Interaction and a post-doc in a design/architecture lab working on various projects. So not it's time to reflect a bit abut the next step (as Julian did lately).

So, I am leaving academia and there are different reasons for that. The first thing to say is that I am not sure that I want to play the tricks of the academic game which are both about location ("in Europe is usually "you go to certain US universities for 3-X years and find another position somewhere to eventually try to get back"), publication competition and of course specialty/discipline. I guess it's here that I was a bit frustrated lately. Being a bit interdisciplinary, I don't know where to sit now: my original background was in cognitive sciences (psychology) and I did a master in Human-Computer Interaction in a psychology department (University of Geneva), and then a PhD in HCI in a Computer Science department (EPFL). My last job (research assistant in a design/architecture lab) also reflect my interest in design research. And in addition, over the course of my studies, I have been interested in having conversations with companies/think tank which turned me into a consultant and a conference organizer for LIFT. This combination of activities and interests have led me to look various overlapping domains (user experience, design research, foresight research, cognitive psychology, anthropology and ethnography, human-computer interaction, usability, etc.) and of course different methods, paradigms, authors, POV.

Looking at these another domains and methods have no doubt changed my practice and modified my interests. The sort of research I was doing 5 five years ago was mostly experimental and quant studies to address psychological implications of technologies. Starting from theoretical models, the point was to test hypothesis (H0 versus Hn), compute inferential statistics, analyse the results, see what they mean wrt to theories and at the end of the day reflect on what this means for engineers or design practitioners (the criticized "implications for design"). Very much cognitive psychology-inspired HCI. I don't really do that anymore and my research practice has been changed due to different factors:

• Having worked with video game designers in the last 7 years, I learnt how looking or building "implications for design" is different than doing cognitive psychology. I felt that their needs were less about building theories and laws about behavior but more situated account of how their technologies or environment were used, understood, appropriated. Learning more about ethnography and qualitative research was very fruitful for that matter. Of course, this does not dismiss more quant-inferential research but it seemed to me that qual+quant descriptive research was the thing they need at first.
• On the theoretical side, I was also interested in less hardcore cognitive science theories, more alternative accounts of how people make decision, do things together and use/create artifacts. Theories like Situated Action, Distributed Cognition was interesting for that matter although I don't agree with everything here. But it surely changes the way I want to conduct research.
• Having done research in ubicomp where it's impossible to carry out studies in a controlled environment (which is the pre-requisite to run experiments), I had to go for more qualitative methods.
• ...

Thus, having experienced that (and sometimes tried to make some bridges between different methods or theories), I started to doubt about where I was sitting, what sort of research tradition I'd like to adopt (top-down inferential cognitive psychology? bottom-up descriptive situated ethnomethodology?). And of course, once you're doubting... you start raising issues or questions that does not appeal to reviewers or researchers from certain tradition. Eventually, I found it hard to get back to ultra narrow-minded cognitive stuff and interdisciplinarity is sometimes recommended however not really rewarded. And i became fed up reading papers in which people don't know anything about a certain literature/methods/ideas because it's "out of their field".

So... this situation led me to to question what I was interested in: circulation of knowledge, innovation, user experience of techniques/technologies, foresight and future research can be relevant keyword in that context. Which can be defined by two vectors:

1. "User experience research": I know that sounds not very academic and rather practitioner oriented but I find it covers a lot of the issues I like to investigate through field/user studies. It's about understanding the implications of certain technologies, how they are appropriated, used, deployed, understood, etc. a a micro/meso level (not the whole society level) from a descriptive perspective that can inspire design.
2. "Foresight": doing scanning, building scenarios, describing alternative futures based on weak signal spotting. This is definitely less academic and more about diffusion of innovation but I am convinced the material gathered in (1) can be useful for this and help defining scenarios for the future. In general, foresight research rather operate at higher level (more macro, with data coming from sociology) but my point is that all these levels can be combined.

What I am interested in, oftentimes, it the cross-pollination between different worlds, making analogies between different domains and drawing issues/solutions/problems/insights form them to enrich the problem at stake. Mapping the overview, defining the problem space, finding opportunities by using various sources: meeting people, having conversations, reading academic papers, annotating books, conducting user research (from usability test to ethnographical studies), taking weird pictures or writing about all of this. This is why I am interested in foresight research since it's rather about this sort of macro perspective than the more narrow POV of scientific research.

What does that mean for the next? Simply that I will have, from now on, 2 affiliations: being a consultant/conference organizer at LIFTlab and a researcher at the Near Future Laboratory. In the end, it's about being involved in a "think-tank" stance: smaller, more flexible, less about ivory-tower and silos. That said I will still have one foot in academia through teaching HCI and user experience research in different institutions; and I am still working on academic publications.

We are currently in the process of defining the services we will provide ranging from providing strategic review of projects, writing foresight research report, conducting user studies, organizing workshops (or participating in workshops), lecturing, teaching and organizing conferences. And my focus will remain in my areas of expertise are: urban and mobile computing, networked objects and tangible interfaces. Any interest in collaborating? Need someone like me for a specific gig? feel free to ping me.

In the meantime, thanks Jef and all the LDM team for this fruitful year!

Paul Saffo's Long Now talk

Paul Saffo's talk at the Long Now Foundation (MP3 here) is a very good overview of foresight research heuristics/rules of thumbs/methods. Some notes:

• "Hunt of Bin Laden, experts agree, Al Qaeda leader is dead or alive" is a great forecast because it accurately captures the uncertainty of the moment. The biggest mistake is to be more certain than what the fact suggest, especially today, at this very uncertain moment in time (where indicators are going in different directions). As Peter Schwarz says: "The difference between a good forecast and reality is...a good forecast has to be believable and internally consistent"
• The job is not about predicting but rather mapping the “cone of uncertainty” on a subject. And, uncertainty means opportunity. It's a cone shape for commonsensical reasons and because uncertainty expands as you project further into the future. The important thing is to find edges: Where might they happen? There you should look for wild-cards to define the boundaries and science-fiction can be a good candidate for that matter (as well as bad press about the future).
• Change is not linear and very slow and most big technological changes take 20 years to develop ("new technologies take 20 years to have an overnight success"). This means that you need good backsight, BUT because evolution is slow, you still have time even if you miss an early indicator.
• Look then for early indicators ("prodromes" or "prodroma": an early symptom or leading indicator) as claimed by William Gibson's observation that the "future is already here, it's just not unevenly distributed". Look for indicators and things that don’t fit.
• We tend to over-estimate the speed of short-term adoption and under-estimate the diffusion of the technology ("Never mistake a clear view for a short distance"). In addition, things aren’t accelerating and every society has always complained that things were getting faster, even in the 16th century ("every generation thinks things are accelerating").
• Look at failures and cherish them (Preferably other people’s). Silicon Valley has been built on the ashes of failure. Look also for people who failed in a company and went starting their own.
• Prove yourself wrong: look for indicators that proves what you say BUT also weak signals that prove it wrong
• "Be indifferent. Don’t confuse the desired with the likely"
• Know when not to make a forecast
• The problem for forecasters is not of being wrong, it about persuading people to act on forecasts.

The Wire about design issues

Watching "The Wire - The Complete Second Season" (Ernest Dickerson), there is this interesting moment in Episode 5 (around minutes 47:00 to 47.56) where the dockers are explaining how technologies often fail. It deals with both radio-wave signals and handheld computers:

"That's cans, containers, coming off the ship, and others going back on. Now, look at the screen. Every time a can goes on or off, the computer creates a record and puts it in the permanent database.

He was saying the computer makes it hard to steal off the docks. Did our port manager tell you that right now we got 160 boxes missing off the Patapsco terminal alone? Or that last time, we inventoried the truck chassis... We came up 300 light?

No, I suppose not.

That's management for you.

Not that all of them are stolen.

You can lose a can by accident, no problem. For one thing, these hand-helds use radio waves. With all the equipment and container stacks out there... sometimes waves get knocked down. That happens, a can don't get entered.

Or, just as easy,

A checker makes the wrong entry. Either 'cause he's lazy, he's sloppy, or he's still shitfaced from the night before. Or, simpler than that, you got fat fingers. So imagine February on the docks. You're wearing Gortex gloves, trying to punch numbers on that thing."

Why do I blog this? always intrigued to find examples of such issues.

Victor Scardigli: the meaning/direction of technique

It's often when reading obscure and never translated european writers that I find the most intriguing ideas, especially when it comes to foresight and innovation. The book "Les sens de la Technique" by Victor Scardigli is no exception to this; the title is a sort of pun since "sens" in french means both "meaning" and "direction". Thus you can read the title as "The Meaning of Technique" or "Where Technique is heading", which reveals the ambivalence of technical innovation. What's intriguing here is that the author, for once, do not distinguish "techniques" and "technologies", rather taking techniques as a whole that encompass vaccines or ICTs. Above all, the book is above the gap between the expectations our societies put into innovation AND the weak consequences of the first change we can notice. After inventions and R&D processes, innovation is expected by some (especially the inventors) to diffuse in society and "impact it" (for best or for worse). Different rationales are at stake here since engineers or biologists expect Sciences to serve Progress, the reciprocal adaption of human beings and techniques and hence measure the "social impact" of their invention. On the other hands, social scientists often more convinced by the prominence of human causalities are more skeptical and think that new techniques are only tools to modify the course of time based on their own objectives.

The author then addresses how techniques and their usage evolve over time, for which he describes 3 phases in his "diffusion model" using a raft of interesting examples that I won't describe here:

1. Phase 1: The "time of prophecy and fantasy" (enthusiastic or terrifying) where revolutions are predicted and technique is "inserted socially" (right after invention and R&D). It's mostly the time of positivists and the moment where imaginary symbols are constituted. The less objective fact you have, the more imaginary you get, so irrational thoughts are important here. Prophecies (or social actors who promote them) attempt to create a connection between 3 elements: the new technical object, human desire and expectations/fear of the time being. This leads to imaginary representations that you can find in the discourse of companies promoting the innovation, surveys or advertising/media messages. For Scardigli, there are of course constant imaginary issues: power on constraints (liberty of slavery), knowledge, fear of death, social justice, social bounds, economical wealth and global solidarity. There is therefore a discourse around the hopes and fears linked to these issues which are recurring in history. What happen is that fantasy, scientific knowledge and actions are intertwined and even the weakest signal is turned into an excessive hope or fear. Prophecies become necessities and then self-justificated.
2. Phase 2: The "delusion phase" that suggest how the expected technological revolution does not lead to a social revolution. Positivists' prominence is obscured by skeptical voices who raise the gap between forecasts and realizations/effects. They also reveal how "techniques" themselves are not sufficient to change "society". To some extent, observers realize that science only make progress... in science. It's of course the time where "users/people" enter the scene and begin employing the technique. These small actors transform, invent new uses, hack or tweak the innovation. This appropriation and reinvention of daily life leads to a third phase.
3. Phase 3: "the side-effect phase": 30 or 40 years after, the real diffusion of the technique is effective and some social and more long term consequences appear but often different from the one expected at first (new social form, new forms of cultures or human activities). He cites an example of a sort of bulletin-board system in the 80s in French that was expected to revive surburbian communities. What happened is that technology vanished (the state program was stopped) but it allowed people to gather, meet and create "mediating" organizations that survived. In the end, the collective imaginary of progress from the 1st phase is articulated with the strategy of actors who promote the innovation. Social change appear as a side-effect of the technical innovation, not because of it. The introduction of the innovation acts as a "analyser" revealing problems, social dynamic, aspirations, needs and above all as an alibi for new forms of sociality. And at the end of the road, it's end-users themselves who give sense to techniques by integrating to their daily life/culture.

Also Scardigli raises the importance of the socio-cultural context of innovation, who often fail without it. He exemplify this with a description of "mediating" persons who are social actors who can promote technologies and make people understand how it will be of interest for their purposes/life. In addition, there is of course a compromise between the Ideal of the project and the economic/user realism. If what happen in the 3rd phase is different than what was expected in the first one, it's because big actors (States, companies) are struggling with each others with different visions BUT also because small actors (users!) modify, change, tweak or slow down the unfolding of these innovation.

Finally, in his conclusion, he discusses some lessons about progress and innovation:

• Human beings build their own history, sometimes by designing new techniques but often with other means (e.g. organizational). And it's not these techniques that will change or social and daily life.
• These innovation effort are always carried out over and over, as a sort of Sisyphean curse because new techniques have to articulate both Science (who likes to "discover") and social demand for a better world. Unfortunately, harmonious encounters between both is very rare and needs and innovation are scarcely matching. Technical inventions are always the fruit of a culture and inventors, engineers or users all share the will to have a better world so they try, like Sisyphe.
• Social appropriation is always slower than technical innovation. 5-10 years are needed to go from the fantasy phase to find a niche of users. 10 or 20 years are then needed so that the innovation is entirely appropriated in daily life.

Reasons for some failed futures

Being interested in technological failures, I read "Where's My Jetpack?: A Guide to the Amazing Science Fiction Future that Never Arrived" by Daniel H. Wilson. Some excerpts that I found interesting, related to causes of failures:

"Jetpack: "the development of the jetpack effectively ceased the day Wendell Moore passed away, and there are plenty of reasons why. As it turns out, the government frowns on the notion of everyday people equipped with jetpacks and the ensuing midair collisions, air range, and transformation of drunk drivers into inebriated human torpedoes. Worse yet, jeptacks are nearly useless in military applications - a soldier strapped to a jetpack is a sitting duck"

Moving sidewalk: "a few litigious pedestrians have spoiled it for the rest of us with their skull-cracking falls and attendant lawsuits"

Self-steering cars: "Obstacles abound, but without a broader understanding of the world, a robot car cannot tell the difference between a harmless clump of grass and a farmers' market. Negative obstacles, such as holes in the ground, are particularly difficult for robot cars to identify. Navigation is also more difficult in cities, where tall buildings and bridges can block crucial GPS signals and soft, delicate targets (called pedestrians) abound."

Flying car: "Merely providing the vehicles is not enough, however; if everyday people are to use them, scientists must know how to track thousands of these car-planes. And knowing is half of the battle. Collision-deterring navigation systems are key to transforming highways into skyways. Regular people just can't be trusted"

Hoverboard: "They may be perfect for cruising over flat surfaces like water, ice, or a well-manicured lawn. but they are dangerously inept on city streets".

Why do I blog this? currently collecting material about technological failures and failed (micro-)visions of the future for a project.

Tech Report about designing multi-user location-aware applications

A recent EPFL Technical report I wrote with Fabien Girardin and Pierre Dillenbourg: A Descriptive Framework to Design for Mutual Location-Awareness in Ubiquitous Computing.

"The following paper provides developers, designers and researchers of location-aware applications with a descriptive framework of applications that convey Mutual Location-Awareness. These applications rely on ubiquitous computing systems to inform people on the whereabouts of significant others. The framework describes this as a 3 steps process made of a capturing, retrieval and delivery phase. For each of these phases, it presents the implications for the users in terms of interpretations of the information. Such framework is intended to both set the design space and research questions to be answered in the field of social location-aware applications."

The paper actually gives an overview of the main issues regarding location-based services, and more specifically multi-user location-aware applications/mobile social software.

Different layers of information

Seen in Verona, Italy last week-end. Different layers of information, some official (regular signage), some more informal (badly written with Tipp-Ex, to state that drugs can be find on the right).

Another way to communicate that information is to use shoes hung onto a telephone wire as seen on the picture taken in San Francisco few years ago (but this is not more a sort of urban legend):

Anyway, this is part of an ecosystem of signs in contemporary cities that are more less perceived or understood by city-dwellers.

Old technologies which are still around

Reading this piece on ZDnet that I flagged few months ago, I stumbled across interesting figures:

• In 2007, Minitel traffic and services generated 100 Millions Euros (shared between the french provider France Telecom and third parties) through to 4000 "services" (sort of the equivalent of websites). In 1996, there were 25 000 services that generated 1 billion euros of revenues.
• 220 millions of connections in 2007, approximately 20 millions per months.
• Traffic dropped by 90% between 1996 and 2006 and by 35% between 2006 and 2007.
• There are still 1 million Minitel terminals that are active but people still access Minitel services through their PCs (2 millions do, through emulators). In 1996, there were 6.5 millions.
• Minitel terminals are still sold and - even better - manufactured by recycling old ones.
• Most of the usage are: looking up addresses/phone numbers by the mythic "3611", reverse phone directory, astrology and bets. But "minitel rose" (sex chats) have vanished.
• Professional services are very important mostly for logistics marketplace.
• 25% of the revenues comes from financial services (following stock exchanges, investments etc.)

Why do I blog this? intrigued by an object of the past that still have offer some resistance to progress. The fact that people still use minitel services through the Web is very interesting: the thing work, people have their habits and keep using the media they used for a long time.

Also it's important to note that if things/invention are slow to take off, they are also slow to die!. If there's an S-curve till a mature market for any invention, the curve is reversed the other way as well. The following paper in the NYT times the other day address this issue concerning mainframe computer which were expected to disappear ten years ago:

"What are the common traits of survivor technologies? First, it seems, there is a core technology requirement: there must be some enduring advantage in the old technology that is not entirely supplanted by the new. But beyond that, it is the business decisions that matter most: investing to retool the traditional technology, adopting a new business model and nurturing a support network of loyal customers, industry partners and skilled workers. The unfulfilled predictions of demise, experts say, tend to overestimate the importance of pure technical innovation and underestimate the role of business judgment."

Henry Petroski about design, failures and compromises

Among my readings during Easter was this "Small Things Considered: Why There Is No Perfect Design" by Henry Petroski. The whole book is about design as a compromise in response to constraints, illustrated by stories concerning automobile cup holders, duct tape, WD-40, paper cups/bags and the devices to make them, the invention of single-lever faucets, the redesign of vegetable peelers and printers. It reads a bit like a Stephen Jay-Gould book in the sense that it's highly descriptive with lots of details. Some chapters are a bit less insightful than others (the one about buying a house was a bit less interesting). And Petroski is an engineer, which gives him a certain perspective of the world. The conclusion was certainly the part that interested me most, about silos/disciplines:

"Designing and building a piece of technology is more than an application of science. In fact, relying on science alone would make it virtually impossible to design even a modest bridge. What science would be applied? The laws of mechanics tell us that forces must balance if the bridge is to stand. But what forces, and stand how? Unless inventors and engineers, designers all, can first visualize some specific kind of bridge in their mind's eye, they have nothing to which to apply the laws of science. The creation of a bridge or any other artifact requires, before anything else something imagined. Whether or not science can be applied to that mental construct is a matter of availability. It there is a body of scientific knowledge that can be applied, then it would be foolish not to exploit it. (...) In fact, "Science finds - Industry Applies - Man Conforms" will never be more than a catchy motto. The reality is "People Design - Industry Makes - Science Describes." It is the creative urge that drives the human endeavor of design, which leads to inventions, gadgets, machines, structures, systems, theories, technologies, and sciences. Both science and technology are themselves artifacts of human thought and effort."

And the last bit about failures:

"Simply put, all technology is imperfect as its creators, and we can expect that it will always be. As we can, by practice and discipline, improve our own behavior, so we can, by experience and process improve the behavior of our creations. (...) As this book has suggested, there are countless examples of technology's imperfections and limitations, from the simplest of the most complex of made things. By understanding their flaws and the limitations of the design process that created them, we can better appreciate why they are and must be imperfect. All things designed and made have to conform to constraints, have had to involve choice among competing constraints, and thus have had to involve compromise among the choices. By understanding this about the nature of design, we can better negotiate the variety of stairways that we encounter, no matter how idiosyncratic or metaphorical, taking us from one level of technology to another."

Why do I blog this? Being currently interested in "failure, possibly for a book/short piece, I am gathering sources like this. What did I learn here? all the evidences gathered in this book are meant to illustrate that "design failures" are not caused by human errors but are a side-effect of the need to make compromise between needs and constraints.

Location-based annotation

A location-based annotation that indicates when water overflowed that street in paris. Interesting marker of the past (from 1910) that aims at reminding a different state of the environment. That's the sort of Holy Grail for mobile phone service developers... who try to promote a digital equivalent to this. Where are we in 2008 wrt to this sort of system?

Intelligent use of space

How to use spare/interstitial spaces (seen in paris last monday in the RER)

Ordered versus less ordered modern cities

(clean San Diego, a vision form the future)

As stated by Mike Crang:

""as robins (1999) has pointed out, too often futuristic accounts of the electronic city are driven by a resurrected modernism that, like the Saint Simonian's of the 19th century, looks to offer transparency, efficiency, and thus social harmony. Indeed visions of the city in accelerated time-space very often assume the desirability of instantaneity and speed, in the 'real-time city'. Robins (1997) has called for a revaluation of Byzantine complexity, and social complexity rather than transparency in thinking through the city - rather than the often unthinking celebration of ordered, purified digital space that is somehow friction-free and the assumption that the absence of dirt and disorder is a good thing."

(In Crang, M. Urban Morphology and the Shaping of the Transmissible City. In: Graham, S. The Cybercities Reader. London: Routledge; 2004:129-132.)

(Puebla, Mexico)

Why do I blog this? the contradiction between the clean and almost aseptic vision of modern city (or what modern cities should be) is well described in this quote from Mike Crang. Especially when it comes to digital/physical interlinkages. Too often, it's represented as on the first picture and not as on the second one.