Slow Roll Oauth/id/Login, payment and wallet sophistication

@humbitious commented on [Sat Jan 26 2019](https://github.com/ConsenSys/web3studio/issues/19)

## Overview

As a user, I want to start off with a bootleg app without having to create a new "decentralized" ID or have to figure out Metamask, uPort or how to manage my private keys and wallets, etc. (As the user, I'm fine logging in with my google authentication and then get migrated over time as the value of my assets gets scary and I start to worry about the Bootleg company/provider managing my token keys.) And I'm fine paying for bootlegs with credit card, especially if over time the system promps me to take control of buying with tokens directly...or Adhara and other service allows direct bank account/funds without having to deal with funding something like gdax or a wallet (which is basically a liquidity well.)

Purchase tokens or bootleg..if latter, if we assume we want to allow the user to put in credit card, could we run something like standard payments gateway that the company handles for the user and funds gdax accounts? (hmmmm...must be a way to do this without turning the bootleg company into a money transmission system, which would be problematic from a regulation and business cost perspective)

### Reference

- [Reference](links)
- [To issues](or-any-inspiration)
- [That might be](helpful)

### Questions

- List any questions?
- That you are unsure of the answer?

### Assumptions

- List any assumptions that
- You are making in terms of timeframe,
- Output, or general context setting

### Acceptance

- List of what needs to be true
- to consider this done
- done done

## Tasks

- [ ] A list of tasks that need
- [ ] to be done to call this issue done

The issue names OAuth/login, Google authentication, MetaMask, uPort, wallets, credit-card payments, GDAX funding, and regulatory concerns, but no files, tests, or entry points. Start by defining the scope and acceptance criteria for these unresolved questions; done requires a concrete, implementable plan rather than the current placeholder tasks.

Written by the indexing model from the issue text.