Publisher vs self-publishing: how indie game and app developers should decide
Your game or app is nearly done, and now it has to reach players. You can publish it yourself or sign with a publisher, and each path suits some developers far better than others. This guide sets out what each option involves, where the trade-offs sit, and gives you a decision matrix to test your own situation against.
Updated:
What self-publishing actually involves
Self-publishing means releasing under your own developer account and running everything that happens after the build is finished. Uploading the binary is the easy part. The real work is the set of jobs around it, and most of them have little to do with programming.
If you plan to publish a mobile game on your own, budget time for:
Plenty of solo developers handle all of this. Go in knowing that each item takes time to learn, several of them cost money, and user acquisition in particular can drain a budget quickly if the game's numbers are not ready yet.
- Developer accounts: enrolling in the Apple Developer Program and Google Play Console, identity verification, account fees and keeping the accounts secure.
- Store review: meeting Apple and Google guidelines, privacy labels, the data safety form, age ratings, and fixing builds that get rejected.
- ASO: title, keywords, screenshots and preview video, plus testing them across languages and markets.
- User acquisition (UA): setting up campaigns on ad networks, producing creatives and keeping spend profitable.
- Ad monetization: mediation setup, ad placements, in-app purchase products and the balance between them.
- Analytics: tracking installs, sessions, progression and revenue events correctly from day one.
- Payouts and tax: receiving money from stores and ad networks, bank and tax forms, invoicing and bookkeeping.
- Live ops: updates, events, bug fixes, replying to reviews and player support.
What a publisher takes over, and what you give in return
A publisher handles that second half of the job. Typically that means store operations, marketing, user acquisition, monetization setup and data analysis; some also bring funding and technical support. You stay focused on the product itself.
In exchange, publishers usually take a share of revenue. They put their UA budget and their team's time at risk, and the revenue share is how they get paid back. Deal terms vary widely with the product, its stage and how much the publisher plans to invest, so there is no single fair number to look for. It is more useful to read what an offer actually covers: who pays for what, who carries test costs, whether there is an advance, and how long the agreement runs.
With Techmora, for example, the developer never touches store accounts: the product goes out on Techmora's own App Store and Google Play accounts, and earnings are paid to the developer's bank account in the currency they prefer. Revenue share, IP, test costs and advances depend on the product, written terms arrive after the first meeting, and nothing starts until both sides sign. You can read how it works on the mobile game and app publishing page.
Control and IP: what you share and what you keep
Control is the strongest argument for self-publishing. Pricing, update cadence, ad density and which markets you launch in, and when, are all your call. Ownership of the IP is never in question.
Working with a publisher means sharing some of those decisions. That is not always a loss; an outside team looking at real data can spot problems you would miss on your own. Still, get clear answers to these questions before you sign:
A serious publisher will answer these in writing without hesitation. For a fuller list of what to compare between publishers, see our guide on how to choose a game publisher.
- Who owns the IP, and what happens to the rights when the agreement ends?
- Whose account holds the store listing and player data, and what happens if you part ways?
- Who has the final say on product decisions?
- How long does the agreement run, and how can either side exit?
- How often is revenue reported, and in how much detail?
Speed to market, cost and who carries the risk
Which path is faster depends on how ready you are. If your accounts already exist, you have been through store review before and you can fund a small test, self-publishing can move quickly. If this is your first release, account verification, rejected builds and compliance forms can take longer than expected. New personal accounts on Google Play may also need to run a closed test before they can publish to production, so build that into your timeline.
A publisher can shorten the administrative steps because the accounts and processes are already in place. Evaluation, calls and contract review take time too, though. For an honest comparison, write out both timelines side by side.
On cost, the key question is who funds user acquisition. Self-publish and you carry all the risk but keep all the revenue. Sign with a publisher and both the risk and the revenue are shared. Which makes more sense depends on whether the product can scale through paid UA and how much risk you can afford.
The hybrid path: self-publish first, partner after soft launch
The two options are not mutually exclusive. For many developers the most sensible route is to self-publish in a limited set of markets, gather core metrics with a small test budget, and then approach publishers with that data. Real retention and revenue numbers put you in a stronger position to negotiate and let a publisher evaluate the product faster.
One thing to plan for: if the store listing sits on your account, signing a deal may mean transferring the app to another account or republishing it. Raise this in the first conversation to avoid surprises. When you share data, granting view-only analytics access is a good habit.
Soft-launch readiness checklist
A soft launch means releasing in a few markets on a limited scale and measuring before you open up to everyone. Whether you publish yourself or with a partner, launching before these are in place will give you misleading data:
- The core loop or main user flow is complete, with no critical crashes.
- Analytics are live: install, session, progression and purchase events fire correctly.
- Retention is measurable: you can pull cohort reports for day 1, day 7 and beyond.
- Monetization is switched on: ad placements and in-app products have been tested.
- The store listing is final in at least one language: screenshots, description and icon.
- Test markets are chosen and a small UA test budget is set aside.
- Privacy policy, data safety form and age rating are complete.
- You have written down in advance what results mean continue, fix or stop.
Making the call
There is no universally right answer. Your time, budget, experience and the product's potential decide it. The decision matrix below covers the situations developers run into most often; find the rows closest to yours and weigh the reasoning against your own circumstances.
If the publisher route looks right, you can send Techmora your game or app with a demo and any data you have. Every application gets a reply within 5 business days, with reasons if it is declined, and you do not need a company to apply. To get guides like this regularly, subscribe to our monthly newsletter.
Decision matrix: self-publish or work with a publisher?
- You have shipped to the stores before and your accounts are active — Recommendation: self-publish: you know the process, so keeping control costs you little extra.
- This is your first release and you have never been through store review — Recommendation: either: doing it yourself teaches a lot, a publisher saves time; pick whichever matters more to you now.
- You are building a hyper-casual or hybrid-casual game that grows through paid UA — Recommendation: publisher: results in these genres depend heavily on testing speed and acquisition budget.
- Your game or app serves a niche, community-driven audience — Recommendation: self-publish: growth comes more from community and organic channels than from ads.
- The product looks promising but you have no budget for UA — Recommendation: publisher: sharing test and acquisition costs makes the risk manageable.
- Keeping full IP ownership and creative control is non-negotiable — Recommendation: self-publish: or do not sign until the agreement confirms in writing that the IP stays with you.
- You have soft-launch data and the metrics look healthy — Recommendation: either: you can keep scaling yourself or use that data to negotiate better terms.
- You have no company, and receiving international payouts and handling tax is a struggle — Recommendation: publisher: a partner that handles payouts and guides you on invoicing removes that burden.
- You are a solo developer who wants to move on to the next project — Recommendation: publisher: handing off marketing and live ops frees your time for development.
- You are releasing a simple utility with no revenue goal — Recommendation: self-publish: a publisher would add little value.
Frequently asked questions
How do I publish a mobile game?
Enroll in Google Play Console and the Apple Developer Program, prepare your store listings, complete the privacy and content forms, upload your build and submit it for review. Once approved, the game goes live. The ongoing work starts after that: user acquisition, monetization and updates.
Will I lose the rights to my game if I sign with a publisher?
Not necessarily; it depends entirely on the contract. Some deals leave the IP with the developer, others share it. Before signing, get the IP, termination and account transfer clauses clarified in writing.
Does my game need to be finished before I approach a publisher?
Usually not. A playable demo or gameplay video is often enough to start a conversation. When applying to Techmora you can share a TestFlight build, Google Play internal testing, an APK, a web build or a gameplay video, and granting view-only analytics access to info@techmorainvest.com makes the review easier.
Can I self-publish first and work with a publisher later?
Yes, and it is a common route. Soft-launch data makes it easier for a publisher to evaluate the product. Agree early on which account will hold the store listing and how a transfer would work.
Do I need a registered company to work with a publisher?
It depends on the publisher. Techmora works with individual developers and freelancers as well as companies, and guides developers on invoicing and tax.
More guides
- How to Choose a Mobile Game Publisher: A Practical Guide for Indie Developers
- Custom App Development: A Practical Guide to Hiring an Outside Team
- How to Raise Early-Stage Funding for a Game or App Studio
- Mobile Game and App Monetization: Ads, In App Purchases and Subscriptions
- Mobile Game User Acquisition: How to Read CPI, Retention and LTV
- How to Publish an App on the App Store and Google Play
- Fixed Price or Time and Materials for a Software Project?