Here’s What Android 17 Means for Gaming and Lottery

What Operators Need to Know 

Android 17 has introduced changes across critical player journeys, making end to end testing essential. 

- Location permissions are becoming more visible, putting greater emphasis on clear permission UX and recovery journeys.  
- OTP protections are tightening across web and native experiences, making registration and account recovery key testing priorities.  
- Apps need to work across more screen sizes and orientations, particularly tablets and other large-screen devices.  
- Security and app distribution are evolving, with greater scrutiny around sideloading and unverified apps.  
- AI is becoming more embedded in Android, creating future opportunities for more intelligent on-device experiences.  

Key takeaway: Don't just ask whether your app works on Android 17. Ask how the update has affected the complete player journey. 

Android 17 was released back in June, this release goes considerably further than another round of performance and security improvements. Google describes it as the beginning of Android's transition towards an intelligence system, while also introducing changes across privacy, security, connectivity, performance and the way apps work across different devices.  

Android 17 introduces a wide range of features and behaviour changes, including enhanced privacy controls, enforces adaptive experiences across large-screen devices' given this process started in Android 16, multitasking improvements, gaming optimisations for foldables and Google's continued move towards AI-powered experiences. While not all of changes will affect lottery and gaming operators equally, several sit directly within critical player journeys.  

At mkodo, we've been developing mobile experiences for lottery and regulated gaming for more than two decades. New operating system releases, such as Android 17, are about understanding what has changed, what this means for players and what opportunities it might create for your app. With Android 17, location permissions, OTP security and increasingly varied Android devices are three areas we'd have firmly on the testing list. 

Location is becoming more transparent 

Perhaps the most relevant Android 17 development for regulated gaming is Google's continued focus on location privacy. Android 17 introduces a new Location Button, a system rendered element that enables users to grant precise location access for the current session. Google says the approach is designed to reduce the friction associated with repeated temporary permission prompts while giving users greater control over when precise location is shared. For gaming operators, that creates an interesting UX consideration. 

Location verification is fundamental in many regulated markets, but players don't necessarily understand why a sportsbook, casino or lottery needs access to their precise location. Android 17 puts that decision even more visibly into the player's hands. The OS also introduces a persistent location indicator when a non-system app accesses location. Players can tap it to see which apps have recently accessed their location and manage permissions directly.  

That means operators should think beyond whether their location technology technically works. Is the player being given enough context to understand why location is required? What happens if they change that permission? And how easily can they recover the journey if location access isn't available?  

Android 17 makes good permission UX more important, not less. 

Approximate location is changing too 

There's another location development worth watching. Android's approximate location system previously used a fixed 2km-wide grid. Android 17 introduces a population density based approach, allowing the approximate area to vary according to how populated the surrounding location is. Google says the change is intended to provide better privacy, particularly in sparsely populated areas.  

For regulated gaming, this reinforces a point GeoLocs has made for years: an approximate location signal and a compliance grade location decision are not the same thing. 

Operators should therefore test how their complete geolocation stack behaves on Android 17, particularly where precise location is necessary and around jurisdictional boundaries. 

Registration deserves attention as well 

Location isn't the only player journey we'd be watching. Android 17 expands protections around SMS one time passwords (OTPs), making registration, login and account recovery important areas for operators to test. 

For web content and WebView experiences, WebOTP provides a route for receiving and autofilling verification codes. Android 17 strengthens protections around WebOTP-formatted messages so that apps that aren't the intended recipient cannot access them immediately. 

For native Android experiences, SMS Retriever and SMS User Consent provide the recommended approaches for accessing verification codes without relying on broad SMS permissions.  

For operators, the important point isn't simply whether an SMS arrives. Test the complete journey: request the code, receive and populate it, complete registration, then continue into verification, deposit or ticket purchase. A small break early in that sequence can quickly become a conversion problem. 

Don't assume every Android player is using the same screen 

Android 17 also continues Google's push towards adaptive applications. For apps targeting Android 17, developers can no longer opt out of orientation and size change requirements on large screen devices. Apps need to adapt appropriately across environments such as tablets, that matters because “Android compatibility” isn't one device test. 

Gaming interfaces can contain complex navigation, bet slips, game content, account journeys and transaction flows. Lottery apps may combine ticket purchasing, scanning, results and account functionality. Operators should make sure those experiences remain usable when the available screen space and orientation change. 

Security and performance are changing underneath the experience 

There are several less visible changes operators shouldn't overlook either.  

Android 17 continues Google's move towards a more tightly controlled security environment. Advanced Protection Mode, first introduced with Android 16, continues to evolve, with safeguards including tighter restrictions around apps installed from unknown sources. 

For gaming operators, this puts greater focus on app distribution. As Android tightens protections around sideloading and unverified apps, operators distributing outside Google Play should consider how these changes could affect installation journeys. Getting apps onto Google Play – and continuing to meet its policies – may become increasingly important compared with relying solely on self-served APKs. 

Android 17 also introduces stricter memory limits and additional network and privacy protections. These changes may be largely invisible to players, but a small platform change can still result in a crash, broken integration or interrupted journey – making thorough testing essential. 

 Android is becoming more AI-aware 

Perhaps the biggest strategic change is Google's direction of travel. Android 17 marks the start of what Google calls its transition to an “intelligence system”, putting apps at the centre of increasingly intelligent experiences. One technical indication of that shift is a new requirement for apps targeting Android 17 to declare an android.hardware.npu feature if they need access to a device's Neural Processing Unit.  

For gaming and lottery operators, this is less about immediately adding AI into every player journey and more about being ready for a mobile ecosystem in which on-device intelligence becomes increasingly important. 

Operators should be considering where AI can genuinely improve the experience, from personalisation and customer support to fraud detection and understanding player behaviour – while making sure any implementation continues to meet expectations around security, privacy and responsible gaming. 

The opportunity isn't to use AI because Android supports more of it. It's to understand where intelligent, on-device capabilities could make the player experience meaningfully better. 

What would we test first? 

For an operator, we'd prioritise four journeys: registration and OTP verification; location permissions and geolocation; notifications, critical third-party SDKs and the complete player experience across representative phones and tablets. 

Then we'd look at the data.  

Has permission behaviour changed?  
Are location verification attempts increasing?  
Has registration completion moved?  
Are particular Android 17 devices generating more support requests, crashes or abandonment? 

Google itself recommends running through all app flows when testing against Android 17. This update isn't simply another compatibility exercise. It represents a wider shift towards more intelligent, privacy- conscious, adaptive and secure mobile experiences. 

For operators, the question shouldn't simply be “Does our app work on Android 17?” It should be: “What has Android changed, what opportunities does that create and what does it mean for our players?” 

With more than two decades of experience developing mobile products for lottery and regulated gaming, mkodo works with operators to understand, test and optimise their applications as mobile technology evolves. If you want to know what this update  means for your app or player journeys, speak to our team about preparing for a future update.