Since using the AlephZero client I began thinking about how the client could look down the line, and once I had that itch I had to scratch it.
http://cl.ly/image/1v2G102r0T3S/oOf course this is a very rough sketch and shows only the contracts tab. I imagined it as a collection of all your active contracts, but added a few features that are not on the current code but seem no-brainer, specifically features in which a contract tells the client the kind of data it accepts (and what UI) and the current status of the client.
I'm also adding the ability of querying a third party of your choosing to audit and describe each contract, so you can trust it before.
Most features of the current AlephZero are visible on that screen. The "owned accounts" would be similar to the contracts page and the remaining status and blockchain could be tucked in the "network" screen.
I'm using Retro gravatars to identify contracts because they're much more instantly recognizable than hashes, and I believe they are much better than the traditional "kaleidoscope" gravatars. I didn't pick or choose any, but you can still read an image in all of those random patterns.
So what does the community think? Is that kind of contribution welcome? How can I help in a more productive way?
Thanks
Comments
I can see how tricky the contracts will be to visualized into a GUI. Specially with the underlining info.
@texture? what are your thoughts...
In fact, we will be providing GUI tools for dapps developer, meaning that contracts will have their own, decentralized GUI unique to each. Personally when I think of the reference clients, I imagine them very much like the itunes store, with (d)applications going full screen when started.
Fun times ahead!
So a single app could have multiple clients, using any kind of technology: HTML in browser, a mobile app, a watch.
I see ethereum as bigger than the cloud (the ether) where data is stored and commands are executed, but multiple clients can be built on top of it.
Instead of trying to be java app, a single ugly interface that Should be universal but may not work in a future system, I see it as the Twitter API, one single service, multiple clients.
The main client, in this scenario, would be merely a central place to access, control and view the multiple apps.
Maybe the right metaphor would be a file system, were you keep data and an open apps..