Most mobile payment solutions today operate on top of Tokens, with MasterCard, Visa, and Amex serving as Token Service Providers. Tokens appear similarly to current credit card numbers (not distinguishable in some cases). Each token is a unique number used for a payment, which the TSP then links to the card on file / credit card number. Merchants only ever have access to the Token.
Android Pay, that succeeded Google Wallet, uses such tokens.
Schematics makes it easy to specify an API interface. It will let you bind / coerce json to your types, and then validate that the provided json bound exactly (no extra fields, no missing required fields, custom validators). We also extended it to provide a polymorphic type that will bind to a class based on a discriminator value in the json (based on an old gist from one of the schematics contributors). The roles definition also allows you to provide different serialized views of a model (though whether the model should be aware of that concern is questionable, but a nice shortcut).
We use schematics to back the data on our domain models. It provides models that are separate from persistence models that live in the data / client layer (database or external service bound), and gives you a few nice things for free (like validation) and you can attach behavior to them.
The only things I would like to see added are:
- A native polymorphic type (we're going to try and submit a pull request with our implementation within the next month)
- Roles (lists of fields that are output) optionally separated from the models.
- Support for redefining a model (currently it is difficult to add a self referencing field and have schematics pick it up for you, or add fields through mixins).
Amazing game, loved the stack on level 21. Made it to level 26, will have to come back and play more later. Go sell it on an app store and make some money for your time.
AspectJ would probably be the most widely broken dependency, even with UseSplitVerifier enabled. Version 1.7 of AspectJ fixes the issue, but most corporate IT consumers aren't in a position to update it themselves.
It's already pretty close to being there; you only need to install a plugin now in order to get first class support in the IDE [0]. A few days ago, you would have had to install the VS2012 Update 2 CTP (hard to justify in a corporate environment in case bugs slow development), but now that it has gone RTM, there isn't much a barrier to entry besides awareness that the plugin exists.
I'm really surprised that integration with external credit cards (and banks, but especially credit cards given their importance in the US) isn't on the top of their priority list. I understand that they'll miss out on the extra data they get by being partnered with their bank, but it would let me drop mint.com with its dated ui, and make it much easier to use the goals mechanism (and daily spending limits would be a lot more relevant). Alternatively they could just launch a Simple credit card, give me 1% cash back / rewards and I'd feel comfortable moving most of my spending onto their card, which would let me continue to maintain my credit score and extract a bit of that merchant fee.
There's a mouthwash that aims to do the same thing, and is conducting clinical trials in the US.
The link I found says that they were starting in March, but I can't seem to find anything about the results or if they actually started the expanded trials.
They have a 256 gb ssd / i7 model for $1800, and a 128gb / i5 for a cheap $1300 (both are on Amazon, look for model number np900x4c). We played with one in a Best Buy before purchasing online, it definitely felt pretty comparable to the mba's I've used.
Android Pay, that succeeded Google Wallet, uses such tokens.