Publishing & release
Everything between a finished build and people using it.
Five stages to a published app
- Stage oneAccountsDeveloper accounts set up in your organisation's name, with you as owner.
- Stage twoTesting tracksTestFlight and Google Play internal testing for your staff.
- Stage threeListingDescriptions, screenshots, age rating and privacy labels prepared.
- Stage fourReviewSubmission, reviewer questions answered, fixes turned round.
Accounts you own
Apple and Google both require a developer account to publish. We recommend these are registered to your organisation, not to us, so that you keep control of the listing whatever happens. We guide you through registration, including the organisation verification steps both stores ask for, and are then invited as team members.
A listing that tells the truth
We write store descriptions in plain British English, prepare screenshots from the real app, and complete privacy disclosures accurately from the data the app actually collects. Overclaiming in a listing is a common cause of rejection and, worse, of disappointed users.
When an app should not be public
Many yard tools are for staff only. In those cases we discuss alternatives: unlisted distribution, managed device enrolment, or a progressive web app that never enters a store. We explain the trade-offs so you can decide with full information.
Publishing websites and web apps
For the web we set up hosting, domains, TLS certificates, backups and a staging copy for testing changes. Where your organisation already has hosting, we work within it and document exactly what we changed.
After release
Operating system updates arrive every year and store policies change. Our support agreements include checking each major release, updating dependencies, and resubmitting when needed, so an app does not quietly stop working.