Everstead Labs · App Rescue
TrailKit — one broken app, three fixes, side by side
A fictional hiking-gear checklist app that was losing users. Toggle between the state it arrived in and the same screen after the three highest-impact fixes.
As it arrived — layout collides, Save silently fails, nothing is labeled.
at saveGear (app.js:47:19)
at HTMLButtonElement.onclick (index.html:1:212)
After the rescue — labeled, readable, and saving for real.
Hiking gear checklist · saved on this device
Add your first item above — it saves automatically to this device.
The 3 fixes
Every rescue starts with the three defects costing the most money. Here is what we found in TrailKit, what we did, and why it matters commercially.
Tapping Save threw a JavaScript error behind the scenes. The user saw nothing — their checklist just vanished on the next visit.
Wired Save (and every add, check, and delete) to real device storage, with a visible "Saved" confirmation so users know it worked.
Losing a user's data once is usually losing the user forever. Data loss is the fastest route to 1-star reviews and refund requests.
On a phone — where nearly all checklist use happens — inputs stacked on top of the title, the Save button ran off-screen, and the tap targets collided.
Rebuilt the screen mobile-first with a simple vertical flow, full-width fields, and comfortable tap targets.
A layout users can't operate is a 100% conversion killer. If the first screen looks broken, people assume the whole product is — and uninstall in seconds.
Two bare input boxes with no labels, pale grey-on-grey text, and a blank void where the list should be. New users had no idea what to type or whether the app worked.
Labeled every field, raised text contrast to readable levels, and added a friendly empty state that tells first-time users exactly what to do.
Most trial users decide in under ten seconds. Clear labels and a guided first step are the cheapest retention win an app can buy.