Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Monthly plan

Your app updates built, submitted and published by one engineer

In store release management I handle your Google Play and App Store releases month by month: I build, sign, test and submit each update, deal with store review feedback and keep a way back if a release misbehaves. The price is quoted after a short discovery call, against a written scope.

Who is Store Release Management for?

  • Teams with an app in the stores and nobody who knows how to ship an update.
  • Companies whose releases get stuck on signing, store policy or review feedback.
  • Owners whose old developer still holds the store accounts and the build setup.

What does Store Release Management include?

  • A written review firstI check who owns the store accounts, how builds are made and what could block the next release.
  • Builds and signingRelease builds and signing keys are set up and written down, so a release does not depend on one laptop.
  • Release pipelineWhere it helps, I set up fastlane and CI so a release is a repeatable process and not a ritual.
  • Submission to both storesI prepare and submit updates to Google Play and the App Store, with release notes and the required store information.
  • Store review feedbackWhen a store asks questions or rejects an update, I read the reason and fix what it points at.
  • Staged rollouts and a way backReleases go out in a controlled way, I check the live version and a rollback is ready if something goes wrong.
  • Account ownershipStore accounts and keys are moved into your name, with named access for me, so nothing depends on one person's login.
  • Written updates, one weekly callA short written update for each release and one fixed overlap call each week.

What does Store Release Management not include?

  • A promise that a store will approve an update or how fast. Review is up to Google and Apple.
  • App marketing or store optimisation.
  • Building the features inside the release. That is covered by a separate scope.
  • Work without a written scope. Every month runs against one.

How does Store Release Management work?

  1. Send me a few linesWhich stores, who owns the accounts and what has been blocking releases. I reply within 24 hours.
  2. A discovery callA call within 48 hours to understand your release routine and the app.
  3. A written review and scopeWhat blocks releases today and a scope of the releases I will handle.
  4. KickoffTypically inside two weeks, with account access and signing set up properly.
  5. Month by monthReleases planned in two-week sprints, each with a written note and a check on the live version.

Is Store Release Management a good fit for me?

A good fit when

  • You have releases waiting because nobody dares submit them.
  • You need a senior person to take over store accounts and builds from an agency or a former developer.
  • You ship updates regularly and want them to be routine.

Not a fit when

  • You want a promise of approval or of review time.
  • Your app is not built yet.
  • You expect marketing or promotion in the stores.

What do people ask about Store Release Management?

What does release management cost?

It depends on how many apps and how often you ship, so I quote a monthly figure after a short discovery call, against a written scope.

Will the store approve my update?

I cannot promise that, because review is decided by Google and Apple. I can make sure the build and the submission are right first time.

Who owns the store accounts?

You do. I work through named access, and I help move accounts into your name if they are not already.

Do you work on apps built in other tools?

I work most with Flutter and native Android and iOS. I look at your project first and tell you plainly if it is outside what I do.

Read next

Before you decide

Related projects

All projects

Own product · Taxi dispatch SaaS

TaxiDex

My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.

TypeScriptNode.jsAdonisJSNext.js

Fintech · Buy now, pay later

Qist Bazaar

A buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.

FlutterDartWooCommerceREST

Enterprise · Field data

DCOR

An offline-first field app with three roles, GPS attendance, a dynamic form engine and five languages.

FlutterDartBLoCget_it

Next step

Store Release Management: let's talk

A discovery call within 48 hours, and a kickoff typically inside two weeks.