Malleable software: Restoring user agency in a world of locked-down apps (2025)
Ink and Switch explores the shift from flexible physical tools to rigid software silos, proposing design patterns for user-adaptable software ecosystems.
read it Offers a compelling conceptual framework for why modern software feels restrictive and how computing can return to user-driven tool creation.
summary
Modern software environments have traded the malleability of physical workshops and early computing for rigid, closed-off consumer applications. Centralized developers cannot keep up with niche user needs, leading to user burnout and abandoned workflows. The authors propose malleable software, an ecosystem built on gentle slopes from user to creator, composable tools instead of isolated apps, and shared data. Ultimately, the essay calls for reimagining foundational computing infrastructure to restore user agency.
key points
- Mass-produced software creates rigid workflows because centralized teams cannot serve long-tail niche requirements without bloating products.
- Effective malleable systems require a gentle slope where incremental power upgrades demand minimal extra learning skill, akin to spreadsheets.
- Composable tools act like general-purpose kitchen knives rather than single-purpose avocado slicer apps, relying on shared data formats.
who should read it
Software engineers, product designers, and tool builders interested in human-computer interaction and end-user programming.
discussion positive
consensus
Most participants agree that modern software has devolved into locked-down SaaS black boxes, drawing heavy nostalgia for hackable past eras.
pushback
A vocal minority points out that the vast majority of mainstream users neither want nor care about software customizability.
I believe it is critical for regulators to force mega-corporations (and software vendors in general) to permit third party clients.
I use services like YouTube every day, why can I get sued if I write my own YouTube client that's better than the one provided by Google? Why can I get sued if I create a chat client that aggregates the myriad of chat services I use?
I'd argue that this even extends down the stack. Why is there only Android and iOS? It's because hardware drivers are practically impossible to write for undocumented hardware (which is virtually all hardware). Vendors should be …
Argues that regulatory intervention forcing open APIs and third-party clients is essential to breaking vendor lock-in.
Generated by an LLM from the article and thread. Check the sources before relying on it.