Project Description
I’m building a self-contained virtual core that runs cleanly from Android 9 through 17. The goal is to let any embedded game call the native Facebook, Twitter, Google or other social-login SDKs directly, with zero crashes and the same frame-rate smoothness you would expect on a physical device. No standard “virtual SDK” tricks—I need an isolated space that looks and behaves like genuine Android, yet never bleeds into the host environment.
Security is critical. The core must slide past ACE checks and similar anti-tamper routines, all while a custom licensing layer keeps tight control over which apps can launch inside. My model blocks by both package name and visible app name, and I’ll cap the total number of authorised packages. If someone tries to exceed that cap, the licence should quietly refuse the launch.
I also need full remote authority over every deployment: I must be able to deactivate any seat instantly, watch usage metrics in real time, and grant or revoke specific user roles without shipping a new build. In short, remote deactivation, usage tracking and granular user-access management are all mandatory.
Implementation detail: the limitation mechanism should rely on a simple counter of maximum installs rather than whitelists or manual approvals; once the cap is hit the service rejects fresh installs until I raise the ceiling.
Deliverables
• A compiled virtual core APK (or AAB) that supports Android 9–17, bypasses ACE, and exposes clean social-login hooks.
• A companion licensing server (dashboard plus API endpoints) meeting the control requirements above.
• Documentation covering integration steps for third-party game studios, plus a short test suite that shows the licence cap, remote kill switch and usage analytics in action.
Send a quick outline of the architecture you’d propose, the key libraries or frameworks you’d lean on, and a timeline for the MVP. I’m ready to start as soon as I see a plan that keeps performance high and control in my hands.