Before you brief an app developer
Write down who the user is, the one task they must complete, and what they do today instead. Those three sentences will save more money than any feature list.
mobileResources
Stuff we keep saying.
So we wrote it down. Hit a topic word to shuffle the wall.
Native or cross-platform?
Cross-platform suits most business apps with standard screens. Native is worth considering for heavy device features, demanding graphics, or when you only need one platform.
mobileTest with five people
Ask five people who match your audience to complete one task while thinking aloud. You will usually find the biggest problems by the third session.
designWords are interface
Label buttons with the outcome ("Book appointment") rather than the mechanism ("Submit"). Use the terms your users use, not internal jargon.
designA website checklist
Every page needs a unique title and description, readable text on a phone, working contact details and a privacy notice that matches what the site actually does.
webKeep forms short
Each extra field loses people. Ask only for what you need to reply, and say clearly what happens after someone presses send.
webDeveloper accounts belong to you
Register Apple and Google developer accounts in your organisation's name. Grant access to developers; do not let them hold the account.
publishingStore privacy answers
Both stores ask what data your app collects. List every analytics, crash-reporting and login tool before filling in the forms; they all count.
publishingBusiness email basics
Set up SPF, DKIM and DMARC records for your domain so your messages are less likely to land in spam, and check that website forms send from an existing mailbox.
publishingThese notes are general guidance, not legal or regulatory advice. For data protection obligations, see the Information Commissioner's Office.