1. Rule base 2FA online oracle.
Basically you would setup an M of N wallet with an Armory web service being one of the M. You could then go to a website provided by Armory and setup various rules (BTC per transaction, BTC per day, approved address, etc.). Using your desktop client you would make/sign a transaction. This would automatically get submitted to the web service. The service would check the transaction against the rules you have setup. If it matches any of the rules, it would be signed and transmitted to the bitcoin network. If not, the web service would make a request for a second form of authentication (SMS, email, HTOP, etc.)
2. Hosted watching only wallets.
Basically Armory would setup a website that looks exactly like the desktop client except it could only work with watching only wallets. You would create a wallet on your offline computer, export the watching only wallet, then upload it to this website. The website would be responsible for maintaining the blockchain and connections to the bitcoin network. When you want to perform a transaction, the website would give you a file to download. You would take this to your offline computer, sign it, then bring it back to the online computer and upload it. This will be useful to people that want to use bitcoin on computers with limited resources because they do not need to maintain their own set of data (currently ~40GB).
Both of these ideas could be developed independently, but in the end I would like to see them combined to create the ultimate low/no trust web wallet. It could probably even silence the people that say you can't trust any web wallet because it could just serve you different javascript. Nothing in either of the services that I described requires javascript to operate.
I like those ideas very much!
Especially the "Rule based 2FA" is great! This solves problems which weren't solvable until now!
Thumbs up, I like your thinking!
Ente