Small Apps Need Smaller Promises
The easiest way to finish a product is to make the promise smaller, sharper, and easier to keep.
The most useful product constraint I have found is a small promise. Not a small app, exactly. A small promise.
An app can have very little code and still promise too much. It can imply that it will organize your life, fix your focus, improve your health, or replace a whole workflow. That pressure leaks into every decision. The settings page grows. The onboarding grows. The empty states start explaining a philosophy.
A smaller promise is easier to design around. “Join these audio files into one audiobook.” “Track this fast.” “Time this session.” The product can still be thoughtful, but it does not need to become a system.
I like this because it makes quality more visible. When the promise is narrow, every rough edge is obvious. The first launch, the first empty screen, the first saved item, the first export. There is nowhere for complexity to hide.
That is uncomfortable, but useful. It means the work becomes less about adding one more clever thing and more about making the main thing feel calm, obvious, and reliable.