Splitting it into installers wasn’t my idea, but the current implementation of installers is mine and the idea to have it replace itself with the game is also my idea. Original ones didn’t share ID, so they had to be manually removed from the device, they required running in a specific order and didn’t have any built in checks for already installed assets and didn’t install the game itself at the end. It’s not really a bigger security risk than manually installing the app because android doesn’t give permanent permission to install apps like for example you can get for file system access with legacy API. Instead access has to be requested every time you try to install app or at least that was my understanding when I researched on how to do it. I do plan to try an even better way eventually if possible that doesn’t even require legacy permissions or app installing permissions (although I would still prefer to keep using file system access for user convenience with saves) but I haven’t really started working on it so I don’t know if it will work. I’d completely get rid of legacy permissions if android didn’t make it almost impossible for regular users to access app internal storage without using PC/rooted phone.