For mobile device, or those env not suitable to run a local light client node, solutions like blockchain.info would be nice.
One js API to abstract both use cases.
Sent from my iPhone using Tapatalk
I guess the new API with username in openwallet is for this purpose. As this doesn't add too much complexicity to C code, I think it's fine.
But from security point of view, the unlocking of private key still happens on server. The fact that unlocking happens in browser makes me believe that I'm safe with blockchain.info wallet. I may choose another solution If I'm going to setup some online wallet services like blockchain.info. As I understand, the online wallet like blockchain.info only need to provide 2 things:
1. Storage of encrypted private keys.
2. Publishing signed transactions. This can be public interface and doesn't have to be done from one's wallet (means no login).