Covent Garden, London · apps · web · publishing
Your release, cleared for departure.
Aerorise designs, builds and publishes mobile apps and web products. Our speciality is the last mile: signing, store listings, review, rollout and the steady releases after. We prepare for launch from the first week, so launch day is calm.
Example board for a fictional product.
Most launches stall in the last mile
The app works. The website looks right. Then the surprises arrive: a signing certificate expired over the weekend, the privacy questionnaire asks about a library nobody remembers adding, the screenshots are the wrong size for one device class, and the reviewer cannot sign in because the demo account was deleted.
None of these is difficult. Each one costs days when it is discovered late. Aerorise treats publication as a discipline in its own right, with accounts, keys, listings and declarations prepared alongside the product rather than after it.
We do this for products we build, and for products other teams have built and need to get out of the door.
Launch planner
Pick a target public date. We count backwards using the preparation windows we plan with. The dates are a planning aid, not a promise: store review times vary and are outside anyone’s control.
- Choose a date to see your countdown.
Why do submissions bounce?
Store reviewers are not out to catch you. Most rejections come from a small set of preventable gaps. Choose one to see what usually causes it and how we prepare for it.
Usually caused by
How we prepare
What we do, and what you hold afterwards
Publishing
Store accounts, listings, privacy declarations, review preparation and phased rollout, for apps we build and apps built by others.
You hold: accounts in your name, a submission pack, a written release guide.
Publishing assistanceMobile apps
iOS and Android, native or cross-platform, built with signing, build automation and test tracks in place from week one.
You hold: source code, an automated build pipeline, store-ready builds.
Mobile developmentWeb
Fast, accessible websites and web applications with deploys you can repeat and reverse in one step.
You hold: hosting in your name, preview environments, a rollback plan.
Web developmentUI/UX
Interfaces and store visuals designed together, so the listing tells the truth about the product.
You hold: tested flows, a component library, correctly sized screenshots.
UI/UX designAfter take-off: a steady release rhythm
Every autumn Apple and Google release new operating systems. Every year store policies tighten and libraries need updating. A product that is not released regularly slowly becomes one that cannot be released at all.
Our support keeps a predictable cadence: fixes grouped into maintenance releases, phased rollouts watched closely, and release notes that real people can read. We work Monday to Friday, 09:00 to 18:00 UK time.
Who usually calls us
A team with a finished build and no publishing experience. You have an app that works, but nobody has been through App Store Connect or Play Console before. We set up the accounts properly, prepare the submission with you and record the steps so the next release is yours.
A product stuck in review. A rejection notice has arrived and the guideline it cites is vague. We read it with you, check the build and the listing, and decide together whether to change the app, clarify the notes or appeal.
An organisation starting from an idea. You want the app or website designed and built by people who will also see it through publication and the first year of updates. We plan the release from the first week.
A website moving house. A new site is replacing an old one and the old addresses must keep working. We map redirects, check search console, rehearse the switch on staging and keep a rollback ready.
Three pre-flight habits
Install it fresh
Before each release, install the test build on a device that has never had the app. First-run crashes hide on developers' phones.
Keep a release log
One line per release: version, date, changes, rollout percentage. It makes support and review conversations far quicker.
Check the keys monthly
Certificate and profile expiry dates belong in a shared calendar, not in one developer's memory.
Before you get in touch
Can you publish an app another team built?
Yes. We review its configuration, permissions and data use, flag likely review issues and then handle submission. Source access helps but is not always needed for a first look.
Can you guarantee approval or a launch date?
No one can. Approval belongs to Apple and Google. Complete, accurate submissions avoid most delays, and we plan buffer time for a resubmission.
Whose name are the store accounts in?
Yours. Developer accounts, signing keys, domains and hosting belong to your organisation. We are invited in with the access we need.
Do you only do the publishing part?
No. We design and build apps and websites too, but you can engage us for publication alone.