Your Guide to Launching an App (2026 Update)

Knowing how to start an app business in Australia comes down to doing five things in the right order: set up a structure that can own the app (usually a Pty Ltd company), make sure that entity owns the code and the brand, publish app-specific terms and a privacy policy, get through Apple and Google’s review, then keep the whole thing maintained after launch.

Here’s the honest bit. Most founders pour months into design and code, then treat the business and legal setup as a weekend job before submission. That’s backwards. The mistakes that cost real money, like a developer who legally owns your code or an App Store listing stuck in your personal name, all happen before launch, and they’re all avoidable.

What do you need to start an app business in Australia?

You need a legal structure, clear ownership of your intellectual property, a set of user-facing legal documents, and developer accounts with Apple and Google. Below is the order we’d tackle them in, because each step makes the next one easier.

Stage	What to sort out	Why it matters for an app
1. Structure	Company registration, ABN, business name if needed	Decides whose name appears as the seller on the App Store and who carries the liability
2. Ownership	Developer agreement, IP assignment, NDA	Makes sure the business (not a contractor or founder) owns the code
3. Brand	Trade mark search and application	Stops a rebrand after you’ve paid for downloads and reviews
4. User documents	App terms of use, privacy policy, subscription terms	Required by both stores and shaped by Australian consumer and privacy law
5. Store accounts	Apple Developer Program, Google Play Console	Organisation accounts need the company and a D-U-N-S Number first
6. Launch and maintain	Testing, submission, reviews, updates	Every new feature or data flow can change your legal documents

Notice where the app stores sit. Fifth. First-time founders often open a developer account on day one under their own name, then spend weeks untangling it once a company exists.

Should you start an app business as a sole trader or a company?

For most founders who want to start an app business with real users, a company is the better choice. Apps collect data, take payments and get used in ways you can’t fully predict, so the risk profile is higher than it looks from your laptop. A Pty Ltd company is a separate legal entity, which means claims and debts generally sit with the company rather than your house.

“Generally” is doing real work in that sentence, though. A company doesn’t make you bulletproof. Directors can still be personally liable for things like insolvent trading, breaches of director duties or personal guarantees you sign. The company protects you from ordinary business risk, not from everything.

The app store reason most guides miss

Apple’s organisation enrolment only accepts legal entities, and it verifies them using a D-U-N-S Number. Trading names and business names aren’t accepted. So if you’re a sole trader trading as “Budget Buddy”, you enrol as an individual, and your full personal name shows as the seller on your App Store listing.

Google has its own version of this. Personal Play Console accounts created after 13 November 2023 must run a closed test with at least 12 testers for 14 continuous days before they can go live. Organisation accounts skip that requirement. Registering a company first can save you a fortnight of chasing friends to keep a test app installed.

	Sole trader	Company (Pty Ltd)
Personal liability	Unlimited. Your personal assets are exposed	Generally limited to company assets
App Store seller name	Your personal legal name	Your company’s legal name
Google Play testing gate	Applies to new personal accounts	Organisation accounts are exempt
Raising investment	Not possible to issue shares	Can issue shares and set up vesting
Setup and running cost	Low	Higher, with ASIC fees and annual review
Best for	Testing an idea with no users or revenue yet	Anything you plan to launch, monetise or scale

If you’re going the company route, register your company before you sign with a developer or enrol in either store. That way the contracts, accounts and IP all start life in the right name.

Do you need an ABN and GST registration?

Yes, you’ll need an ABN for the business, and the app stores’ tax setup will ask for it. A company gets its own ABN, separate from any sole trader ABN you already hold. If you’re starting as a sole trader, you can apply for an ABN online in a few minutes.

GST registration kicks in once your GST turnover hits $75,000. One nuance for app founders: when you sell to Australian consumers through the App Store or Google Play, the store is generally treated as the supplier for GST purposes, so Apple or Google accounts for the GST on those sales. Direct web sales and B2B deals work differently. Talk to your accountant before you set prices.

Co-founders and holding companies

Starting with a co-founder? Put a shareholders agreement in place before the first line of code. It covers vesting, decision-making, and what happens if one of you walks away with half the equity and none of the work.

Some founders go a step further and hold the app’s IP in a holding company that licenses it to a separate trading company. The idea is that if the trading company gets sued, the core asset sits one step removed. It adds cost and paperwork, so it suits apps with real revenue or investor interest more than weekend projects. Get your accountant’s view on tax before you set it up.

Who owns your app’s code?

Whoever wrote it, unless a contract says otherwise. Under Australian copyright law, code written by an employee in the course of their job belongs to the employer. Code written by a freelancer, agency or offshore contractor belongs to them by default, even if you paid every invoice.

That default catches a lot of founders out. Without a written assignment, your developer could reuse the code, refuse to hand over the source files, or become the only person who can update your app. Investors will find this in due diligence, and it can stall a raise.

What your developer agreement should cover

Use a software development agreement before any work starts. At a minimum it should deal with:

• IP assignment. All code, designs and assets created for the project transfer to your business on payment.
• Source code handover. The developer delivers the full source files and repository access, not just a compiled app.
• Third-party and open-source components. The developer lists what they’ve used and confirms the licences allow commercial use. Some open-source licences can require you to publish your own code.
• Specifications, milestones and payment. Paying in stages against agreed deliverables means you still hold something back if the project drifts.
• Store account access. Your app should sit in your business’s developer accounts, with the developer added as a team member, never the other way around.
• Confidentiality and warranties. The developer keeps your idea private and promises the work doesn’t infringe anyone else’s rights.

One practical warning on offshore developers. A contract is still worth having, but enforcing an Australian judgment against a developer overseas is slow and expensive. Staged payments and access to the repository from day one protect you better than any clause.

Fixing ownership after the fact

Already built the app without a proper contract? Or wrote it yourself before the company existed? You can fix this with an assignment of intellectual property, signed by whoever currently owns the code, transferring it to your company. Do the same for the logo, designs and any content a freelancer created.

And before you pitch the idea to developers, designers or investors, have them sign a mutual non-disclosure agreement. It won’t stop someone building a similar app from scratch, but it does stop them walking off with your materials.

How do you protect your app’s name and brand?

Register a trade mark. A registered business name doesn’t give you exclusive rights to a brand, and neither does publishing first on the App Store. A trade mark registered with IP Australia is what lets you stop copycats using a confusingly similar name. You can register a trade mark for your app name and logo online.

Search before you build. If someone already holds a trade mark for a similar name in software, you could be forced to rebrand after you’ve spent money on downloads, reviews and paid ads. Rebranding an app means a new listing name, new screenshots and a confused user base. It’s a painful few months.

Most apps need protection in class 9 (downloadable software) and often class 42 (software as a service). If your app delivers a specific service, such as fitness coaching or education, you may need that service’s class too. Getting the classes wrong is one of the most common reasons founders end up with a registration that doesn’t cover what they actually do.

What about patents and copyright?

Copyright in your code, graphics and written content arises automatically in Australia. You don’t need to register it, and a copyright notice on every screen adds very little.

Patents are harder. Australian courts have been strict about software, and an app that simply runs a business process on a phone usually won’t qualify. If your app does something genuinely technical and new, speak to a patent attorney before you release it publicly, because public disclosure can destroy novelty.

What legal documents does an app need before launch?

At a minimum, an app needs terms of use and a privacy policy that match how the app actually works. Depending on your model, you may also need subscription terms, website terms and a separate end user licence. Here’s what each one does and where founders trip up.

App terms of use

Your mobile app terms of use are the contract between your business and your users. They set out what users can and can’t do, how payments and refunds work, who owns user content, when you can suspend accounts, and how far your liability goes.

Two details matter more than most people think:

• Use click-wrap acceptance. Make users tick a box or tap “I agree” at sign-up. Terms that users are only “deemed” to accept by using the app are far harder to enforce.
• Respect the consumer guarantees. A clause saying “no refunds under any circumstances” misrepresents your customers’ rights under the Australian Consumer Law. Liability limits need to be qualified with wording like “to the extent permitted by law”. Since November 2023, unfair terms in standard form contracts can attract penalties, not just be struck out.

Running a website alongside the app? You can often use one combined set of terms for both, provided it clearly covers each platform. Our guide on using the same terms for your website and app walks through when that works.

Privacy policy

Apple and Google both require a privacy policy for every app, and you need to link to it from your store listing and inside the app. A mobile app privacy policy explains what data you collect, why, who you share it with (including analytics and ad SDKs), and how users can access or delete it.

Many founders assume the Privacy Act doesn’t apply to them because of the small business exemption for businesses turning over less than $3 million. Be careful. The exemption doesn’t cover businesses that trade in personal information, such as passing user data to third parties for a benefit, or health service providers. And since 10 June 2025, individuals can sue over serious invasions of privacy under a statutory tort that applies whether or not you’re exempt.

There’s more on the way. From 10 December 2026, privacy policies for businesses covered by the Act must explain any automated decision-making that uses personal information and could significantly affect people. The OAIC’s Children’s Online Privacy Code must also be registered by that date, and it will apply to covered apps likely to be used by children.

Your store listing needs to match your policy, too. Apple’s privacy “nutrition label” and Google’s Data safety form ask you to declare what your app collects. If those declarations don’t match your privacy policy, expect a rejection or, worse, a complaint.

Do you still need an EULA?

Sometimes. If you don’t supply your own licence, Apple applies its standard Licensed Application End User Licence Agreement, which is governed by Californian law. That’s not ideal for an Australian business, and Apple lets you replace it with your own terms.

For most consumer apps, though, well-drafted terms of use that include a licence to use the app do the job. A standalone EULA makes more sense for downloadable software, SDKs or desktop tools. Don’t pay for two documents that say the same thing.

Apps with children, health or sensitive data

Is your app aimed at children or likely to attract them, or does it collect health, biometric, location or family information? Then your privacy obligations step up. You’ll need explicit consent flows, careful parental consent where children are involved, and a privacy policy written for your actual data flows rather than a generic one. Social media style apps should also check whether the minimum age rules for social media platforms, in force since December 2025, apply to them.

What changes for subscription apps in 2027?

Parliament passed the Competition and Consumer Amendment (Unfair Trading Practices) Act 2026 in July 2026. From 1 July 2027, it bans unfair trading practices and subscription traps across the Australian Consumer Law. If your app runs on free trials and auto-renewals, this is the change to plan for now.

In practical terms, businesses offering subscriptions will need to disclose key information before sign-up, notify customers at important points in the subscription, and give them a clear, simple way to cancel. The broader ban also targets manipulative design, often called dark patterns, such as fake countdown timers or cancel buttons hidden three menus deep.

A common assumption is that Apple and Google handle all of this because they process in-app payments. They handle the billing. You’re still responsible for how your app presents offers, what your terms promise, and whether your onboarding pushes people into something they didn’t mean to buy. Build honest subscription screens now and 2027 becomes a non-event.

How do you launch an app on the App Store and Google Play?

Once the business side is in place, launching an app follows a similar path on both stores: enrol, build and test, prepare your listing, submit for review, then release. The details differ, and those details are where launches stall.

	Apple App Store	Google Play
Account	Apple Developer Program, about A$149 a year	Google Play Console, a one-off US$25 fee
Organisation enrolment	Legal entity plus D-U-N-S Number	Organisation account with D-U-N-S Number
Testing before launch	TestFlight is optional but strongly recommended	Mandatory 12 testers for 14 days for new personal accounts
Privacy disclosures	Privacy nutrition label plus privacy policy link	Data safety form plus privacy policy link
Search keywords	App name, subtitle and a 100-character keyword field	Title, short description and full description are all indexed
Description limit	4,000 characters	80-character short description, 4,000-character full description

Fees change, so check the current amount when you enrol.

Launching on the App Store

You’ll manage your app through App Store Connect (the tool older guides still call iTunes Connect). Before you submit, run a beta through TestFlight on real devices, not just the simulator. Apple rejects apps for crashes, broken links, placeholder content and missing login details for the reviewer far more often than for anything exotic.

Two requirements catch founders out. If users can create an account in your app, they must also be able to delete it from within the app. And your privacy label has to reflect every SDK in your build, including analytics and crash-reporting tools you didn’t write yourself.

Launching on Google Play

Google Play also requires a privacy policy link and a completed Data safety form, plus a working way for users to request account deletion. If you’re on a new personal account, the closed test is the real bottleneck. The 14 days must be continuous, and if your opted-in testers drop below 12, the clock effectively resets. Recruit more than 12 so ordinary drop-off doesn’t cost you another two weeks.

Why first submissions get rejected

Most rejections are boring, which is good news, because boring problems are easy to prevent. The usual suspects are crashes on a device you didn’t test, a login screen with no demo account for the reviewer, placeholder text or broken links, a privacy policy URL that doesn’t load, and privacy declarations that don’t match what the app actually collects.

Apps that let users pay for digital content outside the store’s own billing system also draw attention, because both stores have detailed rules about in-app purchases. If your model involves web payments, read the current payment guidelines before you design the checkout, not after the rejection email.

A rejection isn’t the end of the road. Read the reason carefully, fix exactly what the reviewer flagged, and reply through the resolution centre if something was misunderstood. Most apps get through on the second attempt.

Writing a store listing that gets found

App Store search doesn’t read your description, so your keywords need to live in the app name, subtitle and keyword field. Don’t repeat words across those fields; Apple already combines them. Google Play works more like a search engine and reads your full description, so write it for humans first and use your main terms naturally.

Either way, the first two lines of your description do most of the selling, because that’s all people see before tapping “more”. Lead with the problem you solve, not your feature list. And set up a simple website for the app. It gives you somewhere to host the privacy policy and support page both stores ask for, and it helps journalists and search engines find you.

What we see in Lawpath consultations

Lawpath lawyers speak with founders working out how to start an app business every week, from pre-revenue side projects to funded startups preparing for launch. The same handful of problems comes up again and again.

• The code or accounts sit in the wrong name. A consistent pattern is IP owned by the founder personally, or by the developer, with the app live in an individual developer account. The fix is usually an IP assignment deed into the company and a store account transfer, which is far easier before launch than after.
• AI-generated or copied documents that don’t match the app. Founders increasingly arrive with drafts from AI tools or other apps. The common gaps are data flows the policy never mentions, subscriptions described as in-app when they’re actually sold on the website, and references to the “National Privacy Principles”, which were replaced by the Australian Privacy Principles back in 2014.
• Refund and liability clauses that break consumer law. Blanket no-refund clauses, liability exclusions with no “to the extent permitted by law” wording, and terms users only accept by using the app are among the most common fixes our lawyers make.
• Children’s and sensitive data treated as ordinary data. Education, health, family and co-parenting apps often collect far more sensitive information than the founder realises. These need tailored consent flows and a privacy policy built around the actual data.
• Unclear subscription mechanics. Where users pay, when they’re charged, how renewals are notified and how cancellation works are often left vague. Many advisers also recommend limiting paid subscriptions to users aged 18 and over so each subscriber can contract in their own name.
• Insurance as an afterthought. Professional indemnity and cyber insurers often want to see your final terms before quoting. Getting the terms right first can make cover easier to arrange.

None of these are exotic. They’re the normal result of building fast, and they’re all cheaper to fix before your first thousand users than after.

What happens after you launch your app?

Launch day is when the maintenance job begins. Keep an eye on crash reports in App Store Connect and Play Console, respond to reviews (both stores let you reply publicly), and ship fixes quickly while your early users are still forgiving.

Treat your legal documents like part of the product. Every time you add a new SDK, payment option, AI feature or data collection point, check whether your privacy policy, store disclosures and terms still describe what the app actually does. Out-of-date documents are one of the quietest risks in an app business, because nobody notices until a regulator, user or investor does.

A simple habit works well: put a legal check on your release checklist for any update that changes what data you collect, what you charge, or who can use the app.

Checklist: how to start an app business in Australia

• Company registered, with its own ABN (and GST if you’re over or near $75,000)
• Shareholders agreement signed if there’s more than one founder
• Developer agreement signed, with IP assignment and source code handover
• Any existing IP assigned from founders or freelancers to the company
• Trade mark search done and application filed for the app name and logo
• D-U-N-S Number obtained and organisation developer accounts set up
• Mobile app terms of use with click-wrap acceptance in the sign-up flow
• Privacy policy that matches your real data flows, linked in-app and in both store listings
• Apple privacy label and Google Data safety form completed and consistent with the policy
• In-app account deletion working
• Subscription screens that clearly show price, renewal and how to cancel
• Beta tested on real devices (and the 14-day Google test completed if it applies)
• Support website live with contact details and your legal documents

Frequently asked questions

How much does it cost to start an app business in Australia?

Development is the big cost and ranges widely depending on complexity. On top of that, budget for company registration and ASIC fees, a trade mark application, your legal documents, the Apple Developer Program (about A$149 a year) and a one-off US$25 Google Play fee. Legal setup is usually a small fraction of the build cost.

Can I start an app business as a sole trader?

Yes, but you’ll carry unlimited personal liability, you’ll publish on the App Store under your own personal name, and a new personal Google Play account faces a 14-day, 12-tester testing requirement. A sole trader setup suits testing an idea. Most founders switch to a company before launch.

Do I need an ABN to publish an app?

If you’re running the app as a business, yes. Both stores’ payment and tax setup will ask for your business details, and you need an ABN to trade in Australia. A company gets its own ABN, separate from any sole trader ABN you already hold.

Does my app need a privacy policy if I don’t collect personal information?

Yes. Apple and Google require a privacy policy for every app, whatever it collects. In practice, most apps do collect personal information through sign-up, analytics, crash reports or advertising SDKs, even when the founder thinks they don’t.

Who owns the code if I pay a developer to build my app?

The developer does, unless a written agreement assigns it to you. Australian copyright law gives ownership to the person who creates the work, except for employees working in the course of their job. Get a signed IP assignment and the full source code handed over.

Should I trade mark my app name before launching?

Yes, ideally before you build. A registered trade mark gives you exclusive rights to the name in your chosen classes, while a business name or App Store listing gives you none. Most apps need class 9, and often class 42.

Do Apple’s and Google’s terms protect my business?

No. Their developer agreements protect Apple and Google. You still need your own terms of use and privacy policy to govern your relationship with your users and limit your liability. Their refund policies also don’t override the Australian Consumer Law.

How long does it take to launch an app on the stores?

Apple’s review commonly takes a day or two, but allow extra time for a first submission and possible rejections. On Google Play, a new personal account needs at least 14 days of closed testing before it can even apply for production. Build a buffer of a few weeks into your launch date.

What changes for subscription apps from July 2027?

From 1 July 2027, the ban on unfair trading practices and subscription traps starts. Subscription apps will need clear pre-sign-up disclosure, notices at key points in the subscription, and a simple way to cancel. Manipulative design patterns will also be prohibited.

Can I use one set of terms for my website and app?

Often, yes, as long as the document clearly covers both platforms and reflects how each works, such as whether subscriptions are bought on the web or in the app. If the website and app do very different things, separate terms are cleaner.

Feeling a bit overwhelmed? That’s normal. Learning how to start an app business means learning three new rulebooks at once. You don’t need everything perfect on day one. You need the structure right, the code in your name, and honest documents that match your app. Founders who sort those three out before launch are already ahead of most of the apps in the store.

The easiest next step is to hand the setup to people who do it every day. Get a fixed-fee quote from a Lawpath lawyer to set up your app’s structure, IP and launch documents in one go, then get back to building.