I know it's not much at the moment, but I would be willing to donate 5000 to 10000 Aeon to whoever would make such a thing... assuming it passed the muster of the Aeon community.
Yeah I can throw in a few
æ into the mix.
A bootstrapped template for a website just isn't going to cut it - it needs to be properly designed from scratch (imho).
I'll work on some PSD mockups of a few site designs and post them here later in the week. Perhaps with some PSD designs on display we as a community can analyse and introspect accordingly (as we did with the logos).... and then once we've gotten to an area we like... then it should be a fairly simple process for a web coder to take the PSDs and construct accordingly.
This way we can guarantee that everyone has a say in how the site
looks and the various elements that should be included. Plus... working from PSD mockups ensures that we start by considering the user experience
first and thus work backwards to the technology.... just as I have been doing recently with some mockups for an Aeon mobile wallet:-
I like the designs here. When designing are you trying to make them as symbolic as possible, making it easier to use by mitigating language barriers and having the added benefit of decreasing translation costs?
Translation / language universality is a great point.
At the moment the designs are mainly just sketches as a way of thinking about the UI process while testing out different color schemes, typography etc.
For the purposes of universality the UI experience should (imo) be as simple and intuitive as possible.
One example is ditching the use of the terms
Locked Balance and
Unlocked Balance, which is just
unnecessarily confusing (particularly to bitcoin immigrants).
If it brings 0 benefit and +1 confusion (and can be changed easily) then alternatives should be used. Reverting to
Confirmed Balance and
Unconfirmed Balance has unity with bitcoin nomenclature. (Although an even better method might be to just use
Available Balance and simply re-formulate unconfirmed balances as incoming transactions - which is effectively whats used in the fiat system today).
Another thing I was looking at was how best to present and interact with a 95-character long Aeon Address on a small mobile phone screen in a way that is both practical, visible, and stylistically appealing. If there's one really irritating thing about cryptocurrency addresses, its typing (or even pasting) them into tiny single-line entry fields, which invariably involves part of the address being concealed at one end or another - you never really know which is the start and which is the end -and a careless keypress or pasting mistake can lead to an erroneous entry.
One way around this (as seen above) is splitting the entry field into 5 rows of 19 characters so that the incoming address is automatically truncated (and centrally justified)... making it entirely visible, practical to manipulate and pleasing to the eye.