Alt Text: Young person using a mobile phone in a park
Millions of Android users search for sports betting applications every week, only to encounter a restriction message in their official store. The industry’s response has been distribution via APK files downloaded outside the Google store.
A common version among Android devices in the country is the 1 x bet Republic of Ireland – a market where Google Play does not include real money gambling categories among its permitted applications.
Fewer Than 40 Markets Have Access to RMG Apps on Google Play
Google maintains a public registry of jurisdictions where real money gambling apps are authorized, referred to as RMG in the Play Console documentation. As of February 2026, it does not exceed 40 entries. The following table details the product categories that Google recognizes and their access conditions.
| RMG Category | Publishing Condition in Play Store |
| Online Casino | Local gambling license verifiable by Google |
| Sports Betting | Specific license for the market where the app is distributed |
| Horse Racing | Regulated and licensed separately from generic sports betting |
| Lotteries | In most markets, governmental operators only |
| Daily Fantasy Sports | Permitted where local legislation classifies them outside of gambling |
Source: Google Play Console, “Country/region allowances for gambling apps” section, accessed February 2026.
Within Latin America, for example, only a select few markets appear in Google’s registry with some type of permitted access. The rest, including several with high Android penetration, remain completely excluded.
Android accounts for approximately 79.6% of the mobile market share in the region according to early 2026 data. In the excluded markets, the APK file functions as the primary access channel.
How a Betting App Reaches a Device Without the Play Store
Google requires RMG app developers to implement geo-blocking, preventing use from territories not covered by the developer’s gambling license. An operator can have millions of registered users in markets where it operates legally but lack permission to publish its app in the official store destined for those same territories.
The direct installation process follows a specific five-step sequence:
- The user accesses the operator’s website from their Android device’s browser.
- Downloads the .apk file hosted on the operator’s servers.
- Android requests authorization to install from sources outside the store.
- The user enables the permission in their device’s security settings.
- The installation executes, and the app becomes operational without Google’s intervention.
Android has allowed this flow natively since its early versions, facilitating its mass adoption in markets with store restrictions.
Live Odds Cannot Wait Days for a Review
Live sports betting applications depend on the speed with which their odds reflect what is happening during a match. A score change modifies the betting lines in a matter of seconds, and the app needs to respond with the same urgency.
Update publishing times differ based on the channel chosen by the developer.
| Channel | Average time to publish an update |
| Google Play Store (standard app) | 24 to 72 hours |
| Google Play Store (complex app: fintech, betting) | 4 to 7 days, up to 7+ in high-demand periods |
| Direct APK distribution | Minutes after uploading to the operator’s server |
Data on Play Store review times: developer forums and Google Play Console documentation, 2025.
When an operator distributes via APK, they push the update to their servers, and the app notifies the user about the availability of a new version. The complete release cycle is drastically reduced, allowing them to correct odds errors and incorporate new sports markets with an agility that store reviews cannot match.
Google Prepares Sideloading Restrictions for September 2026
Google announced plans in August 2025 to restrict the installation of APK files from unverified sources on certified Android devices. All developers, including those who distribute exclusively outside the official platform, will need to verify their identity in the Android Developer Console.
Implementation Schedule
The initial rollout will cover four markets in Southeast Asia and Latin America (Brazil, Indonesia, Singapore, and Thailand) starting in September 2026, with global expansion planned for 2027. Google bases the decision on security data indicating a significantly higher concentration of malicious software in apps downloaded outside the official platform.
What Changes for Betting Companies
Mandatory verification does not eliminate sideloading as an app delivery method. It introduces a developer identification requirement that did not previously exist, and operators with a legitimate presence in multiple markets can comply with it without friction.
Sideloading is No Longer a Technical Gesture
Omdia reported 140.5 million smartphones sold in Latin America during 2025. In the Chilean market, DataReportal registered an internet penetration of 94.5%, with 18.8 million people connected out of a population of 19.9 million at the end of that year.
The frequency with which millions of these users perform APK downloads of betting applications has generated a rarely discussed effect. Enabling unknown sources and verifying installation permissions are steps that a large part of Latin American users execute naturally. Betting companies have contributed to normalizing a process that, a decade ago, was associated exclusively with advanced technical users.
Leave a Reply