3 ms·
As an indie software creator, consider that you likely don't have the resources to be a software publisher yourself. Software publishing is a separate job, a s
by derefr 7y ago
As an indie software creator, consider that you likely don't have the resources to be a software publisher yourself.
Software publishing is a separate job, a separate comparative advantage, and just because you want to be in ultimate control of your software doesn't mean you can't delegate or contract out that job.
Depending on your size and your publisher's size, you might delegate any of these responsibilities to them:
• their core responsibility: handling the jumping-through-hoops required by each distributor/retailer (in these days these are the app stores) and doing any ongoing liasing with them, leaving you free to just have your publisher as a single point of contact
• doing any extra QA passes required to get your work accepted by each distributor/retailer (and sending the bug-reports back to you)
• learning about changes in your software required to comply with the distributor/retailer's policies, and either reporting them to you, or fixing them themselves, making each of their "ports" into a downstream of your upstream codebase with their fixes living in it
• handling ongoing codebase changes required to evolve your code to comply with minimum-runtime targets of each platform—in effect, giving them commit access to your upstream codebase (though they can do this as a downstream fork, I wouldn't recommend it)
• porting your software to platforms that you can't afford to support yourself (because e.g. the SDK is ridiculously expensive), creating separate "port" forks of the codebase, or perhaps even entirely new codebases that just share art assets
---
If you're an indie shop, getting a publisher has always been a necessity to sell on the more closed-down stores, like the console marketplaces.
Well, that onerous-ness is just becoming more universal.
That doesn't mean you're out of the market! It just means you have to take the idea of acquiring a publisher more seriously.
And that doesn't mean that your publisher will bilk you out of most of your profits, either. Especially in the Apple case, the fixed costs on the publisher's part are pretty small, so development houses have a lot of negotiation room. You might get away with just paying a publisher a fixed fee to handle the glue-work.
Or, on the complete opposite end of the spectrum, if you just want to "write something then never touch it again", you could just sell your codebase as IP to the publisher, or make some arrangement where you keep the IP, they can make whatever derivative products they like, and you get royalties on those.