A competition website does not need a mobile app to launch. It needs one when repeat players become the business. The numbers from live operator apps Nera Marketing has built make the case: Rusboy Competitions holds 4.9 stars from 269 App Store ratings, and a single push notification from an operator app reaches around 3,690 subscribed players within minutes. Apps for UK competition websites start from £3,995, go live in about a month, and you own the developer account outright.

Does your competition website need a mobile app?

Not at launch. A mobile app is a retention tool, not an acquisition tool. Every operator app we have shipped went live months after the website, once there was a base of repeat players worth reaching. If you are pre-launch, build the website, get compliant, and prove the model first.

Once the base exists, the demand is real. Players search the app stores for operators they already buy from. The App Store listing of one large UK operator attracts an estimated 2,750 organic visits a month, more than most competition websites get in total. On Google Play, Rusboy Competitions has passed 1,000 downloads with a 4.9 rating from 90 reviews.

The pattern across our clients is consistent. The website wins the player. The app keeps them.

What an app adds that your mobile site cannot

Four things: a place on the player’s home screen, permission to send push notifications, a persistent logged-in session, and a store listing whose ratings sell for you. A mobile website, however fast, has none of these.

The persistent session matters more than it sounds. A returning app user is already logged in with payment details saved, so the distance from push notification to completed entry is two taps. On the mobile web, the same player may need to log in again, and every extra step costs entries. We wrote about that effect in our guide to reducing abandoned entries.

One honest caveat: push reach is capped by your install base. Push notifications only ever reach players who installed the app, so the app complements your email and SMS list rather than replacing it. Transactional email still does the heavy lifting for order confirmations, and it has its own battles, which we covered in our guide to email deliverability for competition websites.

Push notifications are the draw day sales lever

Here is what push actually does on a live operator app we manage: roughly 3,700 subscribed players, and each send delivered to about 3,690 devices within minutes. No spam folder. No inbox placement. No open-rate decay. Delivery is effectively 100 percent of the subscribed base, which no email list can claim.

Click-through depends heavily on what the push says. From 30 days of real sends:

Push type	Real example	Click-through rate
Winner announcement	“Has been found”	1.55%
Cash prize alert	“£500 cash”	0.92%
Draw reminder	“Live draw over the weekend”	0.49%
New competition listing	Prize spec details	0.19% to 0.43%

The lesson sits in the gap between the top and bottom rows. Draw moments outperform broadcasts by five to eight times. A winner announcement or a live draw reminder taps the same excitement that makes Facebook live draws sell tickets in the final hours. A generic product listing push barely registers.

Frequency tolerance is higher than most operators expect. This operator sends one to three pushes per day and the subscriber base held stable across the month, with unsubscribes per send close to zero. Players who install a competition app want to hear about draws. That is why they installed it.

One build decision to make before launch day: what a push tap opens. A OneSignal launch URL set to an ordinary web URL behaves like a web link and sends the player to the website, or worse the App Store, instead of into the app. Sending with no launch URL opens the app cleanly. Opening one specific screen inside the app needs universal links configured during the build, and behaviour differs between a fully closed app and a backgrounded one. If you want pushes that land on a specific draw page, say so before development starts.

When an app makes sense, and when it does not

An app earns its fee when three things are true: you have a few thousand past entrants, you run draws at least weekly, and you want players coming back without paying Meta for the privilege. If that describes your operation, push notifications alone justify the competition app build, because every draw announcement reaches your whole install base for free.

Instant win competitions strengthen the case further. Instant wins generate reasons to open the app between main draws, and the win-or-not moment is exactly the kind of event players want push notifications about.

Skip the app, for now, if you are pre-launch, if you run one draw a month, or if the £3,995 would otherwise fund the ads that build your player base in the first place. An app pointed at an empty audience does nothing. This is sequencing, not a verdict.

App Store and Google Play rules for competition apps

Both stores accept UK prize competition apps, but expect a fight. Getting Luxora Draws approved took roughly three weeks of review cycles and multiple rejected builds (versions 1.0(2), 1.0(3) and 1.0(4)), each cycle taking several days, before it went live on both stores. Every rejection came under a specific guideline in Apple’s App Review Guidelines, and every one is avoidable.

Expect an 18+ age rating on the App Store and PEGI 18 on Google Play, along with content flags such as “Frequent Contests” and “Contains Gambling”. Those flags are normal for the category and do not block approval. These four things do:

Apple guideline	What triggered the rejection	The fix
2.1(a) App Completeness	UK geo-restrictions blocked Apple’s reviewers	A review build with restrictions off, plus reviewer instructions in App Store Connect
2.3.3 Accurate Metadata	Designed mockups instead of real screenshots	Five real in-app captures at exact device resolution
2.3.6 Accurate Metadata	Age rating Apple believed was inconsistent	Correct chance-based activity answers, backed by a legal opinion
5.3.4 Gaming, Gambling, and Lotteries	Distribution set wider than our legal cover	UK-only availability matching the legal opinion

The geo-restriction catch-22

A compliant UK competition app must lock out players outside the UK, so ours enforces geo-location, IP, VPN and mock-location checks. Apple’s reviewers are not in the UK and test with mock locations, so the app blocked the exact people deciding its fate. Rejected under Guideline 2.1(a), tested on an iPad Air 11-inch M3.

Apple is explicit that a demo video is not enough. Reviewers need working access to the real features, with instructions in the App Review Information section of App Store Connect. We shipped a review build with the restrictions switched off, then switched everything back on the moment approval landed. The safer you make a regulated app, the harder you make it to approve, so scope the reviewer’s access path from day one.

The gambling classification trap

This is the highest stakes rejection. Apple flagged the app under Guideline 5.3.4 and told us to answer “Yes” to Gambling in the age rating questionnaire. That answer would have killed the app. Apple removes real-money gambling apps from operators without a licence, and a UK prize competition with a skill question and free postal entry route is deliberately structured to sit outside gambling law under section 14 of the Gambling Act 2005.

The correct age rating configuration for a prize competition app: Contests set to Frequent, Simulated Gambling set to None, Gambling set to No, Loot Boxes set to No. What ended the argument was a legal opinion letter confirming no gambling licence is required. Source the letter before you submit, not during an appeal. It is the difference between a firm answer and weeks of stalling. The same evidence requirement exists on Google Play’s real money gaming policy.

Screenshots must show the real app

Our first listing used designed mockups. Rejected under Guideline 2.3.3, and Google Play refused them too. Both stores want screenshots that show the actual app in use, and Apple required a set of five 6.5-inch iPhone captures. The specs are strict on pixel dimensions and aspect ratio, so an export at the wrong DPI or a forced 9:16 crop fails before a human ever looks at it. Treat store screenshots as a build deliverable, not a design afterthought.

Territory can never run ahead of your legal cover

Apple requires licensing evidence for every territory an app is distributed in, and it pushed back under Guideline 5.3.4 when our distribution was set wider than the legal opinion covered. We cut availability to the UK, matching the legal cover, and that objection closed. If you want more territories later, add the legal documentation first and appeal with it in hand.

End to end, Apple developer verification started on 21 April 2026 and, after the review cycles above, the iOS app went live on 21 May 2026, with Google Play approved the same week. One more quirk to plan around: a newly approved app takes a few days to appear in App Store search. We set up a direct redirect on the operator’s own domain, for example yourbrand.co.uk/app, so launch announcements work from day one regardless of store indexing.

What a competition website app costs in the UK

Our app builds start from £3,995 and cover both stores. Payment is in two instalments, with the second due when the app is delivered and live. The realistic timeline is about a month, and Apple’s verification and review cycles, not the development, set the pace.

Item	Detail
Price	From £3,995
Payment	Two instalments, second on delivery
Platforms	iOS App Store and Google Play
Timeline	About a month, including Apple review cycles
Push setup	Configured and handed over with a sending guide
Ownership	Your developer account, your app listing

The full scope of what is included sits on our competition website app build page. If you do not have a site yet, the app conversation comes second: the bespoke competition websites we build are the platform the app draws from.

How Nera Marketing builds competition apps

The app is a shopfront for the same platform that runs your website. Luxora Draws runs as a web-view app tied to its WordPress and WooCommerce site, and our newer builds, including Rusboy’s, are native Swift. Either way, competitions, ticket inventory, instant wins, and player accounts live in one place on the Nera Engine platform, so you manage everything once and both surfaces update. iOS beta releases go through TestFlight before submission, push runs on OneSignal, and the UK-only and 18+ restriction layers (geo-location, IP, VPN and mock-location checks) are built in because the law requires them.

Ownership works the same way as our website builds. The developer accounts are registered to your company, not ours. Check the store listings of our clients and the provider reads Rusboy Limited and Luxora Draws Ltd, not Nera Marketing. If we disappeared tomorrow, the apps would still be yours. Rusboy Competitions, our flagship client at £4.5M in year one revenue, runs its app on exactly this arrangement.

Push notifications are handed over, not held hostage. At go-live we configure the push platform under your app and send a plain guide for writing and sending your own notifications. Operators send their own pushes within days, and as the numbers above show, they get good at it quickly.

Getting your players onto the app

The launch playbook is short and it works. Announce the app to your full email list and socials using the direct yourbrand.co.uk/app link, not a store search instruction, because the app will not surface in store search for the first few days. Run a download incentive: one of our operators runs free giveaways for app downloaders, and players name it in their store reviews as the reason they installed.

Then push for ratings in week one. Store ratings are the app’s trust signal, visible before a player installs anything, and they compound. Rusboy Competitions’ 4.9 from 269 ratings now does the selling that no ad could. A competition app with a strong rating, a stocked instant win catalogue, and a weekly draw rhythm becomes the cheapest repeat-sales channel an operator owns.