web
Writing a brief in five sentences
Who uses it, what they must do, what exists, what must not change, and what would count as done. That is enough to begin.
Field notes
Short notes worth keeping in a drawer.
mobile
Phone first is not phone only
Design the smallest screen first, then let it breathe on larger ones. Check landscape and large text settings early.
design
Label buttons with verbs
"Save draft" tells people what happens; "OK" does not. Interface copy is design work.
release
Keep a rollback note
Before any release, write down how to undo it and who can do it. One paragraph is fine.
release
Store listing text is product text
Describe what the app does in the first line, honestly. Screenshots should show real screens.
support
Reporting a fault usefully
What you did, what you expected, what happened instead, when it started and who is affected. A screenshot of the error helps.
support
Passwords and support
Never send a password by email. If access is needed, it should be arranged through a proper account or temporary access.
web
Forms should fail politely
If sending fails, keep the visitor's text and say clearly that nothing was sent.
design
Contrast is not a matter of taste
Text must remain readable for people with low vision or in bright light. Check it, do not guess.
mobile
Ask for permissions at the moment they make sense
Asking for location on first launch with no explanation invites a refusal.