# Disposable Apps: When Software Becomes Cheap

**FN-004 · Issue 001 · 2026-09-15 · By JMPKit**

> An app can be valuable even when it is intended to exist online only for a moment.

## The situation

When applications become inexpensive enough to create for one person, one
group, one occasion, or one temporary need, software behaves less like capital
equipment and more like a message, document, browser tab, or shared room.

Clay Shirky's 2004 account of “situated software” described software made for a
particular social situation rather than a generic population. Agent-directed
creation makes that mode practical at far greater frequency: a dinner vote, an
afternoon file drop, an event board, a family media room, or a tool shaped for
one peculiar workflow.

## What abundance invokes

- Lifetime should follow intent: hours, days, months, or no scheduled end.
- Naming, discovery, provenance, moderation, trust, and resource fairness grow
  more important as creation gets cheaper.
- A hosted copy should be easy to renew, archive, restore, transfer, sponsor,
  or let recede.
- The durable object may be the local source, prompt, data, relationships, or
  stable identity rather than continuous deployment.
- Maintenance becomes a series of small agent-directed changes instead of a
  large permanent project.
- The scarce value shifts toward judgment: recognizing the need, choosing a
  healthy shape, earning trust, and operating the result responsibly.

Cheap creation also creates noise, duplication, abandonment, abuse, broken
dependencies, and unclear responsibility. No person should be expected to
curate that abundance manually. Lifetimes, renewal, capacity, service notices,
local source, and recovery are therefore part of the product model, not merely
billing details.

## JMPKit's response

“Disposable” must not mean careless, insecure, or valueless. It means the
online lifetime may match the need. A temporary app can end gracefully; a
useful experiment can retain its identity and grow. JMPKit must support both
momentary and lasting software because agent-created abundance is an additional
mode, not a smaller version of conventional development.

## Guidance for an agent

- Infer a sensible online lifetime from the request and disclose it.
- Prefer a bounded lifetime when the need is clearly bounded or uncertain.
- Preserve source locally regardless of the hosted lifetime.
- Renew the same app when the need continues; do not produce unnecessary new
  identities or links.
- Treat short-lived work with the same security and consent care as lasting work.

## Related reading

- [Clay Shirky, “Situated Software”](https://gwern.net/doc/technology/2004-03-30-shirky-situatedsoftware.html)
- [Local-first software](https://www.inkandswitch.com/essay/local-first/)
- [Local Source, Public Instance](local-source-public-instance.md)