Solfreaks PublishPro takes a finished app through Google Play Console and App Store Connect and keeps it live: developer accounts, store listings, content ratings, release tracks, review rejections and the routine updates that follow. If the build exists and you'd rather not spend a week fighting consoles and forms, this is the job.
One rule comes first. The developer accounts, and the apps inside them, belong to you, not to us. We're added as users with the access we need, and you can remove us whenever you like. Too many apps end up stuck in an agency's account when a relationship ends, and we won't set things up that way.
What we handle
- Developer account setup in your name, with a walkthrough of what each store asks for.
- Store listings with titles, descriptions, screenshots and graphics for each store, written around what the app really does.
- Rating and privacy forms: the content rating questionnaire, Google's Data safety form and Apple's privacy answers, completed to match the actual app.
- Signed builds and release tracks covering Play App Signing, internal and closed testing, TestFlight, and staged rollouts so a bad release reaches few users.
- Rejection and warning handling, from reading the reviewer's message to resubmitting with a fix or a reply.
- Routine updates with version numbers, release notes and target API level changes handled each time you ship.
Accounts, and the closed-test wrinkle
Google currently asks new personal developer accounts to run a closed test, with a minimum number of testers over a minimum number of days, before they can apply for production access. That adds weeks and can't be skipped. Organisation accounts avoid that rule but need business verification, which usually involves a D-U-N-S number and can take days or weeks. Apple asks for something similar from organisations.
From finished build to live
- Account check. We review what you already have. A new account can be opened in an afternoon, but verification takes from a few days to a few weeks and is out of our hands, so start it early, even while the app is still being built.
- Listing and forms. We write the listing, prepare screenshots and complete the rating and privacy forms. Once we have the build and a privacy policy this usually takes two to three days. If the policy isn't written yet, see our privacy and compliance setup.
- Test tracks. The app goes to internal testing and TestFlight so testers install exactly what the store will deliver. For a new personal Google account, the closed test can add a couple of weeks or more.
- Submission. We send the app for review. Reviews run from a few hours to several days, sometimes longer for new accounts, and the decision is the store's, so we can't promise approval.
- Staged rollout. A new version reaches a small share of users first. We watch crash reports and reviews, then widen the rollout or halt it.
- Updates. Each new version goes through the same checks. Our app maintenance plans cover this monthly.
When a store says no
Rejections are normal, and most are fixable. Common causes include a crash during review, a login with no demo account for the reviewer, missing account deletion, permissions with no clear reason, or a listing that promises more than the app does. We read the reviewer's message closely, fix the app or reply with evidence, and resubmit.
Who this is for
It fits first-time publishers, teams whose app was rejected with a message nobody could decode, and owners whose app sits in an agency's account and who want it moved to their own. Both stores support app transfers, and we plan them carefully.
This isn't for you if you want us to publish under Solfreaks' own developer account. We won't, because you should own what you've paid for. We'll also say so if an app breaks store rules, such as misleading claims, instead of hunting for a way round. And if you need approval guaranteed by a fixed date, no honest provider can offer that.
Money and time
Final price is set by the number of apps and stores, the state of your accounts, how much listing work there is, how many languages you need, and how many policy issues turn up. Listings in other languages or deeper keyword work fall under app store optimisation. A first release is a fixed-scope job, and ongoing updates run monthly. The stores' own fees are paid by you directly to Apple and Google.
With a finished build and ready accounts, a first submission can go out within a few days to a week. A brand-new account often takes several weeks overall, mostly spent waiting on verification, testing requirements and review. The quote follows a short discovery call.
Why Solfreaks for store work
We've taken our own apps through Google Play, so the consoles and their quirks aren't new to us. The team is small and based in Rawalpindi, next to Islamabad, which means you speak to the person doing the submission, in Pakistan hours that overlap with the Gulf and the UK. The accounts, upload keys and listings stay in your name. If you've got a build ready, tell us what you need.
Open-source tools and references
A few public projects that come up a lot in this kind of work. They belong to other people and teams. We link to them because they are worth a look, not because anyone pays us to.
- fastlane/fastlaneAutomates screenshots, metadata and uploads to both stores.
- Triple-T/gradle-play-publisherGradle plugin that publishes Android apps to Google Play.
Frequently asked questions
Should I register as an individual or an organisation?
If the app belongs to a company, register as an organisation. It looks more trustworthy in the store, avoids the closed-test rule for new personal Google accounts, and keeps the app with the business if people leave. The cost is business verification, which takes longer. An individual account is fine for a personal project. We'll explain which fits your situation.
Our app was rejected and the message makes no sense. Can you help?
Usually, yes. Send us the message, and console access if you're comfortable sharing it. Reviewers use standard wording that hides the real cause, so we compare it against the policy, the build and the listing. Many rejections come down to a missing demo login, an unexplained permission or a claim in the listing. We fix what's ours to fix and tell you plainly if the policy rules the idea out.
Can you publish under your own developer account to save time?
We don't, and we'd advise against it with anyone. An app inside somebody else's account is hard to move, and the account holder controls it. Opening your own account takes some effort upfront, but you end up owning the listing, the reviews, the revenue settings and the freedom to change agencies. We guide you through the setup.
How long until the app is live?
With a finished build and ready accounts, often a few days to a week to submit, plus the review. For a new personal Google account, the required closed test adds a couple of weeks or more. Verifying an organisation account can take from days to weeks. The stores set those timings, so we plan around them and keep you updated on progress.
What do you need from me to publish?
A release-ready build or access to the code, your developer accounts or the details to open them, a privacy policy URL, the app description and any branding assets, and a demo login if the app needs sign-in. We send a checklist after the first call so nothing is left until the last day.
Talk it through with us
Tell us what you are building and where it hurts. You get a straight answer, a plan and a price, and if we are not the right people we will say so.
