The Quest for Malleable Software: Reclaiming Control in a Rigid Digital Age (2025)

Authors: Geoffrey Litt, Josh Horowitz, Peter van Hardenberg, and Todd Matthews Date: June 2025 Affiliation: Tenfold: Celebrating 10 Years of Ink & Switch

The Core Thesis

The dawn of personal computing promised us a digital "clay"—a flexible medium that individuals could mold to fit their specific needs. However, the reality we inherited is a world of digital appliances: products designed in isolation, sealed shut, and impossible to alter.

Currently, the burden of adaptation lies with the human. When a tool fails to meet a requirement, the user must $\text{submit a ticket} \rightarrow \text{wait for a developer} \rightarrow \text{hope for an update}$ . We are forced to bend our workflows to fit the software's constraints, rather than the software bending to fit our lives.

Our Vision

We advocate for malleable software: tools that can be reshaped by the user at the moment of use with minimal friction. This shifts the power of adaptation from distant corporate engineering teams to the people actually using the tools.

To achieve this, we must dismantle several systemic barriers:

~~Passive consumption~~ $\rightarrow$ Active co-creation
Siloed, monolithic applications $\rightarrow$ Composable custom workflows
Rigid OS/App Store constraints $\rightarrow$ Open, inviting systems

The Motivation: Why We Need Adaptability

The Wisdom of Physical Spaces

Human beings have an innate drive to customize their environments to unlock their full potential. Consider these examples:

The Luthier: A guitar maker doesn't just use tools; they arrange their workshop with surgical precision. If a specific support is missing, they carve a wooden block or sand down a pair of pliers to create a bespoke tool.
The Home Cook: A kitchen evolves over time. A cook might add ceiling hooks for pots or rearrange shelving to optimize the flow between the prep area and the stove.

In the physical realm, malleability is a given. We can make "micro-adjustments" (like a Post-it note on a monitor) or "macro-adjustments" (like a full kitchen renovation). If we lack the skill for the latter, we hire a local expert.

"Age plus adaptivity is what makes a building come to be loved. The building learns from its occupants, and they learn from it." — Stewart Brand, How Buildings Learn

The Rigidity of the Digital Realm

As our lives migrate from atoms to bits, we have gained efficiency but lost agency. We are now operating in environments where we cannot "move the furniture."

Case Study A: The Index Card Wall

One author recalls a software team using a physical wall of index cards for tracking. This system was highly malleable:

Lines were taped and moved.
Custom checklists were scribbled on the fly.
"Special zones" emerged organically to handle specific project nuances.

When the team migrated to a web-based issue tracker for remote work, these organic adaptations vanished. The software couldn't model a "special zone," so the process was abandoned. What once took minutes to iterate now took hours of configuration—if it was even possible.

Case Study B: Medical Burnout

Dr. Atul Gawande highlights how the "computerization" of medicine is fueling physician burnout. In the era of paper, doctors could skip irrelevant fields. Modern Electronic Medical Record (EMR) systems, however, mandate every field.

"Spending the extra time didn’t anger her. The pointlessness of it did."

The frustration stems from the lack of agency. The software imposes a rigid logic that ignores the reality of clinical practice.

The Systemic Conflict

The current software model relies on centralized development. This creates a fundamental paradox:

Feature	Centralized Development (The "Appliance")	Malleable Software (The "Clay")
Control	Held by a distant corporate team	Held by the end-user
Customization	Feature requests $\rightarrow$ Backlog $\rightarrow$ Update	Direct modification at point of use
Scalability	Bloated "all-in-one" features	Lean, composable components
User Role	Passive recipient	Active co-creator

When a developer tries to satisfy every niche user request, the product becomes a "bloated mess." To maintain quality, teams must say "no" to the long tail of specific needs. This makes the user's struggle feel inevitable—but it is actually a design choice.

The Mathematical Intuition of Agency

We can think of the utility of a tool ( $U$ ) as a function of its core capability ( $C$ ) and the user's ability to adapt it ( $A$ ) to their specific context ( $X$ ):

$U = f(C, A \cdot X)$

In current software, $A \approx 0$ , meaning the utility is capped by whatever the developer envisioned. In malleable software, $A > 0$ , allowing utility to scale with the user's unique needs.

Moving Forward

We believe the path forward involves synthesizing decades of research and prototyping. Our goal is to move away from the "locked-down" app model and toward a system where users can gradually transition from consumers to creators.

Roadmap for Change

Re-evaluate programming languages to support end-user modification.
Challenge the "walled garden" philosophy of modern operating systems.
Develop tools that compose into workflows rather than remaining in silos.
Study historical precedents of user-extensible software.

The Feedback Loop

The current cycle of software improvement is broken:

We propose a new loop: User encounters friction $\rightarrow$ User modifies tool $\rightarrow$ Tool is improved instantly.

Call to Action: Whether you are a researcher, a developer, or a frustrated user, we invite you to help us build this future.

Contact:

Twitter/X: @inkandswitch
Email: hello@inkandswitch.com

Citation: Litt, G., Horowitz, J., van Hardenberg, P., & Matthews, T. (2025). Malleable Software: Restoring User Agency in a World of Locked-Down Apps.