Essentially it'd be the same code, just different language... or even same language. AFAIK you'd have to still make a web request to your own (or a third party) bitcoind daemon or service, generate an address 'account' for the user and display it or hook their device app that hopefully supports bitcoin:// protocol, or pause the app and copy the address to clipboard for them to task switch over to wallet. There'd maybe be only one more step between your website third party and your own server to store in database the users unique device id and balance with account information so after a confirm you can have it available balance in credits or whatever.