| I have long thought that a doc centric view could unite apps and web much better. Obviously docs we use every day are doc centric. Although the holy grail of easily embedding and linking docs has not been achieved. Games and other "session" type interaction should simply be docs. You create a new game session, you could have several. You pick up each session by opening it. You can back up sessions yourself if the app doesn't let you, or you just prefer to do so. You are in "control" of you own data, i.e. game state. (Identity management can allow transferred/leg-up games to be easily differentiated from true one person game accomplishment.) Accounts are just docs. A doc shared by two owners with data and state that gets appended as it is used. Much easier to have two accounts with your financial exchange or bank, or anyone else if you like, without special custom support for that kind of thing. Apps, web or native, take a back seat. They can be auto dowloaded as needed. App folders become just caches as docs know what apps or app classes they need. Most doc creation is simply a duplication of a template with no parameters, or perhaps a simple configuration of creator/viewer/owner/capability parameters. (i.e. an energy utility account.) Because everything is a doc, users can organize them, back them up, etc. Own their own data. A lot more thought could go into this. But there is no reason why the code behind different doc types would matter much - native, web, etc. once the limitations of those platforms for this simpler model were ironed out. Why should the user ever have to care or be aware of platform choices? |
Basically, a notepad that grandma and tech intelligencia can interop on is unbelievably powerful.