Case study
Playtech Platform — Native Android SDK for .NET Avalonia: authentication & identity verification
One-page summary: problem, solution, tech, timeline, outcomes, and code ownership.
Case study summary
- 1. Problem: Playtech needed high-assurance authentication that worked natively inside a .NET Avalonia product — including biometrics and OTP — across cashier terminals and end-user mobile devices.
- 2. Solution delivered: moblers built a native Android SDK integrated with Avalonia, plus two dedicated native Android authentication apps, with secure terminal-to-mobile session handoff.
- 3. Tech stack: Native Android SDK; .NET Avalonia host integration; OTP step-up auth; facial biometrics via CAF and Unico; web-based omnichannel session handoff; two standalone native Android auth apps.
- 4. Timeline: End-to-end SDK development, provider integration, and delivery of two dedicated native authentication apps (duration as published: end-to-end engagement; exact calendar dates not listed on the public page).
- 5. Outcomes / metrics: Unified authentication across terminal and mobile; dual biometric providers for regional flexibility; native performance for facial verification vs web-only flows; cohesive auth architecture across the Playtech platform.
- 6. Code ownership: Clients received full ownership of the source code, repo, binaries and deployment artefacts.
Playtech FAQ
What did moblers build for Playtech?
A native Android authentication SDK for .NET Avalonia with OTP, CAF & Unico facial auth, two companion apps, and terminal-to-mobile handoff — with full source-code ownership. https://moblers.com/case-studies/playtech/
Want a similar outcome?
Share your idea, Figma, or deadline — we will scope a measurable delivery plan.