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.
Thanks for describing that approach. I'd like to use a dedicated API rather than my own creation to save time and avoid making mistakes that could cause people to send money to the wrong address or something.
There is always my PHP kit you can integrate with flash or w/e really.
http://github.com/Xenland/Bitcoin-Development-Kit
The website is http://bitcoindevkit.com but the server is down right now.
Thanks Xenland, I think your kit may do what I need. Please let me know when your server gets back up.http://github.com/Xenland/Bitcoin-Development-Kit
The website is http://bitcoindevkit.com but the server is down right now.