Pre-release checklist
Version number bumped, notes written, test account removed, rollback build kept, approver named.
Toolbox notes
Short, practical notes we hand to people before projects start. Search or filter them; they are general guidance, not advice for your specific setup.
Store listing draft
Write the listing as if to a busy stranger: what it does, who it is for, what permissions it needs and why.
Map a chore on one page
List each step, who does it and where the information comes from. Circle the steps people copy by hand.
Touch-target sanity check
Anything tapped often should be easy to hit with a thumb, with space around it.
Who edits the website?
Name a person, not a team. If nobody can be named, plan a simpler site.
Form error wording
Say what is missing and keep what was typed. Never blame the visitor.
First version filter
If a feature is not used in the first week, it can probably wait for version two.
Patchy signal
Decide what the app should do with no connection before building the happy path.
Before you call IT support
Note the device, what you clicked, the exact message and whether it happens to colleagues too.
Account hygiene
Shared logins make support harder. Give each person their own account where the service allows.