Writing a brief in one page
Describe the problem, the people, the must-haves and the nice-to-haves. Add a budget range and any fixed dates. Examples you like — and dislike — help more than long specifications.
maaf / library
The workshop library.
Practical notes we hand out all the time. Free, no sign-up, useful whoever you end up working with.
Ten questions for any software supplier
Who does the work? Who owns code and accounts? How are changes priced? What happens if we part ways? Can we see a sample of your documentation? And five more worth asking before you sign.
Choosing between native and cross-platform
A plain comparison of building separately for iOS and Android versus sharing one codebase, and the questions that should decide it: features, team, budget and maintenance.
Keyboard-only accessibility test
Put the mouse away. Can you reach everything with Tab, see where you are, open and close menus, and submit forms? It takes ten minutes and catches a surprising amount.
What to keep when a website launches
Registrar login, DNS records, hosting access, code repository, CMS logins, a list of renewals and dates. Keep it in one safe place your organisation controls.
Why apps need an update every year
Store minimum requirements move on annually. Skip a year and your app may stop appearing to new users. Budget at least one maintenance release a year.
Before you submit to the App Store
Demo account for reviewers, every advertised feature reachable, privacy label matching every library, support URL live. See our launch kit for the full list.
Backups you can actually trust
How often they run, where they live, how long they're kept — and when someone last restored one to prove it works.
How to write a bug report that gets fixed fast
Steps, what you expected, what happened, device and version, and the time. Five lines that save hours.
Cookies, consent and the simple option
If you don't need analytics, don't load them. A site with no tracking needs far less consent machinery — and is quicker for everyone.