Adobe Revolution 2

I remain convinced that a revolution is needed.
Today there are roughly forty different applications. I have always preferred a single application, able to adapt to context through dynamic menus and tools. Facing dozens of apps—many of which I will never truly understand or use—feels like a limitation, not an advantage.

It is very different to have one unified environment that opens different files in different contexts: if I open a video, I manage the video; if I open a photo, I manage the photo. Everything stays coherent and connected, without constantly jumping from one program to another. If monetization is necessary, pricing can be differentiated by function. But pricing is a separate discussion.

Among these forty applications, however, there is a notable absence.

My view is that an “electric car” cannot simply be the same car as before, fitted with a new dashboard, different seats, and an electronic rear-view mirror. An electric car should be conceived from the ground up, starting with its body. And in fact, I would not want a rear-view mirror at all: I would want information to form dynamically on the glass itself. A communicative windshield.

Even though this example refers to automobiles, I am really speaking about a way of designing.

I am even considering letting go of many books—they take up space. Perhaps one day we will return to paper, but in the current context that space has weight and meaning. I am not against paper, nor against traditional cars. But if you are designing something, if you are evaluating space and possibilities, then you must also take into account what is futurible.