Project D · Disposable software — Goldstine Research

What should an app leave behind?

Project D studies short-lived shared software for a single event. It asks when one small tool is worth setting up and which parts of the record people need after it closes.

One meeting point, one decision.

Imagine a group taking a ferry. The organizer needs everyone to see the final meeting point before departure. A pinned message already solves part of that problem.

Follow one trip

The group chooses a place, the organizer confirms it and the others check the final arrangement. A short-lived app has to make those steps easier than the group’s usual tools.

During the trip. After the trip.

The information people need changes when the meeting is over.

Before boarding

Show the current meeting point, who confirmed it and when it becomes final.

After arrival

Keep only the useful summary the organizer chose to retain. Show what happens to the rest.

Open, use, archive.

A proposed study compares the same event in two conditions. One uses a small event space and one uses a pinned group message.

Illustrative example

Proposed study record

Setup
How much does the organizer have to do?
Coordination
Can each person find the latest decision in time?
Close
Can the organizer get the summary and explain what expires?

The page illustrates a possible lifecycle. It does not represent an operating app or an active payment flow.

What would make a small app worth setting up?

Tell us about a one-off event where the group’s existing tools worked well or left an important decision unclear.