Menu

Contact

hello@aveny.co

Voisary Blog
1 min read

Why an indie studio does not need a domain per app

Every new app used to mean a new domain, a new site and a new bill. We stopped doing that, and nothing broke.

Every time we shipped something, the ritual was the same: buy a domain, spin up a landing page, wire the legal documents, pay the yearly bill. Four apps in, that ritual costs more than the apps earn.

What the App Store actually asks for

Apple wants three working URLs: a privacy policy, a support page and a marketing page. It never asks who owns the domain. A path on a domain you already own satisfies the review just as well as a domain bought for one app.

What we do instead

Everything lives under one roof now. Each product gets a folder of markdown, and the site builds the product page, the legal documents and the sitemap entries from it. Adding an app is adding a folder — no code, no deploy config, no new bill.

A domain still makes sense in three cases: the product lives on the web, you are selling to businesses who will judge you by the address, or the app took off and pays for itself. Everything else is a subscription to your own optimism.