iOS, Android and cross-platform
Mobile development for iGaming operators
Most of your players are on a phone, and the store between you and them has an opinion about real-money gambling. Argon builds native and cross-platform apps for casino, sweepstakes and sportsbook brands, handles the store submission and the licence paperwork that goes with it, and tunes for the mid-range Android device your analytics say is the real median.
01
Where teams get stuck
- Store review keeps rejecting the build
- Real-money gambling apps face extra requirements on both stores: licence documentation, geographic restriction, age assurance and account-holder verification. Most rejections are process, not code.
- The web app feels wrong in a shell
- Wrapping a responsive site in a webview and shipping it produces scroll jank, broken deep links, no push, and cashier flows that fight the keyboard.
- It only performs on the test device
- Lobby scrolling, game launch and in-play updates behave very differently on a three-year-old Android handset on a mobile network, which is what a large share of your traffic actually is.
iGaming consideration
State and country level restrictions need device-level location, VPN and emulator detection, and a graceful blocked experience that does not look like a bug.
02
What we do
- Cross-platform delivery
- React Native and Expo where one codebase and fast iteration matter, with native modules dropped in for geolocation, biometrics and anything the bridge should not own.
- Native iOS and Android
- Swift and Kotlin when the product needs platform-grade performance, deep OS integration or a store position that cross-platform cannot reach.
- Progressive web apps and native shells
- A pragmatic route to market in jurisdictions or app categories where a store listing is restricted, including install prompts, offline states and push where the platform allows it.
- Store submission and compliance
- Licence evidence per territory, age rating, geographic availability, account deletion requirements, privacy manifests and the review correspondence. We drive it to approval.
- Payments and cashier in-app
- Deposit and withdrawal flows that respect store rules on in-app purchase, integrated with your existing payment providers rather than a parallel mobile-only path.
- Retention plumbing
- Push notification infrastructure wired to your CRM, deep and deferred deep links, attribution SDKs, and in-app messaging that marketing can drive without a release.
- Release engineering
- Automated builds, signing, staged rollout, over-the-air updates where permitted, crash and performance monitoring, and a rollback path that does not need a store review.
03
What you receive
- Shipped applications live in the App Store and Google Play under your developer accounts
- One maintainable codebase with a documented architecture and design system
- CI/CD pipelines for build, sign, test and staged release
- Automated end-to-end suite running on a real device matrix
- Crash, performance and funnel monitoring wired up from day one
- Release runbook and store submission playbook your team can repeat
04
How the work runs
01
Discovery
Player journeys, analytics on the devices you actually have, store constraints per territory, and the scope of release one.
02
Architecture and design
App architecture, offline and error states, navigation model, design system, and the API contracts we need from your platform.
03
Build in increments
Two-week cycles, a testable build on your device every cycle, and functional software rather than a demo at the end.
04
Device lab and hardening
Real-device testing across the matrix, network throttling, battery and memory profiling, accessibility and localisation passes.
05
Submission
Store assets, licence evidence, privacy disclosures, review responses, and a phased rollout on approval.
06
Post-launch
Crash triage, funnel analysis, performance tuning and an agreed cadence of releases after launch.
05
Why iGaming differs
- Geolocation is a hard requirement, not a feature
- State and country level restrictions need device-level location, VPN and emulator detection, and a graceful blocked experience that does not look like a bug.
- Responsible gaming lives in the UI
- Deposit limits, reality checks, session timers, self-exclusion and cool-off have to be reachable, honest and impossible to lose in a menu. Reviewers check this.
- Store rules differ by product and territory
- What is permitted for a sweepstakes app in the US, a casino app in Malta and a sportsbook app in Canada are three different submissions. We treat them that way.
06
Tools and methods
- Cross-platform
- React Native · Expo · TypeScript · React Query
- Native
- Swift · SwiftUI · Kotlin · Jetpack Compose
- Delivery
- Fastlane · EAS · GitHub Actions · Firebase App Distribution
- Runtime
- Sentry · Firebase · AppsFlyer · Adjust · Detox · Maestro
- Typical team
- Mobile lead, 2 to 4 engineers, designer, QA
07
Questions
React Native or fully native?
React Native for most operator apps: one codebase, one team, fast release cadence, and native modules where it matters. Fully native when the app is the product and every frame counts, or when a platform capability has no reliable bridge.
Can you get a real-money gambling app approved?
Yes, in the territories where your licences permit it. Approval is mostly evidence and configuration: correct licence documentation, correctly scoped geographic availability, correct age rating, and responsible gaming surfaces where the reviewer expects them.
Can you take over an existing app?
Yes. We start with a short assessment of the codebase, the pipelines and the store accounts, then give you a plain answer on whether to continue, refactor or rebuild, with the cost of each.
Who owns the developer accounts and the code?
You do, always. The apps ship under your store accounts and the repositories are yours from the first commit.
Related
- Engagements
- Under NDA as standard
- People
- Background-checked engineers
- Data
- GDPR and DPA ready
- Infrastructure
- World-renowned cloud providers
Next step
Tell us what you are building, or what you are about to buy.
One working day to a reply, from an engineer rather than an account manager. Under NDA as standard, before anything is shared.