BitShares Forum
Main => General Discussion => Topic started by: bodenliu on May 28, 2014, 07:15:10 am
-
any update? screenshot of the interface?
-
Very importand to make a debut with an superb ui that is better than from competitors (like nxt) !!!
I am also very interested about progress here!
Please take EXTRA care on that!
The ui will steal attention from users they have no technical knowledge and they are the most of us!
If the gui is worst than NXTs (as an example) many would interpret that bitshares as a concept is also worst even if it is better. (only dev/programmers etc. would not fall in the trap)
-
Very importand to make a debut with an superb ui that is better than from competitors (like nxt) !!!
I am also very interested about progress here!
Please take EXTRA care on that!
The ui will steal attention from users they have no technical knowledge and they are the most of us!
If the gui is worst than NXTs (as an example) many would interpret that bitshares as a concept is also worst even if it is better. (only dev/programmers etc. would not fall in the trap)
totally agree. people are so easily turned off from bad designed guis. its critical to offer a clean, stylish interface right from the get go
-
+5% absolutely agreed
we should also consider how the first nxt wallets have looked before the new UI design was published .. just said
Its a progress but agreed with you that it's one of the most important task to attract less techniqual users :)
-
UI's being developed for all platforms? Just seeing XC heading into the Top 10 - ? based on it mobile payments option / rapid block generation. Any progress on Android apps?
-
UI's being developed for all platforms? Just seeing XC heading into the Top 10 - ? based on it mobile payments option / rapid block generation. Any progress on Android apps?
first of all we need a working bitshares_toolkit .. guess all other stuff will added over time then
Pls correct me if i'm wrong with this...
-
UI's being developed for all platforms? Just seeing XC heading into the Top 10 - ? based on it mobile payments option / rapid block generation. Any progress on Android apps?
first of all we need a working bitshares_toolkit .. guess all other stuff will added over time then
Pls correct me if i'm wrong with this...
Correct, bitshares_toolkit it's most important thing, but we should launch BitShares XT with very limited but attractive and easy to use GUI.
-
UI's being developed for all platforms? Just seeing XC heading into the Top 10 - ? based on it mobile payments option / rapid block generation. Any progress on Android apps?
first of all we need a working bitshares_toolkit .. guess all other stuff will added over time then
Pls correct me if i'm wrong with this...
Correct, bitshares_toolkit it's most important thing, but we should launch BitShares XT with very limited but attractive and easy to use GUI.
agreed!
-
It is coming along very nicely...
-
It is coming along very nicely...
yup :)
-
It is coming along very nicely...
Can this be expanded upon with maybe just a few more details?
-
this?
(https://dl.dropboxusercontent.com/u/15663627/bts.jpg)
-
Holy crap .. luck much better than i anticipated
-
We have figured out how to simplify the wallet down dramatically now that we have *named accounts*.
Users will never have to see an address again unless they want to use 'advanced' mode.
-
We have figured out how to simplify the wallet down dramatically now that we have *named accounts*.
Users will never have to see an address again unless they want to use 'advanced' mode.
That's seriously great. I think forcing users to work with long addresses is a huge barrier to adoption and eliminating that seems like a massive step forward as Bitcoin itself hasn't gotten there yet for the most part. Looking forward to seeing how the naming system will work out in practice.
-
With names being used are there going to be any character limitations like symbols and punctuations?
-
With names being used are there going to be any character limitations like symbols and punctuations?
They will be restricted to valid domain names.
-
ASCII alphanumeric (convert to lowercase) and hyphens, but can't start or end with hyphen.
-
name is good.
but I am worry about one thing.
You must be very carefully, don't write a wrong alpha, or you maybe send money to a wrong guy.
For bank service, you must write both the account and the name correct.
-
name is good.
but I am worry about one thing.
You must be very carefully, don't write a wrong alpha, or you maybe send money to a wrong guy.
For bank service, you must write both the account and the name correct.
agreed that, more detail about the name system?
-
The GUI will have an autocomplete, if there are multiple names with close spelling then you will see them all as you type and this will help you be sure you are picking the right one. You can also locally label names with your own alias if you are very concerned.
-
Sometimes it is still hard to distinguish 1, l, |, I etc. Is it possible to have the format like
JOHN-DEAN-3J4S
or
FLOWERS-563KT
Checksum will help a lot.
-
Sometimes it is still hard to distinguish 1, l, |, I etc. Is it possible to have the format like
JOHN-DEAN-3J4S
or
FLOWERS-563KT
Checksum will help a lot.
+5% for checksum
checkout recent NXT development .. they are now using Reed-Solomon encoded addresses ... this allowes to *correct* errors!!
-
Sometimes it is still hard to distinguish 1, l, |, I etc. Is it possible to have the format like
JOHN-DEAN-3J4S
or
FLOWERS-563KT
Checksum will help a lot.
+5% for checksum
checkout recent NXT development .. they are now using Reed-Solomon encoded addresses ... this allowes to *correct* errors!!
Considering the name looks up the key it could simply be: ${name}-${KEY[0...4]}
-
Considering the name looks up the key it could simply be: ${name}-${KEY[0...4]}
yup .. nice idea
-
Sometimes it is still hard to distinguish 1, l, |, I etc. Is it possible to have the format like
JOHN-DEAN-3J4S
or
FLOWERS-563KT
Checksum will help a lot.
+5% for checksum
checkout recent NXT development .. they are now using Reed-Solomon encoded addresses ... this allowes to *correct* errors!!
Considering the name looks up the key it could simply be: ${name}-${KEY[0...4]}
+5%