Practical notices, freely given.
Guidance we find ourselves repeating, set as a classified column. No sign-up, no newsletter.
WRITING A ONE-PAGE BRIEF. Describe who the app is for, the single most important task they will complete, and what “done” means for a first release. Leave features for later lists. [Planning]
DECIDING BETWEEN WEB AND NATIVE. If people use it occasionally and need no device features, a well-built website is often enough. Push notifications, camera use and offline work point towards an app. [Planning]
TESTING WITH FIVE PEOPLE. Ask five people from your audience to complete one task while thinking aloud. Do not help. Note where they hesitate; that is your next design change. [Design]
WRITING ERROR MESSAGES. Say what happened, why if known, and what to do next. “Card declined — check the expiry date or try another card” beats “Error 402”. [Design]
BEFORE STORE SUBMISSION. Prepare a privacy policy URL, a support URL, accurate data-collection answers, a demo account for reviewers and screenshots taken from the real build. [Publishing]
WHEN A REVIEW IS REJECTED. Read the cited guideline, change the smallest thing that resolves it, and reply in the resolution centre with a factual explanation. Rejections are common and usually fixable. [Publishing]
DOMAIN EMAIL BASICS. Make sure SPF, DKIM and DMARC records exist for your domain. Without them, legitimate messages from your website or mailbox are more likely to be filtered. [IT]
KEEPING ACCESS SAFE. Use a password manager, turn on two-step verification for store, hosting and domain accounts, and keep at least two trusted people with recovery access. [IT]