Consider the driverless car, as currently envisioned by Google.
That I can tell, anyway, most discussion of its prospects, whether breathlessly anticipatory or frankly horrendified, is content to weigh it more or less as given. But as I’m always harping on about, I just don’t believe we usefully understand any technology in the abstract, as it sits on a smoothly-paved pad in placid Mountain View. To garner even a first-pass appreciation for the contours of its eventual place in our lives, we have to consider what it would work like, and how people would experience it, in a specified actual context. And so here — as just such a first pass, at least — I try to imagine what would happen if autonomous vehicles like those demo’ed by Google were deployed as a service in the place I remain most familiar with, New York City.
The most likely near-term scenario is that such vehicles would be constructed as a fleet of automated taxicabs, not the more radical and frankly more interesting possibility that the service embracing them would be designed to afford truly public transit. The truth of the matter is that the arrival of the technological capability bound up in these vehicles begins to upend these standing categories…but the world can only accommodate so much novelty at once. The vehicle itself is only one component of an distributed actor-network dedicated to the accomplishment of mobility; when the autonomous vehicle begins to supplant the conventional taxi, that whole network has to restabilize around both the vehicle’s own capabilities and the ways in which those capabilities couple with other, existing actors.
In this case, that means actors like the Taxi and Limousine Commission. Enabling legislation, a body of suitable regulation, a controlling legal authority, the agreement on procedures for assessing liability to calibrate the furnishment of insurance: all of these things will need to be decided upon before any such thing as the automation of surface traffic in New York City can happen. And these provisions have a conservative effect. During the elapse of some arbitrary transitional period, anyway, they’ll tend to drag this theoretically disruptive actor back toward the categories we’re familiar with, the modes in which we’re used to the world working. That period may last months or it may last decades; there’s just no way of knowing ahead of time. But during this interregnum, we’ll approach the new thing through interfaces, metaphors and other linkages we’re already used to.
Automated taxis, as envisioned by designer Petr Kubik.
So. What can we reasonably assert of a driverless car on the Google model, when such a thing is deployed on the streets and known to its riders as a taxi?
On the plus side of the ledger:
– Black men would finally be able to hail a cab in New York City;
– So would people who use wheelchairs, folks carrying bulky packages, and others habitually and summarily bypassed by drivers;
– Sexual harassment of women riding alone would instantly cease to be an issue;
– You’d never have a driver slow as if to pick you up, roll down the window to inquire as to your destination, and only then decide it wasn’t somewhere they felt like taking you. (Yes, this is against the law, but any New Yorker will tell you it happens every damn day of the week);
– Similarly, if you happen to need a cab at 4:30, you’ll be able to catch one — getting stuck in the trenches of shift change would be a thing of the past;
– The eerily smooth ride of continuous algorithmic control will replace the lurching stop-and-go style endemic to the last few generations of NYC drivers, with everything that implies for both fuel efficiency and your ability to keep your lunch down.
These are all very good things, and they’d all be true no matter how banjaxed the service-design implementation turns out to be. (As, let’s face it, it would be: remember that we’re talking about Google here.) But as I’m fond of pointing out, none of these very good things can be had without cost. What does the flipside of the equation look like?
- Most obviously, a full-fleet replacement would immediately zero out some 50,000 jobs — mostly jobs held by immigrants, in an economy with few other decent prospects for their employment. Let’s be clear that these, while not great jobs (shitty hours, no benefits, physical discomfort, occasionally abusive customers), generate a net revenue that averages somewhere around $23/hour, and this at a time when the New York State minimum wage stands at $8/hour. These are jobs that tie families and entire communities together;
– The wholesale replacement of these drivers would eliminate one of the very few remaining contexts in which wealthy New Yorkers encounter recent immigrants and their culture at all;
– Though this is admittedly less of an issue in Manhattan, it does eliminate at least some opportunity for drivers to develop and demonstrate mastery and urban savoir faire;
– It would give Google, an advertising broker, unparalleled insight into the comings and goings of a relatively wealthy cohort of riders, and in general a dataset of enormous and irreplicable value;
– Finally, by displacing alternatives, and over the long term undermining the ecosystem of technical capabilities, human competences and other provisions that undergirds contemporary taxi service, the autonomous taxi would in time tend to bring into being and stabilize the conditions for its own perpetuation, to the exclusion of other ways of doing things that might ultimately be more productive. Of course, you could say precisely the same thing about contemporary taxis — that’s kind of the point I’m trying to make. But we should see these dynamics with clear eyes before jumping in, no?
I’m sure, quite sure, that there are weighting factors I’ve overlooked, perhaps even obvious and significant ones. This isn’t the whole story, or anything like it. There is one broadly observable trend I can’t help but noticing, however, in all the above: the benefits we stand to derive from deploying autonomous vehicles on our streets in this way are all felt in the near or even immediate term, while the costs all tend to be circumstances that only tell in the fullness of time. And we haven’t as a species historically tended to do very well with this pattern, the prime example being our experience of the automobile itself. It’s something to keep in mind.
There’s also something to be gleaned from Google’s decision to throw in their lot with Uber — an organization explicitly oriented toward the demands of the wealthy and boundlessly, even gleefully, corrosive of the public trust. And that is that you shouldn’t set your hopes on any mobility service Google builds on their autonomous-vehicle technology ever being positioned as the public accommodation or public utility it certainly could be. The decision to more tightly integrate Uber into their suite of wayfinding and journey-planning services makes it clear that for Google, the prerogative to maximize return on investment for a very few will always outweigh the interests of the communities in which they operate. And that, too, is something to keep in mind, anytime you hear someone touting all of the ways in which the clean, effortless autotaxi stands to resculpt the city.
Yes, enumerate the carriage parts — still not a carriage.
When you begin making decisions and cutting it up rules and names appear
And once names appear you should know when to stop.
- Tao te Ching, tr. M. LaFargue. (For the record, I prefer the Stephen Mitchell translation, but this seemed more pointedly relevant to the work at hand.)
I really want to recommend to you this Olivier Thereaux post about broken bus systems and how they might be fixed (and not just because I happen to be taking the MUNI a great deal lately).
What Olivier absolutely nails is the expression of a thought I’ve come back to again and again over the years: that buses and bus networks are by their nature so intimidating to potential users that many people will do just about anything to avoid engaging them. I don’t mind admitting that, depending on the city, the language in use, and my relative level of energy, I’m definitely to be numbered among those people. When buses are effectively the only mode of public transit available, that “just about anything” has occasionally meant laying out ridiculous sums on taxis; more often, it’s resulted in my walking equally absurd distances across cities I barely know.
“Intimidating,” in this context, doesn’t need to mean “terrifying.” It simply implies that the system is just complicated enough, just hard enough to form a mental model of, that the fear of winding up miles away from your intended destination — and possibly with no clear return route, not enough or the right kind of money to pay for a ticket, and no way of asking for clarification — is a real thing. There’s a threshold of comfort involved, and for quite a few categories of users (the young, the old, visitors, immigrants, people with literacy or other impairments) that threshold is set too high. People in this position wind up seeking alternatives…and if practical alternatives do not exist, they do without mobility altogether. They are lost to the city, and the city is lost to them.
The point is more broadly applicable, as well. You know I believe that cities are connection machines, networks of potential subject to Metcalfe’s law. What this means in the abstract is that the total value of an urban network rises as the square of the number of nodes connected to it. What this means in human terms is that a situation in which people are too intimidated to ride the bus (or walk down the street, or leave the apartment) is a sorrow compounded. Again: everything they could offer the network that is the city is lost. And everything we take for granted about the possibilities and promise of great urban places is foreclosed to them.
If you understand things this way, there’s a clear moral imperative inscribed in the design of systems like bus networks and interfaces. Every incremental thing the designer can do to demystify, explain, clarify, and ultimately to lower the threshold at which a potential user decides the risk of climbing aboard is worth taking does a double service — if the Metcalfe’s law construction of things rings true to you, a geometrical service. You are simultaneously improving the conditions under which an individual lives his or her life, and contributing materially to the commonweal. Not bad for a day’s work, if you ask me.
This is personal for me, too, and not just because I’ve occasionally found a route map overwhelming, or decided to walk from Bloomsbury to Dalston instead of chancing the N38 and winding up in, who knows, Calais. What I’ve come to understand, in these last few years of intense concentration on issues of urban design, is that my fascination with cities grows not at all out of ease or comfort with them, but the opposite. I’m an introvert, I’ve never been comfortable approaching strangers with questions, I’m twitchily hyperaware when I’m inconveniencing others (e.g. holding up a bus by asking questions of a driver) and my gifts for language are not great. Above all, I don’t like looking vulnerable and confused any more than anyone does, especially when traveling.
I’ve gotten better on all these counts over the course of my life, but they’re still issues. They can pop to the surface at any time, and, of course, are more likely to do so under conditions of stress. Taken together, what they spell for me is a relatively circumscribed ability to get around and enjoy the things the cities I visit have to offer — relatively, that is, compared to other able-bodied people my own age and with similar levels of privilege. Even this limitation, though, makes me acutely aware of just how difficult getting around can be, how very intimidating it can all seem, and what both people and place stand to lose each and every single time this intimidation is allowed to govern outcomes.
This is why I believe Olivier is absolutely right to focus on design interventions that reduce user stress, and, with all due respect, it’s why I think people like this Speedbird commenter, who understand cities solely as generators of upside potential, are missing something in the empathy department. There are an awful lot of people, everywhere around us, in every city, who have difficulty negotiating the mobility (and other) systems that are supposed to serve their needs. As far as I’m concerned, anyway, it is the proper and maybe even the primary task of the urban systems designer to work with compassion and fearless empathy to address this difficulty. Only by doing so can we extend the very real promise of that upside potential to the greatest possible number of people who would otherwise be denied it, in part or in full, and only by doing so can we realize in turn the full flowering of what they have to offer us.
I’m halfway through Reinventing the Automobile at the moment, which I figure represents the final comprehensive statement of Bill Mitchell’s thinking about urban mobility. As you’d imagine, it’s a passionately-held and painstakingly worked-out vision, basically the summation of all the work anyone with an interest in the space has seen in dribs and drabs over the past few years; it’s clear, for example, that this is what all the work on P.U.M.A. and MIT CityCar was informed by and leading towards.
In outline, Reinventing presents the reader with four essential propositions about the nature of next-generation urban mobility, none of which I necessarily disagree with prima facie:
- That the design principles and assumptions underlying the contemporary automobile — descended as they are, in an almost straight line, from the horseless carriage — are badly obsolete. Specifically, industry conventions regarding a vehicle’s source of motive power, drive and control mechanism, and mode of operation ought to be discarded in their entirety and replaced with ones more appropriate to an age of dense cities, networks, lightweight materials, clean energy and great personal choice.
- That mobility itself is being transformed by information; that extraordinary efficiencies can be realized and tremendous amounts of latent value unlocked if passenger, vehicle and the ground against which both are moving are reconceived as sources and brokers of, and agents upon, real-time data. (Where have I heard that before?)
- That the physical and conceptual infrastructure underlying the generation, storage and distribution of energy is also, and simultaneously, being transformed by information, with implications (again) for the generation of motive power, as well as the provision of environmental, information, communication and entertainment services to vehicles.
- That the above three developments permit (compel?) the wholesale reconceptualization of vehicles as agents in dynamic pricing markets for energy, road-space and parking resources, as well as significantly more conventional vehicle-share schemes.
It’s only that last one that I have any particular quibbles with. Even before accounting for the creepy hints of emergent AI in commodity-trading software I keep bumping up against (and that’s only meant about 75% tongue-in-cheek), I’m not at all convinced that empowering mobile software avatars to bid on road resources in tightly-coupled, nanosecond loops will ever lead to anything but the worst and most literal sort of gridlock.
But that’s not the real problem I have with this body of work. What I really tripped over, as I read, was the titanic dissonance between the MIT vision of urban life and mobility and the one that I was immersed in as I rode the 33 bus across town. It’s a cheap shot, maybe, but I just couldn’t get past the gulf between the actual San Franciscans around me — the enormous, sweet-looking Polynesian kid lost in a half-hour-long spell of autistic head-banging that took him from Oak and Stanyan clear into the Mission; the grizzled but curiously sylphlike person of frankly indeterminate gender, stepping from the bus with a croaked “God bless you, driver” — and the book’s depiction of sleekly silhouetted personae-people reclining into the Pellicle couches of their front-loading CityCars.
Any next-generation personal mobility system that didn’t take the needs and capabilities of people like these — no: these people, as individuals with lives and stories — into account…well, I can’t imagine that any such thing would be worth the very significant effort of bringing it into being. And despite some well-intentioned gestures toward the real urban world in the lattermost part of the book, projected mobility-on-demand sitings for Taipei and so on, there’s very little here that treats present-day reality as anything but something that Shall Be Overcome. It’s almost as if the very, very bright people responsible for Reinventing the Automobile have had to fend off any taint of human frailty, constraint or limitation in order to haul their total vision up into the light. (You want to ask, particularly, if any of them had ever read Aramis.)
Weirdly enough, the whiff of Gesamtkunstwerk I caught off of Reinventing reminded me of nothing so much as a work you’d be hard-pressed to think of as anything but its polar opposite, J.H. Crawford’s Carfree Cities. That, too, is a work where an ungodly amount of effort has been lavished on detailed depictions of the clean-slate future…and that, too, strikes me as refusing to engage the world as it is.
Maybe I wind up so critical of these dueling visions of future cities and mobility in them precisely because they are total solutions, and I’m acutely aware of my own weakness for and tendency toward same. I don’t think I’d mind, at all, living in one of Crawford’s carfree places, nor can I imagine that the MIT cityscape would be anything but an improvement on the status quo (if the devil was hauled out of its details and treated to a righteous ass-whupping). But to paraphrase one of my favorite philosophers, you go to the future with the cities, vehicles and people you have, not the ones you want. I have to imagine — have to — that the truly progressive and meaningful mobility intervention has a lot more to do with building on what people are already doing, and that’s even stipulating the four points above.
Bolt-on kits. Adaptive reuse. Provisional and experimental rezoning. Frameworks, visualizations and models that incorporate existing systems and assets, slowly revealing them (to users, planners, onlookers) to be nothing other than the weavings of a field, elements of a transmobility condition. And maybe someone whose job it is to account for everyone sidelined by the sleek little pods, left out of the renderings when the New Mobility was pitched to its sponsors.
Bottom line: this book is totally worth buying, reading and engaging if you have even the slightest interest in this topic. Its spinal arguments are very well framed, very clearly articulated, constructed in a way that makes them very difficult to mount cogent objections to…and almost certainly irrelevant to the way personal urban mobility is going to evolve, at least at the level of whole systems. And that’s the trouble, really, because so much of the value in the system described in these pages only works as a holism.
Like my every other negotiation with Bill Mitchell’s thought, including both engagements with his work and encounters in person, I want to be convinced. I want to believe. I want to be seduced by the optimism and the confidence that these are the right answers. But ultimately, as on those other occasions, I’m left with the sense that there are some important questions that have gone unasked, and which could not in any event have been satisfactorily answered in the framework offered. It may or may not say more about me than it does about anything else, but I just can’t see how the folks on the 33 Stanyan fit into the MIT futurama.
Google’s recent announcement of App Inventor is one of those back-to-the-future moments that simultaneously stirs up all kinds of furtive and long-suppressed hope in my heart…and makes me wonder just what the hell has taken so long, and why what we’re being offered is still so partial and wide of the mark.
I should explain. At its simplest, App Inventor does pretty much what it says on the tin. The reason it’s generating so much buzz is because it offers the non-technically inclined, non-coders among us an environment in which we can use simple visual tools to create reasonably robust mobile applications from scratch — in this case, applications for the Android operating system.
In this, it’s another step toward a demystification and user empowerment that had earlier been gestured at by scripting environments like Apple’s Automator and (to a significantly lesser degree) Yahoo! Pipes. But you used those things to perform relatively trivial manipulations on already-defined processes. I don’t want to overstate its power, especially without an Android device of my own to try the results on, but by contrast you use App Inventor to make real, usable, reusable applications, at a time when we understand our personal devices to be little more than a scrim on which such applications run, and there is a robust market for them.
This is radical thing to want to do, in both senses of that word. In its promise to democratize the creation of interactive functionality, App Inventor speaks to an ambition that has largely lain dormant beneath what are now three or four generations of interactive systems — one, I would argue, that is inscribed in the rhetoric of object-oriented programming itself. If functional units of executable code can be packaged in modular units, those units in turn represented by visual icons, and those icons presented in an environment equipped with drag-and-drop physics and all the other familiar and relatively easy-to-grasp interaction cues provided us by the graphical user interface…then pretty much anybody who can plug one Lego brick into another has what it takes to build a working application. And that application can both be used “at home,” by the developer him- or herself, and released into the wild for others to use, enjoy, deconstruct and learn from.
There’s more to it than that, of course, but that’s the crux of what’s at stake here in schematic. And this is important because, for a very long time now, the corpus of people able to develop functionality, to “program” for a given system, has been dwindling as a percentage of interactive technology’s total userbase. Each successive generation of hardware from the original PC onward has expanded the userbase — sometimes, as with the transition from laptops to network-enabled phones, by an order of magnitude or more.
The result, unseemly to me, is that some five billion people on Earth have by now embraced interactive networked devices as an intimate part of their everyday lives, while the tools and languages necessary to develop software for them have remained arcane, the province of a comparatively tiny community. And the culture that community has in time developed around these tools and languages? Highly arcane — as recondite and unwelcoming, to most of us, as a klatsch of Comp Lit majors mulling phallogocentrism in Derrida and the later works of M.I.A.
A further consequence of this — unlooked-for, perhaps, but no less significant for all of that — is that the community of developers winds up having undue influence over how users conceive of interactive devices, and the kinds of things they might be used for. Alan Kay’s definition of full technical literacy, remember, was the ability to both read and write in a given medium — to create, as well as consume. And by these lights, we’ve been moving further and further away from literacy and the empowerment it so reliably entrains for a very long time now.
So an authoring environment that made creation as easy as consumption — especially one that, like View Source in the first wave of Web browsers, exposed something of how the underlying logical system functioned — would be a tremendous thing. Perhaps naively, I thought we’d get something like this with the original iPhone: a latterday HyperCard, a tool lightweight and graphic and intuitive as the device itself, but sufficiently powerful that you could make real things with it.
Maybe that doesn’t mesh with Apple’s contemporary business model, though, or stance regarding user access to deeper layers of device functionality, or whatever shoddy, paternalistic rationale they’ve cooked up this week to justify their locking iOS against the people who bought and paid for it. And so it’s fallen to Google, of all institutions, to provide us with the radically democratizing thing; the predictable irony, of course, is that in look and feel, the App Inventor composition wizard is so design-hostile, so Google-grade that only the kind of engineer who’s already comfortable with more rigorous development alternatives is likely to find it appealing. The idea is, mostly, right…but the execution is so very wrong.
There’s a deeper issue still, though, which is why I say “mostly right.” Despite applauding any and every measure that democratizes access to development tools, in my heart of hearts I actually think “apps” are a moribund way of looking at things. That the “app economy” is a dead end, and that even offering ordinary people the power to develop real applications is something of a missed opportunity.
Maybe that’s my own wishful thinking: I was infected pretty early on with the late Jef Raskin’s way of thinking about interaction, as explored in his book The Humane Interface and partially instantiated in the Canon Cat. What I took from my reading of Raskin is the notion that chunking up the things we do into hard, modal “applications” — each with a discrete user interface, each (still!) requiring time to load, each presenting us with a new learning curve — is kind of foolish, especially when there are a core set of operations that will be common to virtually everything you want to do with a device. Some of this thinking survives in the form of cross-application commands like Cut, Copy and Paste, but still more of it has seemingly been left by the wayside.
There are ways in which Raskin’s ideas have dated poorly, but in others his principles are as relevant as ever. I personally believe that, if those of us who conceive of and deliver interactive experiences truly want to empower a userbase that is now on the order of billions of people, we need to take a still deeper cut at the problem. We need to climb out of the application paradigm entirely, and figure out a better and more accessible way of representing distributed computational processes and how to get information into and out of them. And we need to do this now, because we can clearly see that those interactive experiences are increasingly taking place across and between devices and platforms — at first for those of us in the developed world, and very soon now, for everyone.
In other words, I believe we need to articulate a way of thinking about interactive functionality and its development that is appropriate to an era in which virtually everyone on the planet spends some portion of their day using networked devices; to a context in which such devices and interfaces are utterly pervasive in the world, and the average person is confronted with a multiplicity of same in the course of a day; and to the cloud architecture that undergirds that context. Given these constraints, neither applications nor “apps” are quite going to cut it.
Accordingly, in my work at Nokia over the last two years, I’ve been arguing (admittedly to no discernible impact) that as a first step toward this we need to tear down the services we offer and recompose them from a kit of common parts, an ecology of free-floating, modular functional components, operators and lightweight user-interface frameworks to bind them together. The next step would then be to offer the entire world access to this kit of parts, so anyone at all might grab a component and reuse it in a context of their own choosing, to develop just the functionality they or their social universe require, recognize and relate to. If done right, then you don’t even need an App Inventor, because the interaction environment itself is the “inventor”: you grab the objects you need, and build what you want from them.
One, two, many Facebooks. Or Photoshops. Or Tripits or SketchUps or Spotifys. All interoperable, all built on a framework of common tools, all producing objects in turn that could be taken up and used by any other process in the weave.
This approach owes something to Ben Cerveny’s seminal talk at the first Design Engaged, though there he was primarily concerned with semantically-tagged data, and how an ecosystem of distributed systems might make use of it. There’s something in it that was first sparked by my appreciation of Jun Rekimoto’s Data Tiles, and it also has some underlying assumptions in common with the rhetoric around “activity streams.” What I ultimately derive from all of these efforts is the thought that we (yes: challenge that “we”) ought to be offering the power of ad-hoc process definition in a way that any one of us can wrap our heads around, which would in turn underwrite the most vibrant, fecund/ating planetary ecosystem of such processes.
In this light, Google’s App Inventor is both a wonderful thing, and a further propping-up of what I’m bound to regard as a stagnating and unhelpful paradigm. I’m both excited to see what people do with it, and more than a little saddened that this is still the conversation we’re having, here in 2010.
There is one further consideration for me here, though, that tends to soften the blow. Not that I’m at all comparing myself to them, in the slightest, but I’m acutely aware of what happens to the Ted Nelsons and Doug Engelbarts of the world. I’ve seen what comes of “visionaries” whose insight into how things ought to be done is just that little bit too far ahead of the curve, how they spend the rest of their careers (or lives) more or less bitterly complaining about how partial and unsatisfactory everything that actually does get built turned out to be. If all that happens is that App Inventor and its eventual, more aesthetically well-crafted progeny do help ordinary people build working tools, firmly within the application paradigm, I’ll be well pleased — well pleased, and no mistake. But in some deeper part of me, I’ll always know that we could have gone deeper still, taken on the greater challenge, and done better by the people who use the things we make.
We still can.
Update, 10 June 2013: Vindicated!
I’ve been in San Francisco for a day or so, on my way up to O’Reilly’s Foo Camp. This in itself is already happy-making, but when I found myself jetlagged and wide-awake in yesterday’s dawny gloaming and realized where I was (three blocks from the flagship Apple Store) and what day it was (!!), my schedule for the day was foreordained.
I performed quick ablutions, picked up a tall coffee to go, and met free-at-last Tom Coates a little after six in the morning, on what was already a nontrivial line. Lots of free energy drinks, doughnuts, and burritos and eight hours later, I was ushered into The Presence; after the usual provisioning and activation hassles, I left the store with a gorgeous, brand-spankin’-new iPhone 4.
And it truly is gorgeous, y’know? In its formal qualities, this Mk IV represents a significant advance over the last iteration — which I never cared for, as it looked and felt cheap — and a return to Jony Ive’s long-term effort to reinscribe a Ramsian design ethic in the market for 21st century consumer products. As an object, it just about cannot be faulted. Mmmmm.
Oh, but that interface. Or more particularly, the design of applications and utilities. The worrisome signs that first cropped up in the iPhone 3G Compass app, and clouded the otherwise lovely iPad interaction experience, are here in spades. What’s going on here is an unusual, unusually false and timid choice that, in the aggregate, amounts to nothing less than a renunciation of what these devices are for, how we think of them, and the ways in which they might be used.
I’m talking about the persistent skeuomorphic design cues that spoor applications like Calendar, Compass, iBooks and the truly awful Notes. The iPhone and iPad, as I argued on the launch of the original in 2007, are history’s first full-fledged everyware devices — post-PC interface devices of enormous power and grace — and here somebody in Apple’s UX shop has saddled them with the most awful and mawkish and flat-out tacky visual cues. You can credibly accuse Cupertino of any number of sins over the course of the last thirty years, but tackiness has not ordinarily numbered among them.
Dig, however, the page-curl animation (beautifully rendered, but stick-in-the-craw wrong) in iBooks. Feast your eyes on the leatherette Executive Desk Blotter nonsense going on in Notes. Open up Calendar, with its twee spiral-bound conceit, and gaze into the face of Fear. What are these but misguided coddles, patronizing crutches, interactively horseless carriages?
Lookit: a networked, digital, interactive copy of, say, the Tao Te Ching is simultaneously more and less than the one I keep on my shelf. You give up the tangible, phenomenological isness of the book, and in return you’re afforded an extraordinary new range of capabilities. Shouldn’t the interface, y’know, reflect this? A digital book read in Kindle for iPad sure does, as does a text saved to the (wonderful, indispensable) Instapaper Pro.
The same thing, of course, is true of networked, digital, interactive compasses and datebooks and notepads. If anything, the case is even less ambivalent here, because in all of these instances the digital version is all-but-unalloyed in its superiority over the analogue alternative. On the iPad, only Maps seems to have something of the quality of a true network-age cartography viewer.
I want to use the strongest language here. This is a terribly disappointing renunciation of possibility on Apple’s part, a failure to articulate an interface-design vocabulary as “futuristic” as, and harmonious with, the formal vocabulary of the physical devices themselves. One of the deepest principles of interaction design I observe is that, except in special cases, the articulation of a user interface should suggest something of a device, service or application’s capabilities and affordances. This is clearly, thoroughly and intentionally undermined in Apple’s current suite of iOS offerings.
What Apple has to do now is find the visual language that explains the difference between a networked text and a book, a networked calendar entry and a page leaf, or a networked locational fix and a compass heading, and does so for a mass audience of tens or hundreds of millions of non-science-fiction-reading, non-interface-geek human users. The current direction is inexplicable, even cowardly, and the task sketched here is by no means easy. But if anybody can do this, it’s the organization that made generations of otherwise arcane propositions comprehensible to ordinary people, that got out far enough ahead of the technology that their offerings Just Worked.
Application interfaces as effortlessly twenty-minutes-into-the-future as every other aspect of the iPad experience? Now that truly would be revolutionary and magical. I don’t think it’s too much to ask for, or to expect.
Crossposted with Do projects.
The response to the Systems/Layers walkshop we held in Wellington a few months back was tremendously gratifying, and given how much people seem to have gotten out of it we’ve been determined to set up similar events, in cities around the planet, ever since. (Previously on Do, and see participant CJ Wells’s writeup here.)
We’re fairly far along with plans to bring Systems/Layers to Barcelona in June (thanks Chris and Enric!), have just started getting into how we might do it in Taipei (thanks Sophie and TH!), and understand from e-mail inquiries that there’s interest in walkshops in Vancouver and Toronto as well. This is, of course, wonderfully exciting to us, and we’re hoping to learn as much from each of these as we did from Wellington.
What we’ve discovered is that the initial planning stages are significantly smoother if potential sponsors and other partners understand a little bit more about what Systems/Layers is, what it’s for and what people get out of it. The following is a brief summary designed to answer just these questions, and you are more than welcome to use it to raise interest in your part of the world. We’d love to hold walkshops in as many cities as are interested in having them.
Systems/Layers is a half-day “walkshop,” held in two parts. The first portion of the activity is dedicated to a slow and considered walk through a reasonably dense and built-up section of the city at hand. What we’re looking for are appearances of the networked digital in the physical, and vice versa: apertures through which the things that happen in the real world drive the “network weather,” and contexts in which that weather affects what people see, confront and are able to do.
Participants are asked to pay particular attention to:
- Places where information is being collected by the network.
– Places where networked information is being displayed.
– Places where networked information is being acted upon, either by people directly, or by physical systems that affect the choices people have available to them.
You’ll want to bring seasonally-appropriate clothing, good comfortable shoes, and a camera. We’ll provide maps of “the box,” the area through which we’ll be walking.
This portion of the day will take around 90 minutes, after which we gather in a convenient “command post” to map, review and discuss the things we’ve encountered. We allot an hour for this, but since we’re inclined to choose a command post offering reasonably-priced food and drink, discussion can go on as long as participants feel like hanging out.
Do projects’ Nurri Kim and Adam Greenfield plan and run the workshop, with the assistance of a qualified local expert/maven/mayor. (In Wellington, Tom Beard did a splendid job of this, for which we remain grateful.)
We feel the walkshop works best if it’s limited to roughly 30 participants in total, split into two teams for the walking segment and reunited for the discussion.
In order for us to bring Systems/Layers to your town, we need the sponsorship of a local arts, architecture or urbanist organization — generally, but not necessarily, a non-profit. They’ll cover the cost of our travel and accommodation, and defray these expenses by charging for participation in the walkshop. In turn, we’ll ensure both that the registration fee remains reasonable, and that one or two scholarship places are available for those who absolutely cannot afford to participate otherwise.
If you’re a representative of such an organization, and you’re interested in us putting on a Systems/Layers walkshop in your area, please get in touch. If you’re not, but you still want us to come, you could try to put together enough participants who are willing to register and pay ahead of time, so we could book flights and hotels. But really, we’ve found that the best way to do things is to approach a local gallery, community group or NGO and ask them to sponsor the event.
At least as we have it set up now, you should know that we’re not financially compensated in any way for our organization of these walkshops, beyond having our travel, accommodation and transfer expenses covered.
Our schedule tends to fill up 4-6 months ahead of time, so we’re already talking about events in the (Northern Hemisphere) spring of 2011. And of course, it’s generally cheapest to book flights and hotels well in advance. If you think Systems/Layers would be a good fit for your city, please do get in touch as soon as you possibly can. As we’ve mentioned, we’d be thrilled to work with you, and look forward to hearing from you with genuine anticipation and excitement. Wellington was amazing, Barcelona is shaping up to be pretty special, and Taipei, if we can pull it off, will be awesome. It’d mean a lot to us to add your city to this list. Thanks!
This last installment of our series (I, II) on networked mobility is more of a coda than anything else, and it goes directly to the question of systemic cost, and who bears it. (In the interest of full disclosure, I ought to mention that I’ve been having some lovely conversations with Snapper, the company that provides farecard-based payment services to the transit riders of Wellington, and now Auckland as well, and that I have a stake in the success of their endeavor.)
Any time you’re shifting atoms on the scale presented by even a small town’s transit infrastructure, there’s obviously going to be expense involved, and that has to be recovered somehow. Maintaining such a network once you’ve brought it into being? Another recurring expense, on a permanent basis. Rolling stock, of course, doesn’t grow on trees. Training and paying the front- and back-of-house staff — the people who oversee operations, design the signs, drive the trams, clean the stations, even the folks who get to snap on blue latex and haul the belligerent piss-drunks off the buses — another enormous ongoing outlay. Pensions, unplanned overtime, insurance coverage: these things don’t pay for themselves. All stipulated.
So why do I still believe that transit ought to be free to the user?
Because access to good, low- or no-cost public institutions clearly, consistently catalyzes upward social mobility. This was true in my own family — the free CUNY system was my father’s springboard out of the working class — and it continues to be quantifiably true in the context of urban transportation. The returns to society are the things most all of us, across the center of the political spectrum broadly defined, at least claim to want: greater innovation, a healthier and more empowered citizenry, and an enhanced tax base, for starters.
I’m going to make a multi-stage argument, here, first about the optimal economic design of public transit systems, and later about how the emergent networked technologies I’m most familiar with personally might best support the measures and policies I believe to be most sound. Most of what you’re about to read is bog-standard public-policy stuff; only toward the end does it veer toward the kind of Everyware-ish material regular readers of this blog will be comfortable with, and everyone else may find a little odd. Politically, its assumptions ought to be palatable to a reasonably wide swath of people, from social democrats on the center-left to pro-business Republicans on the right; with suitable modifications, anarchosyndicalists shouldn’t find too much that would give them heartburn.
- Let’s start with the unchallenged basics. Access to reliable transportation allows people to physically get to jobs, education and vital services (e.g. childcare) they might not otherwise.
- Jobs obviously have a direct effect on household wealth; post-secondary education tends to open up higher-paying employment opportunities, and generates other beneficial second-order effects; and services like reliable childcare allow people to accept (formal and informal) employment with time obligations they would not otherwise be able to accommodate.
- A regional transportation grid sufficiently supple to connect the majority of available jobs with workers rapidly and efficiently is never going to be cheap.
- The return on such an investment is, however, considerable — when savings due to reduced road and highway depreciation, etc., are considered as well as direct benefits, on the order of 2.5:1. This isn’t even remotely in the same galaxy as the kind of multiples that get VCs hot & bothered, but it’s not at all bad for a public-sector expenditure. (Note, too, that the proportion of systemic costs generally retired due to user fees is comparatively small.)
- Being able to spread the fixed costs of a transit system over a significantly expanded ridership would increase the economic efficiency of that system, and thus represent a different kind of savings. Given two types of riders — dependent, people for whom public transit is their only real option, and discretionary, folks who choose public transit over other modes only if it’s markedly cleaner, safer, more convenient, cheaper, etc. — how to maximize both?
- Increasing dependent ridership is relatively easy. I’m going to propose that a greater expansion in the number of transit riders would be achieved by reducing the cost of ridership from relatively-low to zero than by a comparable reduction from relatively-high to relatively- or even absolutely low. Another way of putting it is to say that a significant number of potential riders are dissuaded by the presence of any fare at all. (Strictly speaking, a reduction of fees to zero would be a Pareto-optimal outcome, though this is true only if we agree to consider genuine concerns like increased crowding and greater systemic wear-and-tear from higher loads as externalities. Which, of course, they are not.)
- Maxing out the number of discretionary riders is a little tougher. What both dependent and discretionary riders have in common, though, is the requirement that network apertures be located in as close proximity as is practically achievable to origins and foreseeable destinations. And here’s where the argument arcs back toward the things we we’ve been talking about over the last week, because the transmobility system described accommodates just this desire, by forging discrete modal components into coherent journeys. Trip segments dependent on more finely-grained modes like walking, shared bikes or shared cars, primary at origins and destinations, are designed to dovetail smoothly with the systems responsible for trunk segments, like buses, BRT, light rail, subways, metros and ferries.
∴ That transit system is of most social and economic value to a region which fuses the greatest number of separate transportation modes and styles into a coherent network; which minimizes friction at interline and intermodal junctures; and which does this all while presenting a cost to the rider no greater than zero.
Fully subsidizing any such system would be expensive…inarguably so, immoderately so. But if my conjecture is right — and oh, how I would love to see data addressing the question, one way or the other — a total subsidy produces disproportionate benefits even as compared to a generous subsidy. Success on this count would be the ultimate refutation of the zero-sum governance philosophy that took hold in the outsourcin’, rightsizin’ States during the 1990s, and has more recently and unaccountably migrated elsewhere. (I say “unaccountably” because you’d think people would have learned from America’s experience with what happens when you leave things in the hands of a “CEO President.” And also because, well, there hasn’t turned out to be much in the way of accountability for all of that, has there?) Municipalities ought to be conceiving of transit fees not as a potential revenue stream, but as a brake on a much bigger and more productive system.
To me, this isn’t a fantasy, but rather a matter of attending to the demands of basic social justice. For all too many, bad transport provisioning means getting fired because they couldn’t get to work on time, despite leaving the house at zero-dark-thirty. Or not getting hired in the first place, because they showed up late to the interview. Or not being able to take a job once offered, because the added expense of an extra bus trip to put the baby in daycare would burn every last cent one might otherwise eke out of a minimum-wage gig. Anyone who’s ever been trapped by circumstances like these intimately understands cascading failure in the for-want-of-a-nail mode. (Not buying it? See if you can’t dig up a copy of Barbara Ehrenreich’s seminal Nickel and Dimed.)
I’ve recently and persuasively seen privilege defined — and thanks, Mike, for digging up the link — as when one’s “social and economic networks tend to facilitate goals, rather than block them.” As I sit here right now, my mobility options are as infinitely finely grained as present-day practices and technologies can get them: which is to say that my transportation network, too, facilitates the accomplishment of whatever goal I devise for it, whether that means getting to the emergency room, my job, the SUNN O))) gig, the park or the airport. What I’ve here called “transmobility” is an opportunity to use our best available tools and insights to extend that privilege until it becomes nothing of the sort.
Finally: How do I expect my friends at Snapper to make any money, if everything I imagine above comes to pass? Even stipulating that cost to user is zero, there are multiple foreseeable transmobility models where a farecard is necessary to secure access and to string experiences together, before even considering the wide variety of non-fare-based business use cases. And anyway, my job is to help people anticipate and prepare for emerging opportunity spaces, not to artificially preserve the problem to which they are currently the best solution.
OK, I’ve gone all SUPERTRAIN on you for umpty-two-hundred words now; I need a break, and I’m sure you do too. I fully expect, though, that two or maybe even three of you will have plowed all the way to the bottom of this, and are even now preparing to launch the salvos of your corrective discipline, in an attempt to redress faulty assumptions, inflated claims & other such lacunae in my argumentation as you may stumble over. Trust me when I say that all such salvos will be welcome.
Part II of our exploration of transmobility. I want to caution you, again, that this is very much a probe.
Perhaps it’s best to start by backing up a few steps and explaining a little better what I’m trying to do here. What I’m arguing is that the simple act of getting around the city is in the process of changing — as how could it not, when both paths themselves and the vehicles that travel them are becoming endowed with the power to sense and adapt?
Accordingly, I believe we need to conceive of a networked mobility, a transmobility: one that inherently encompasses different modes, that conceptualizes urban space as a field to be traversed and provides for the maximum number of pathways through that field, that gathers up and utilizes whatever resources are available, and that delivers this potential to people in terms they understand.
Yesterday, I posed the question as to how we might devise a transmobility that met all of these conditions, while at the same time acknowledging two additional, all-but-contradictory desiderata. These were the desire, on the one hand, to smoothen out our interactions with transit infrastructure until vehicular transportation becomes as natural as putting one foot in front of another, and on the other to fracture journeys along their length such that any arbitrary point can become a node of experience and appreciation in and of itself. Any system capable of meeting these objectives would clearly present us with a limit case…but then, I believe that limits are there to be approached.
Finally, I’m addressing all of these questions from a relatively unusual disciplinary perspective, which is that of the service, interaction or experience designer. The downside of this is that I’m all but certainly disinterring matters a professional transit planner or mobility designer would regard as settled questions, while missing the terms of art or clever hacks they would call upon as second nature. But there’s a significant upside, too, which is that I’m natively conversant with the interactive systems that will increasingly condition any discussion of mobility, both respectful of their power and professionally wary of the representations of reality that reach us through them.
So petrified, the landscape grows
In addressing the questions I posed yesterday, then, I’m inclined to start by holding up for examination some of the ways in which trips, routes and journeys are currently represented by networked artifacts. Maybe there’s something that can be gleaned from these practices, whether as useful insights or musts-to-avoid.
I would start by suggesting that the proper unit of analysis for any consideration of movement through urban space has to be the whole journey. This means grasping the seemingly obvious fact that from the user’s perspective, all movement from origin to destination comprises a single, coherent journey, no matter how many times a change from mode to mode is required.
I say “seemingly obvious,” because the interactive artifacts I’m familiar with generally haven’t represented circumstances this way.
Take a simple example: a trip that involves walking to the nearest bus stop, riding the bus downtown, and finally walking from the point you alight from the bus to your ultimate destination. Some of the more supple route-planning applications already capture this kind of utterly normal experience — HopStop, for example, is quite good, at least in New York City — but you’d be surprised how many still do not. To date, they’ve tended to treat journeys in terms solely of their discrete component segments: an in-car GPS system plots automotive routes, a transit route-planner provides for trips from station to station, and so on.
But people think about movements through the city in terms that are simultaneously more personal and more holistic. We think of getting to work, stopping off to pick up a few things for dinner on the way home, or heading crosstown to meet friends for drinks.
So contemporary representations already seem well-suited to one of our criteria, in that the seams between methods of getting around are stark and clear, and perhaps even stark and clear enough to imply the self-directed moments of experience that attend a journey on either side. As far as a GPS display is generally concerned, what happens in the car stays in the car, and what happens next is up to you.
Certainly as compared to some overweening, totalizing system that aimed at doing everything and wound up doing none of it well, there’s something refreshing about this humility of ambition. On the other hand, though, such systems manifestly do not lend themselves well to depicting an important variety of end-to-end trips through the city, which are those trips that involve one or more changes of conveyance.
Think back to our rudimentary example, above. It would be useful if, for the portion of the journey on which you take the bus, that bus “understood” that it was essentially functioning as a connector, a linkage between one segment traversed on foot and another.
And this is still truer of journeys involving intermodal junctures where both traffic and the systemic requirements of timetables and schedules permit you less freedom in planning than walking or cycling might. Such journey plans need to be adjusted on the fly, drawing in data from other sources to accurately account for unfolding events as they happen, with signaling carried through to the infrastructure itself so that some delay, misrouting or rupture in the original plan results in the traveler being offered a panoply of appropriate alternatives.
What if, instead of living with the vehicle, the representational system lived with the traveler, and could move with them across and between modes? On this count, we’re obviously most of the way there already: with turn-by-turn directions provided by Google Maps, the iPhone and its Android-equipped competitors spell howling doom for the single-purpose devices offered by Garmin and TomTom. The emergence of truly ambient approaches to informatic provisioning would guarantee that a traveler never lacked for situational awareness, whether or not they had access to personal devices at any given moment.
What if we could provide these systems with enough local intelligence to “know” that a specified endpoint offers n possibilities for onward travel? What if this intelligence was informed by a city’s mesh of active public objects, so that travel times and schedules and real-time conditions could all be taken into account? And finally, instead of presenting journey segments as self-contained, what if we treated them as if they enjoyed magnet physics?
Then, should you want (or be forced by exigencies beyond your control) to alter your travel plans, you could snap out the mode you’re currently using, and swap in another that met whatever bounding constraints you specified, whether those had to do with speed or accessibility or privacy or shelter from the weather. The RATP‘s head of Prospective and Innovative Design, Georges Amar, speaks of enabling transmodality, and this is just what we begin to approach here.
The distinction I’m trying to capture is essentially the same as that Lucy Suchman drew between global, a priori plans on the one hand and situated actions on the other. The result would be a more responsive journey-planning system that, given any set of coordinates in space and time, is capable of popping its head up, having a look around and helping you determine what your best options are.
Moments in modal culture
This isn’t to say that we don’t also conceive of mobility in terms of particular modes of travel, and all the allegiances and affinities they give rise to. As Ivan Illich put it, “Tell me how fast you go, and I’ll tell you who you are.”
It’s not simply the coarser distinctions that tell, either. These shades of meaning and interpretation are crucial even among and between people who share a mode of transport: a fixie rider self-evidently has a different conception of the human-bicycle mesh than a Brompton fan does, while New Yorkers will know perfectly well what I mean if I distinguish two friends by describing them respectively as a 6 train rider and a 7 type. (Though not directly analogous, you can summon up similar images by evoking the L Taraval versus the J Church, the Yamanote-sen against the Hibiya-sen, or the 73 bus against the 15.)
Those of us who ride public transit form personal connections with our stops, our stations and even with particular linkages between lines, and I can only imagine that both our cities and our lives would be impoverished if we gave that up. But there’s no particular reason we need to; all I’m suggesting here is that the total journey needs to be represented as such by all the networked systems traversed in the course of a given outing.
Neither, in devising our transmobility system, can we afford to neglect the specificities and particularities of the component systems that furnish us with its articulated linkages. If one train line isn’t interchangeable with another in the hearts and minds of their riders, the same is true of other kinds of frameworks.
For example, we can’t merely plug some abstract shared bicycle service into the mesh of modal enablers and call it a day. Consider the differing fates of two apparently similar bike-share networks, the Parisian Vélib and Barcelona’s Bicing. In their diverging histories, we can see how differences in business model wind up percolating upward to impact level of service. By limiting the right to use Bicing to residents, by requiring that users open accounts, and having those accounts tied in to the usual variety of identification data, the system provides would-be bad actors with a strong disincentive. You’re personally liable, accountable…responsible.
There are real and problematic downsides to this approach, but the difference this set of decisions makes on the street is immediate and obvious. A rank of Vélib bikes, even in a posh neighborhood, looks like a bicyclical charnelhouse, with maybe three or four out of every five saddles reversed, in what has become Parisians’ folk indicator to one another that a particular bike is damaged to the point that it’s unavailable for use. The Bicing installations that I saw, including ones seeing very heavy use in core commercial districts, aren’t nearly as degraded.
This goes to the point I was trying to make, earlier, by contrasting the older conception of a vehicle as an object to the emergent way of understanding it as a service. Even though they may be physically identical — may draw current from the same grid, may be housed in the same lot, may present the driver with the selfsame control interface — a ZipCar Prius doesn’t function in just exactly the same way as a City CarShare Prius does. You could design a transmobility system so it accounted for either or (preferably) both…but not interchangeably.
Again, though I want to enable smooth transitions, I’m not arguing for perfect seamlessness in transit, or anything like it. Kevin Lynch reminds us, in The Image of the City, that “[a]ny breaks in transportation — nodes, decision points — are places of intensified perception.” We ought to welcome some of this heightened awareness, as a counterpoint to the automaticity that can all too easily accompany the rhythms of transit ridership, especially when experienced on a daily or twice-daily basis. On the other hand, it’s true that some of this “intensified perception” is almost certainly down to the anxiety that attends any such decision under circumstances of time pressure, human density and the urgent necessity to perform modal transitions correctly — and this is the fraction I’d argue we’d be better off designing out of transmobility.
At most, I mean for transmobility systems to bolster, not replace, human intuition. Where alternative modes or routings exist, we’re already generally pretty good at using them tactically to optimize against one or another criterion. Sometimes you know the subway’s the only way you can possibly beat the gridlock and get to your appointment on time; other times you choose a taxi instead, because you need to arrive at a meeting looking fresh and composed. One day you have the time to take the bus and daydream your way downtown, and the next it doesn’t get you nearly close enough to where you need to be.
You know this, I know this. So if we’re going to propose any technical intervention at all, it had better be something that builds on our native nous for the city, not overwrites it with autistic AI.
And before we can even begin to speak credibly of integrated mobility services, we’d need to see existing systems display some awareness of the plenitude of alternatives travelers have available to them, some understanding of all the different real-time factors likely to influence journey planning.
To take the most basic example, journey planning for walkers requires a different kind of thinking about the city than, particularly, turn-by-turn directions for drivers. This isn’t simply for the obvious reasons, like car-centric routings that represent a neighborhood as a an impenetrable thicket, a maze of one-way streets all alike, that a walker would stroll on through placidly and unconcernedly.
It’s because, as thinkers from Reyner Banham to Jane Jacobs and Kevin Lynch to Ivan Illich have reminded us — and as anyone who’s ever ridden in a car already understands quite perfectly well — velocity is something like destiny. You simply attend to different cues as a walker than you do as a driver, you notice textures of a different gauge, different things matter. And of course the same thing is true for cyclists vis à vis both walkers and drivers.
Over the past eighteen months, I’ve finally seen some first sentinel signs of this recognition trickle into consumer-grade interactive systems, but we’ve still got a long, long way to go.
A final step would be to design the built environment itself, the ground against which all journeys transpire, to accommodate transmobility. Why wouldn’t you, at least, plan and design buildings, street furniture and other hard infrastructure so they account for the fact of networked mobility services — both in terms of the hardware that underwrites their provision, and of the potential for variability, dynamism, and open-endedness they bring to the built landscape?
In other words: why shouldn’t a bus shelter be designed with a mobile application in mind, and vice versa? Why shouldn’t both be planned so as to take into account the vehicles and embedded sensors connected to the same network? When are we finally going to take this word “network” at face value?
Of course these technologies change — over time they get lighter, more powerful, cheaper. That’s why you design things to be easy-access, easily extensible, as modular as can be: so you can swap out the CAT5 cable and spool in CAT6 (or replace it with a WiMax transponder, or whatever). Nobody’s recommending that we ought to be hard-wiring the precise state of the art as it existed last Tuesday morning into our urban infrastructure. But anyone in a position of power who, going forward, greenlights the development of such infrastructures without ensuring their ability to accommodate networked digital interaction ought to be called to account by constituents at the very next opportunity.
You know I believe that we used to call “ubiquitous computing” is now, simply, real life. Anybody who cares about cities and the people who live in them can no longer afford to treat pervasively networked informatic systems as a novelty, or even a point of municipal distinction. It’s always hard to estimate and account for, let alone attach precise dollar figures to, missed opportunities, to count the spectral fruits of paths not taken. But given how intimate the relationship between an individual’s ability to get around and a region’s economic competitiveness is known to be, there is no excuse for not pursuing advantage through the adroit use of networked systems to enhance individual and collective mobility.
What we ought to be designing are systems that allow people to compose coherent journeys, working from whatever parameters make most sense to them. We need to be asking ourselves how movement through urban space will express itself (and be experienced as travelers as a cohesive experience) across the various modes, nodes and couplings that will necessarily be involved.
The challenge before us remains integrating this tangle of pressures, constraints, opportunities and affordances into coherent user-facing propositions, ones that would offer people smoother, more flexible, more graceful and more finely-grained control over their movements through urban space. Then we could, perhaps, begin to speak of a true transmobility.