app development01
Shipping apps people keep open
The practical interface decisions behind software that survives week two.
/ 3 min
The journal
Useful ideas for
the next chapter.
Retention, states, release engineering and the decisions that separate an app people keep from one they delete.
About this topic
Why we keep
writing about it.
1 article · App development
An app is judged in its first four minutes and kept or deleted in its first week. Almost none of what decides that is the feature list — it is the empty state, the permission prompt, the offline case and how quickly someone reaches the thing they downloaded it for.
These pieces cover the unglamorous half of shipping software to a store: instrumenting retention before launch rather than after, the rejection causes that catch teams twice, staged rollouts, and rehearsing the release that goes wrong before it does.
Browse by topic
Five things we
write about.
Each topic collects the arguments we find ourselves repeating in first meetings, written down properly so you can read them instead.
Web development
3 piecesBriefs, structure, platform choices and why accurate websites so often fail to persuade anyone.
App development
1 pieceRetention, states, release engineering and the decisions that separate an app people keep from one they delete.
E-commerce
2 piecesPlatform decisions, replatforming risk, checkout friction and where merchandising velocity actually comes from.
Platform & support
2 piecesCore Web Vitals, accessibility, security and the compounding value of work nobody notices.
Agency practice
2 piecesHow we work, what we refuse, and the arguments we would rather have in week two than week ten.
Editorial policy
Why there is no
posting schedule.
We publish when we have learned something worth another team’s ten minutes, which works out at roughly one piece a month. There is no content calendar, no keyword-led brief and no ghostwriter, because articles written to fill a slot read exactly like articles written to fill a slot.
Everything here is written by the people doing the work, and every recommendation has been tested on a real engagement — including the ones where we got it wrong first. Where a claim is contested, we say so rather than presenting a preference as a finding.
Nothing is gated. If a guide is useful, it should be useful before you speak to us.
A better brief starts here
Ready to make the next move obvious?
Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.