Make native better
Improve performance, discovery and the journey into gameplay.
ENTAIN · NATIVE CASINO · PORTFOLIO LEADERSHIP
Native had to be better. Not just more expensive.
I led product strategy and delivery across Entain's native casino portfolio — more than 40 iOS and Android apps spanning 10 major brands and multiple regulated markets.
The opportunity with native was obvious: faster, richer experiences and more control over how players discovered and returned to games.
The problem was making that advantage work at scale.
40+Native casino apps
10Major brands
16 secFaster to first game
+20%Avg. session duration*BetMGM US native app vs wrapper experience.
01 · The trade-off
Native gave us more control. It also gave us more work.
Native could provide a faster, more responsive and better-designed casino experience. It also created more integration and development overhead than wrapper products.
Across more than 40 apps and 10 brands, that overhead became a significant product and operational challenge.
There was little point having the better experience if the games players wanted weren't there.
02 · My role
This wasn't one app or one feature.
I owned product strategy and delivery across the native casino portfolio, working across multiple squads and Product Managers and partnering with Commercial, Casino, Engineering and senior stakeholders.
The strategy had two priorities, and neither could succeed without the other.
Make native easier to scale
Improve the speed and repeatability with which content could reach the portfolio.
03 · The experience
Getting to a game shouldn't feel like work.
We improved the experience around faster access to relevant content: Recently Played, personalised game discovery and the journey from login to game launch.
The point wasn't that native looked nicer. Players were behaving differently.
04 · The content problem
A great casino experience still needs great content.
Casino is a fast-moving content product. Native could deliver the better experience, but slower game integrations could undermine that advantage.
At the scale of more than 40 apps, content integration had become a product problem rather than simply an engineering task.
Experience↔Speed to market
06 · Operating at scale
The strategy had to work beyond one app.
40+Apps
→10Brands
→MultipleMarkets
The portfolio covered more than 40 apps, 10 major brands and multiple regulated markets, including native casino rollout across multiple US states.
Product leadership at this scale meant creating enough consistency to move the portfolio forward while allowing individual markets, brands and teams to respond to their own context.
That's much closer to the work I enjoy: setting the direction, making the trade-offs clear and giving good teams enough context to move.
07 · Outcomes
What I'd take from it
Better UX isn't enough.
Native gave us opportunities that wrapper apps couldn't.
We could make things faster. Improve discovery. Make it easier for players to get back to games they enjoyed.
But none of that mattered if the content couldn't keep up.
The interesting problem wasn't choosing between experience and speed to market.
It was figuring out how we could improve both.
Next case study · 01We couldn't remove KYC. So we removed the unnecessary work around it.