Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]
44
Quoting myself from former days on Twitter: Businesses have a mental model of what they do. Businesses build software to help them do it—a concrete manifestation of their mental model. A gap always exists between these two. What makes a great software business is their ability to keep that gap very small. I think this holds up. And I still think about this idea (hence this post). Software is an implementation of human understanding — people need X, so we made Y. But people change. Businesses change. So software must also change. One of your greatest strengths will be your ability to adapt and evolve your understanding of people’s needs and implement it in your software. In a sense, technical debt is the other side of this coin of change: an inability to keep up with your own metamorphosis and understanding. In a way, you could analogize this to the conundrum of rocket science: you need fuel to get to space, but the more fuel you add, the more weight you add, and the more weight you...
4 months ago

Improve your reading experience

Logged in users get linked directly to articles resulting in a better reading experience. Please login for free, it takes less than 1 minute.

More from Jim Nielsen’s Blog

Transforming HTML With Netlify Edge Functions

I’ve long wanted the ability to create custom collections of icons from my icon gallery. Today I can browse collections of icons that share pre-defined metadata (e.g. “Show me all icons tagged as blue”) but I can’t create your own arbitrary collections of icons. That is, until now! I created a page at /lookup that allows you to specify however many id search params you want and it will pull all the matching icons into a single page. Here’s an example of macOS icons that follow the squircle shape but break out of it ever-so-slightly (something we’ll lose with macOS Tahoe). It requires a little know how to construct the URL, something I’ll address later, but it works for my own personal purposes at the moment. So how did I build it? Implementation So the sites are built with a static site generator, but this feature requires an ability to dynamically construct a page based on the icons specified in the URL, e.g. /lookup?id=foo&id=bar&id=baz How do I get that to work? I can’t statically pre-generate every possible combination[1] so what are my options? Create a “shell” page that uses JavaScript to read the search params, query a JSON API, and render whichever icons are specified in the URL. Send an HTML page with all icons over the wire, then use JavaScript to reach into the DOM and remove all icons whose IDs aren’t specified in the page URL. Render the page on the server with just the icons specified in the request URL. No. 1: this is fine, but I don’t have a JSON API for clients to query and I don’t want to create one. Plus I have to duplicate template logic, etc. I’m already rendering lists of icons in my static site generator, so can’t I just do that? Which leads me to: No. 2: this works, but I do have 2000+ icons so the resulting HTML page (I tried it) is almost 2MB if I render everything (whereas that same request for ~4 icons but filtered by the server would be like 11kb). There’s gotta be a way to make that smaller, which leads me to: No. 3: this is great, but it does require I have a “server” to construct pages at request time. Enter Netlify’s Edge Functions which allow you to easily transform an existing HTML page before it gets to the client. To get this working in my case, I: Create /lookup/index.html that has all 2000+ icons on it (trivial with my current static site generator). Create a lookup.ts edge function that intercepts the request to /lookup/index.html Read the search params for the request and get all specified icon IDs, e.g. /lookup?id=a&id=b&id=c turns into ['a','b','c'] Following Netlify’s example of transforming an HTML response, use HTMLRewriter to parse my HTML with all 2000+ icons in it then remove all icons that aren’t in my list of IDs, e.g. <a id='a'>…</a><a id='z'>…</a> might get pruned down to <a id='a'>…</a> Transform the parsed HTML back into a Response and return it to the client from the function. It took me a second to get all the Netlify-specific configurations right (put the function in ./netlify/edge-functions not ./netlify/functions, duh) but once I strictly followed all of Netlify’s rules it was working! (You gotta use their CLI tool to get things working on localhost and test it yourself.) Con-clusions I don’t particularly love that this ties me to a bespoke feature of Netlify’s platform — even though it works really well! But that said, if I ever switched hosts this wouldn’t be too difficult to change. If my new host provided control over the server, nothing changes about the URL for this page (/lookup?id=…). And if I had to move it all to the client, I could do that too. In that sense, I’m tying myself to Netlify from a developer point of view but not from an end-user point of view (everything still works at the URL-level) and I’m good with that trade-off. Just out of curiosity, I asked ChatGPT: if you have approximately 2,000 unique items, how many possible combinations of those IDs can be passed in a URL like /lookup?id=1&id=2? It said the number is 2^2000 which is “astronomically large” and “far more than atoms in the universe”. So statically pre-generating them is out of the question. ⏎ Email · Mastodon · Bluesky

2 days ago 1 votes
Little Swarming Gnats of Data

Here’s a screenshot of my inbox from when I was on the last leg of my flight home from family summer vacation: That’s pretty representative of the flurry of emails I get when I fly, e.g.: Check in now Track your bags Your flight will soon depart Your flight will soon board Your flight is boarding Information on your connecting flight Tell us how we did In addition to email, the airline has my mobile number and I have its app, so a large portion of my email notifications are also sent as 1) push notifications to my devices, as well as 2) messages to my mobile phone number. So when the plane begins boarding, for example, I’m told about it with an email, a text, and a push notification. I put up with it because I’ve tried pruning my stream of notifications from the airlines in the past, only to lose out on a vital notification about a change or delay. It feels like my two options are: Get all notifications multiple times via email, text, and in-app push. Get most notifications via one channel, but somehow miss the most vital one. All of this serendipitously coincided with me reading a recent piece from Nicholas Carr where he described these kinds of notifications as “little data”: all those fleeting, discrete bits of information that swarm around us like gnats on a humid summer evening. That feels apt, as I find myself swiping at lots of little data gnats swarming in my email, message, and notification inboxes. No wondering they call it “fly”ing 🥁 Email · Mastodon · Bluesky

3 days ago 4 votes
My Copy of The Internet Phone Book

I recently got my copy of the Internet Phone Book. Look who’s hiding on the bottom inside spread of page 32: The book is divided into a number of categories — such as “Small”, “Text”, and “Ecology” — and I am beyond flattered to be listed under the category “HTML”! You can dial my site at number 223. As the authors note, the sites of the internet represented in this book are not described by adjectives like “attention”, “competition”, and “promotion”. Instead they’re better suited by adjectives like “home”, “love”, and “glow”. These sites don’t look to impose their will on you, soliciting that you share, like, and subscribe. They look to spark curiosity, mystery, and wonder, letting you decide for yourself how to respond to the feelings of this experience. But why make a printed book listing sites on the internet? That’s crazy, right? Here’s the book’s co-author Kristoffer Tjalve in the introduction: With the Internet Phone Book, we bring the web, the medium we love dearly, and call it into a thousand-year old tradition [of print] I love that! I think the juxtaposition of websites in a printed phone book is exactly the kind of thing that makes you pause and reconsider the medium of the web in a new light. Isn’t that exactly what art is for? Kristoffer continues: Elliot and I began working on diagram.website, a map with hundreds of links to the internet beyond platform walls. We envisioned this map like a night sky in a nature reserve—removed from the light pollution of cities—inviting a sense of awe for the vastness of the universe, or in our case, the internet. We wanted people to know that the poetic internet already existed, waiting for them…The result of that conversation is what you now hold in your hands. The web is a web because of its seemingly infinite number of interconnected sites, not because of it’s half-dozen social platforms. It’s called the web, not the mall. There’s an entire night sky out there to discover! Email · Mastodon · Bluesky

5 days ago 7 votes
Becoming an Asshole

Read more about RSS Club. I’ve been reading Apple in China by Patrick McGee. There’s this part in there where he’s talking about a guy who worked for Apple and was known for being ruthless, stopping at nothing to negotiate the best deal for Apple. He was so aggressive yet convincing that suppliers often found themselves faced with regret, wondering how they got talked into a deal that in hindsight was not in their best interest.[1] One particular Apple executive sourced in the book noted how there are companies who don’t employ questionable tactics to gain an edge, but most of them don’t exist anymore. To paraphrase: “I worked with two kinds of suppliers at Apple: 1) complete assholes, and 2) those who are no longer in business.” Taking advantage of people is normalized in business on account of it being existential, i.e. “If we don’t act like assholes — or have someone on our team who will on our behalf[1] — we will not survive!” In other words: All’s fair in self-defense. But what’s the point of survival if you become an asshole in the process? What else is there in life if not what you become in the process? It’s almost comedically twisted how easy it is for us to become the very thing we abhor if it means our survival. (Note to self: before you start anything, ask “What will this help me become, and is that who I want to be?”) It’s interesting how we can smile at stories like that and think, “Gosh they’re tenacious, glad they’re on my side!” Not stopping to think for a moment what it would feel like to be on the other side of that equation. ⏎ Email · Mastodon · Bluesky

a week ago 10 votes
The Continuum From Static to Dynamic

Dan Abramov in “Static as a Server”: Static is a server that runs ahead of time. “Static” and “dynamic” don’t have to be binaries that describe an entire application architecture. As Dan describes in his post, “static” or “dynamic” it’s all just computers doing stuff. Computer A requests something (an HTML document, a PDF, some JSON, who knows) from computer B. That request happens via a URL and the response can be computed “ahead of time” or “at request time”. In this paradigm: “Static” is server responding ahead of time to an anticipated requests with identical responses. “Dynamic” is a server responding at request time to anticipated requests with varying responses. But these definitions aren’t binaries, but rather represent two ends of a spectrum. Ultimately, however you define “static” or “dynamic”, what you’re dealing with is a response generated by a server — i.e. a computer — so the question is really a matter of when you want to respond and with what. Answering the question of when previously had a really big impact on what kind of architecture you inherited. But I think we’re realizing we need more nimble architectures that can flex and grow in response to changing when a request/response cycle happens and what you respond with. Perhaps a poor analogy, but imagine you’re preparing holiday cards for your friends and family: “Static” is the same card sent to everyone “Dynamic” is a hand-written card to each individual But between these two are infinite possibilities, such as: A hand-written card that’s photocopied and sent to everyone A printed template with the same hand-written note to everyone A printed template with a different hand-written note for just some people etc. Are those examples “static” or “dynamic”? [Cue endless debate]. The beauty is that in proving the space between binaries — between what “static” means and what “dynamic” means — I think we develop a firmer grasp of what we mean by those words as well as what we’re trying to accomplish with our code. I love tools that help you think of the request/response cycle across your entire application as an endlessly-changing set of computations that happen either “ahead of time”, “just in time”, or somewhere in-between. Email · Mastodon · Bluesky

2 weeks ago 10 votes

More in design

Vita Tessera Cosmetics by DeepBlue design

VITA TESSERA COSMETICS COLLECTION Designing this skincare collection was a journey into calmness, purity, and quiet sophistication. Inspired by the...

3 hours ago 1 votes
Single-function Devices in the World of the Everything Machine

What we lost when everything became a phone, and when the phone became everything. In 2001, I took a train from Providence to Detroit. What should have been a 12-hour journey stretched into 34 when we got caught in a Buffalo blizzard. As the train sat buried in rapidly accumulating snow, bathrooms failed, food ran out, and passengers struggled to cope with their containment. I had taken along my minidisc player and just three discs, assuming I’d spend most of the trip sleeping. With nothing else to do but stay put in my seat, I got to know those three albums very, very well. I’ve maintained a relationship with them with format fluidity. Over the course of my life, I’ve had copies of them on cassette tape, originals on compact disc, more copies on MiniDisc, purchased (and pirated) .mp3, .wav, and .flac files, and access through a dozen different streaming services. Regardless of how I listen to them, I am still transported back to that snow-bound train. After nearly twenty-five years, I have come to assume that this effect would be permanent. But I never expected it to intensify — in a sudden feeling of full return to the body of my youth — like it did when I dug out my old MiniDisc player, recharged its battery, and pressed play on the very same discs I held back in 2001. The momentary flash of being back on that train, of the raw exhilaration of the cold and of being alone in it, of reinhabiting a young mind still reeling from what was formative, culture-wide shock on September 11th — it all came back. This was truly a blast from the past. In some ways, I am simply describing true nostalgia. I had a sense of return, and a mix of pleasure and pain. But unlike other times, when simply replaying some music would trigger recall, this was as if the physical objects — the player and discs themselves — contained the original moment, and turning it on and pressing play released it back into my mind. To the Everything Machine and back When Steve Jobs unveiled the first iPhone, he presented it as three essential devices in one: “an iPod, a phone, and an internet communicator.” The audience cheered at each revelation. Of course they did — who wouldn’t want to carry one device instead of three? For a citizen of the early aughts, a single, “everything machine” was the dream. The consolidation seemed like an obvious win for convenience, for progress, for the future itself. Nearly twenty years later, we can see that this convergence did more than just empty our pockets of multiple devices. It fundamentally transformed our relationship with technology and information. Today’s iPhone isn’t just a unified tool for known purposes; it has become Marshall McLuhan’s medium-as-message, reshaping not just how we do things but what we choose to do and think about, what we know and want to know, what we believe and are. I doubt even Steve Jobs, a man capable of grandiosity to the extreme, could have imagined the epistemological and ontological effects of the iPhone. This realization has been progressive. Books, films, music, and a near constant conversation have been the public reckoning with the everything machine. We grapple with our newly acquired digital addiction in as many ways as it manifests. We do everything we can to counter the everything machine. One thing I have done, mostly out of curiosity, is to go back to the single-function devices I have accumulated over the years. Some of them have been put away, turned-off for longer than they were ever out an don. Simply turning them back on has been illuminating. Each one has reactivated a memory. Each one has reminded me of what it was like to use it for the first time, back at the time at which it was the latest and greatest — when it hinted at a world to come as much as it achieved something its present required. What started as a backward-looking survey of sorts — sifting through a catalog of dusty devices and once-murky memories — revealed something unexpected: Not only did these older, limited devices create a different kind of relationship with technology, catalyzing imagination rather than just consuming attention, there is still a place for them today. For context, here’s a list of the more interesting devices I have in what is a small, personal museum of technology: A partial catalog of my personal device library Device Media Year Nintendo GameBoy Video Game Console 1989 Qualcomm QCP-860 Mobile Phone 1999 Sony CMT CP11 Desktop Audio System 2000 Sony MXD-D40 CD/MiniDisc Deck 2001 Apple iPod 1st Generation mp3 Player 2001 Handspring Visor PDA 2001 Cybiko Classic PDA 2001 Tascam MD-350 MiniDisc Player/Recorder 2001 Sony MZ-B10 Portable MiniDisc Player/Recorder 2002 Siemens C55 Mobile Phone 2002 Sony CLIÉ PEG-SJ22 PDA 2003 BlackBerry Quark Smartphone 2003 Canon PowerShot A70 Digital Camera 2003 Sony Net MD Walkman MZ-N920 Portable MiniDisc Player/Recorder 2004 Sony DCR-HC36 MiniDV Camcorder 2006 OLPC XO Laptop Computer 2007 Sony NWZ-S615F Digital Media Player 2007 Sony NWZ-A815 Digital Media Player 2007 Sony NWZ-A726 Digital Media Player 2008 Cambridge Audio CXC Compact Disc Transport 2015 Sony NW-E394 Digital Media Player 2016 Sony NW-A105 Digital Media Player 2019 Yoto Player 1st Generation Audio Player 2020 Yoto Mini Audio Player 2021 Cambridge Audio CXA81 Integrated Amplifier 2020 easier to use. But if it is a better experience for the writer, who can argue with that? After all, in a world of as many options as we have, ease is not the only measure of value; there are as many measures as there are choices. Subjective experience might as well take the lead. There is also a common worry that returning to single-purpose devices is risky — that their media is somehow more fragile than cloud-hosted digital content. But I’ve found the opposite to be true. I returned to Blu-Ray when favorite shows vanished from streaming services. I started recording voices and broadcasts to MiniDisc when I realized how many digital files I’d lost between phone upgrades. My old MiniDiscs still work perfectly, my miniDV tapes still play, my GameBoy cartridges still save games. It’s not the media that’s fragile, it’s the platform. And sometimes, the platform wasn’t fragile, the market was. MiniDisc is, again, a great example of this. The discs were more portable, robust, and more easily recordable than larger Compact Discs and the players were smaller and more fully-featured. But they ran right into mp3 players in the marketplace. The average consumer valued high capacity and convenience over audio quality and recording features. But guess which devices still work just as they did back then with less effort? The MiniDisc players. Most mp3 players that aren’t also phones require a much greater effort to use today because of their dependence upon another computer and software that hasn’t been maintained. And, unlike most devices made today, older devices are much more easily repaired and modified. Of my list above, not a single device failed to do what it was created to do. Besides comprising a museum of personal choices, these devices are a fascinating timeline of interface design. Each one represents a unique experiment in human-computer interaction, often feeling alien compared to today’s homogeneous landscape of austere, glass-fronted rectangles. Re-exploring them reminds me that just because an idea was left behind doesn’t mean it wasn’t valuable. Their diversity of approaches to simple problems suggests paths not taken, possibilities still worth considering. That the interface is physical, and in some cases, also graphical, makes for a unique combination of efficiency and sensory pleasure. Analog enthusiasts, particularly in the high-fi space, will opine on things like “knob-feel,” and they have a point. When a button, switch, or knob has been created to meet our hands and afford us fine-tuning control over something buried within a circuitboard, it creates an experience totally unlike tapping a symbol projected onto glass. It’s not that one is objectively better than another — and context obviously matters here - but no haptic engine has replicated what a switch wired with intention can do for a fingertip. Today’s smartphone reviewer’s will mention button “clickiness,” but if that’s what gets you excited, I encourage you to flip a GameBoy’s switch again and feel the click that precedes the Nintendo chime; eject a MiniDisc and feel the spring-loaded mechanisms vibration agains the palm of your hand; drag the first iPod’s clickwheel with your thumb in a way that turned a low-fi text list of titles into something with weight. Physicality is what makes a device an extension of a body. Function is what makes a device an extension of a mind. And single-function devices, I believe, do this better. By doing less, of course, they can only be so distracting. Compared to an everything machine and the permanent state of cognitive fracture they’ve created, this is something we should look back upon with more than a bit of nostalgia. We still have something to learn from a device that is intentionally limited and can fully embody that limitation. But the single-function device doesn’t just do less; it creates a different kind of mental space. A GameBoy can only play games, but this limitation means you’re fully present with what you’re doing. A miniDV camcorder might be less convenient than a smartphone for capturing video, but its dedicated purpose makes you think more intentionally about what you’re recording and why. For many contemporary enthusiasts, the limitations of old media create artifacts and effects that are now aesthetically desirable: they want the lower resolution, the glitchiness, and the blurring of old camcorders in the same way that modern digital camera users apply software-driven film emulation recipes to synthesize the effects once produced by developing physical film. The limitation heightens the creation. Each device a doorway These devices remind us that technological progress isn’t always linear. Sometimes what we gain in convenience, we lose in engagement. The friction of switching between different devices might have been — and remains — inefficient, but it created natural boundaries between different modes of activity. Each device was a doorway to a specific kind of experience, rather than a portal to endless possibility. Modern devices have their place. When it comes to remaining in communication, I wouldn’t trade my current smartphone for the phone I used twenty years ago. As critical as I am of the everything machine, I’m inclined to work on building better personal use habits than I am to replace it with a worse experience of the features I use. But there is also room for rediscovering old devices and maintaining relationships with technologies that do less. I actually prefer playing movies and music on physical media than through a streaming interface; I would jump at the chance to reimagine my smartphone with fewer features and a more analog interface. Limitations expand our experience by engaging our imagination. Unlimited options arrest our imagination by capturing us in the experience of choice. One, I firmly believe, is necessary for creativity, while the other is its opiate. Generally speaking, we don’t need more features. We need more focus. Anyone working in interaction and product design can learn from rediscovering how older devices engaged the mind and body to create an experience far more expansive than their function. The future of computing, I hope, is one that will integrate the concept of intentional limitation. I think our minds and memories will depend upon it.

3 days ago 6 votes
Roots by F/Agency

Roots — a retailer offering healthy, farm-fresh, and natural products. The project involves adapting one of Russia’s largest grocery chains...

4 days ago 5 votes
The Best Interfaces We Never Built

Five fictional interface concepts that could reshape how humans and machines interact. Every piece of technology is an interface. Though the word has come to be a shorthand for what we see and use on a screen, an interface is anything that connects two or more things together. While that technically means that a piece of tape could be considered an interface between a picture and a wall, or a pipe between water and a home, interfaces become truly exciting when they create both a physical connection and a conceptual one — when they create a unique space for thinking, communicating, creating, or experiencing. This is why, despite the flexibility and utility of multifunction devices like the smartphone, single-function computing devices still have the power to fascinate us all. The reason for this, I believe, is not just that single-function devices enable their users to fully focus on the experience they create, but because the device can be fully built for that experience. Every aspect of its physical interface can be customized to its functionality; it can have dedicated buttons, switches, knobs, and displays that directly connect our bodies to its features, rather than abstracting them through symbols under a pane of glass. A perfect example of this comes from the very company responsible for steering our culture away from single-function devices; before the iPhone, Apple’s most influential product was the iPod, which won user’s over with an innovative approach to a physical interface: the clickwheel. It took the hand’s ability for fine motor control and coupled it for the need for speed in navigating a suddenly longer list of digital files. With a subtle but feel-good gesture, you could skip through thousands of files fluidly. It was seductive and encouraged us all to make full use of the newfound capacity the iPod provided. It was good for users and good for the .mp3 business. I may be overly nostalgic about this, but no feature of the iPhone feels as good to use as the clickwheel did. Of course, that’s an example that sits right at the nexus between dedicated — old-fashioned — devices and the smartphonization of everything. Prior to the iPod, we had many single-focus devices and countless examples of physical interfaces that gave people unique ways of doing things. Whenever I use these kinds of devices — particularly physical media devices — I start to imagine alternate technological timelines. Ones where the iPhone didn’t determine two decades of interface consolidation. I go full sci-fi. Science fiction, by the way, hasn’t just predicted our technological future. We all know the classic examples, particularly those from Star Trek: the communicator and tricorder anticipated the smartphone; the PADD anticipated the tablet; the ship’s computer anticipated Siri, Alexa, Google, and AI voice interfaces; the entire interior anticipated the Jony Ive glass filter on reality. It’s enough to make a case that Trek didn’t anticipate these things so much as those who watched it as young people matured in careers in design and engineering. But science fiction has also been a fertile ground for imagining very different ways for how humans and machines interact. For me, the most compelling interface concepts from fiction are the ones that are built upon radically different approaches to human-computer interaction. Today, there’s a hunger to “get past” screen-based computer interaction, which I think is largely borne out of a preference for novelty and a desire for the riches that come from bringing an entirely new product category to market. With AI, the desire seems to be to redefine everything we’re used to using on a screen through a voice interface — something I think is a big mistake. And though I’ve written about the reasons why screens still make a lot of sense, what I want to focus on here are different interface paradigms that still make use of a physical connection between people and machine. I think we’ve just scratched the surface for the potential of physical interfaces. Here are a few examples that come to mind that represent untried or untested ideas that captivate my imagination. Multiple Dedicated Screens: 2001’s Discovery One Our current computing convention is to focus on a single screen, which we then often divide among a variety of applications. The computer workstations aboard the Discovery One in 2001: A Space Odyssey featured something we rarely see today: multiple, dedicated smaller screens. Each screen served a specific, stable purpose throughout a work session. A simple shift to physically isolating environments and distributing them makes it interesting as a choice to consider now, not just an arbitrary limitation defined by how large screens were at the time the film was produced. Placing physical boundaries between screen-based environments rather than the soft, constantly shifting divisions we manage on our widescreen displays might seem cumbersome and unnecessary at first. But I wonder what half a century of computing that way would have created differently from what we ended up with thanks to the PC. Instead of spending time repositioning and reprioritizing windows — a task that has somehow become a significant part of modern computer use — dedicated displays would allow us to assign specific screens for ambient monitoring and others for focused work. The psychological impact could be profound. Choosing which information deserves its own physical space creates a different relationship with that information. It becomes less about managing digital real estate and more about curating meaningful, persistent contexts for different types of thinking. The Sonic Screwdriver: Intent as Interface The Doctor’s sonic screwdriver from Doctor Who represents perhaps the most elegant interface concept ever imagined: a universal tool that somehow interfaces with any technology through harmonic resonance. But the really interesting aspect isn’t the pseudo-scientific explanation — it’s how the device responds to intent rather than requiring learned commands or specific inputs. The sonic screwdriver suggests technology that adapts to human purpose rather than forcing humans to adapt to machine constraints. Instead of memorizing syntax, keyboard shortcuts, or navigation hierarchies, the user simply needs to clearly understand what they want to accomplish. The interface becomes transparent, disappearing entirely in favor of direct intention-to-result interaction. This points toward computing that works more like natural tool use — the way a craftsperson uses a hammer or chisel — where the tool extends human capability without requiring conscious attention to the tool itself. The Doctor’s screwdriver may, at this point, be indistinguishable from magic, but in a future with increased miniaturization, nanotech, and quantum computing, a personal device shaped by intent could be possible. Al’s Handlink: The Mind-Object In Quantum Leap, Al’s handlink device looks like a smartphone-sized Mondrian painting: no screen, no discernible buttons, just blocky areas of color that illuminate as he uses it. As the show progressed, the device became increasingly abstract until it seemed impossible that any human could actually operate it. But perhaps that’s the point. The handlink might represent a complete paradigm shift toward iconic and symbolic visual computing, or it could be something even more radical: a mind-object, a projection within a projection coming entirely from Al’s consciousness. A totem that’s entirely imaginary yet functionally real. In the context of the show, that was an explanation that made sense to me — Al, after all, wasn’t physically there with his time-leaping friend Sam, he was a holographic projection from a stable time in the future. He could have looked like anything; so, too, his computer. But that handlink as a mind-object also suggests computing that exists at the intersection of technology and parapsychology — interfaces that respond to mental states, emotions, or subconscious patterns rather than explicit physical inputs. What kind of computing would exist in a world where telepathy was as commonly experienced as the five senses? Penny’s Multi-Page Computer: Hardware That Adapts Inspector Gadget’s niece Penny carried a computer disguised as a book, anticipating today’s foldable devices. But unlike our current two-screen foldables arranged in codex format, Penny’s book had multiple pages, each providing a unique interface tailored to specific tasks. This represents customization at both the software and hardware layers simultaneously. Rather than software conforming to hardware constraints, the physical device itself adapts to the needs of different applications. Each page could offer different input methods, display characteristics, or interaction paradigms optimized for specific types of work. This could be achieved similarly to the Doctor’s screwdriver, but it also could be more within reach if we imagine this kind of layered interface as composed of individual modules. Google’s Project Ara was an inspiring foray into modular computing that, I believe, still has promise today, if not moreso thanks to 3D printing. What if you could print your own interface? The Holodeck as Thinking Interface Star Trek’s Holodeck is usually discussed as virtual reality entertainment, but some episodes showed it functioning as a thinking interface — a tool for conceptual exploration rather than just immersive experience. When Data’s artificial offspring used the Holodeck to visualize possible physical appearances while exploring identity, it functioned much like we use Midjourney today: prompting a machine with descriptions to produce images representing something we’ve already begun to visualize mentally. In another episode, when crew members used it to reconstruct a shared suppressed memory, it became a collaborative medium for group introspection and collective problem-solving. In both cases, the interface disappeared entirely. There was no “using” or “inhabiting” the Holodeck in any traditional sense — it became a transparent extension of human thought processes, whether individual identity exploration or collective memory recovery. Beyond the Screen, but Not the Body Each of these examples suggests moving past our current obsession with maximizing screen real estate and window management. They point toward interfaces that work more like natural human activities: environmental awareness, tool use, conversation, and collaborative thinking. The best interfaces we never built aren’t just sleeker screens — they’re fundamentally different approaches to creating that unique space for thinking, communicating, creating, and experiencing that makes technology truly exciting. We’ve spent two decades consolidating everything into glass rectangles. Perhaps it’s time to build something different.

2 weeks ago 13 votes
Lights&Shadows by Modern World Studio

We developed the complete design for the Lights & Shadows project—a selection of 12 organic teas—from naming and original illustrations...

2 weeks ago 33 votes