Topic: The official Bitcoin client looks awful (Read 4326 times)

Ok I should not have mentioned concrete examples. Discussing them is besides the point. Let me add to the ctrl-c reply of your that I know that it is possible. I just wish you could it in the window that opens when you double-click a transaction line. You can select the text but do nothing with it.

Again: Discussing them is besides the point. There is a lot do do. Don't make us take your medicine, Dr. Trax. I do not wish to glow in the dark.

Here's a reasonable feature request: when you go to send coins, if the amount is *large*, then perhaps a warning should pop up before the actual coins are sent asking you to verify that you did not make a typo?

Presumably, what is considered a large amount will vary over time and from individual to individual, so this amount could be adjustable.

No. There's a big difference between stupid skinned themes designed by programmers and a clean fluid looking interface that looks contemporary and is designed by a designer.

Everyone, please don't take my original advice. From the replies here, it's obvious it would be confused with some programmer's idea of what a cool skinned theme would look like, which is just wrong. Stick to what you're doing. Maybe someday, you can hire a designer and make it look really good.

You can do that! There is button "Copy to Clipboard". You probably missed it because the button is yet not skinnable... Sorry, can't resist being sarcastic.

Cloud based backup is bad idea. Backing up wallet on so called "cloud" gives 2 concerns. First the cloud can be destroyed by adversary or accident more easily than offline backups in your phisical possesion. Second, even if the backup crypto is not broken, the theft of wallet is more easily done becouse all you need is login information than wallet.dat file itself. Login information is a little bit easier to retrieve from remote systems using keyloggers than file.

things to put in a context menu: copy recieved address, copy sent address, copy full log, an item to open another window with the transaction log, hide, and pin.

as for the tool bar, a toolbar is fine, but sitting empty like that is pointless waste of space. Stick your bitcoin balance on that as well instead of on its own line... displaying the bitcoin address the way it does doesnt really do anything either by the way, no one cares what the string contains, just so long as it connects to them. More useful would be a tool to choose an address to copy (of your previous addresses) or choosing one of the new ones.

I would really like the information that is acquired through blockexplorer to be accessable, not all of it, just the relevant information to your own transactions.

For example you need to be able to do ctrl-c on a bitcoin address or have provider-pluggable cloud-based backup built in. There are a million things still to do.

What should you need to change in Bitcoin client??? You need to bloat the GUI with skinnable themes to attract additional bunch of retarded users who judge software purely from so called "eye candy"? (search youtube for "happy tree friends eye candy") (lol)

You must get rid of the block count in statusbar that most users even did not notice?

The Bitcoin is example of simplicity and functionality. I have said my word.

The question is: Are the bitcoin devs aware that the app sucks big time and know how to improve it? I believe they are. If they are, they don't need our input.

To me it looks like the UI can get most needed features in a fulltime-week effort. It is pretty good already but it need 10-20 additional little tweaks, features and tools to be perfect for noobs as well as for nerds at the same time.

@antares, now I may be drunk and this may be offensive, but you're talking bollocks. I don't want to have to search the web to know how to use a piece of software, it should just work. If the user interface of some software requires searching the web before you can use it, then it quite simply fails at its job of interfacing with the user!

If the key audience is a technical elite like you are suggesting, then there should be compile instructions rather than binaries on the main website. I'd be quite happy with that, but that's not the case.

I know what HTML is, I was just struggling to think of a GUI toolkit that designers find easy to use, that is cross platform, user-friendly, mature and suited to rapid development. HTML ticks all of those boxes, in fact Windows 8 will use HTML and JavaScript for client-side apps.

The Win32 API and Cocoa are reasonably lightweight, but not cross-platform. GTK, .Net, QT and Java have enormous dependencies and are a ball-ache to just jump in and start developing for. WebKit is tiny but has loads of Apple's dependencies, Mozilla have a very ugly build process.

CEGUI and Irrlicht are nice and small, but not very flexible. A small, lightweight, cross-platform HTML4 rendering library with minimal dependencies (zlib, opengl and libpng) would solve a lot of problems in this space. For example we wouldn't need a 10MB download for the Bitcoin client, and the same code could be used across mobile devices with constrained memory.

@bitplane - I consider people should at least get some knowledge before using bitcoins - it's usually those people thar are even too dumb to google up those said 3 items that get their wallets stolen and then spread the word about some unsafe service, just because they are too dumb and ignorant to admit that it's their own fault. As I said I can feel for some of your suggestions from the first post, however it shouldn't be too easy. I mean, look at the recent mtgox incident - there were people using unsafe passwords. Those were the one who cried out loud. It's not like we've 1995 here, where password security was something "unheard of before" in the internet community. Therefore I consider at least some basic barrier to keep away those who are even too unwilling to read a couple pages before using something. That again implies that a fluffy colourful iPhone-bitcoin is in fact the wrong step - it attracts those dumb people like light attracts flies.

For Definition: A dumb person is (IMHO) someone who does not know something AND is not willing to get at least basic knowledge by researching the missing information, while complaining when that same persons fails because they did not research at least basic information.

Further, being a noob is not something bad(imho). We all started as noobs, but many of us have evolved and learned about the possibilites, risks and precautions using bitcoin

This is technological elitism and a very short-sighted, ignorant view of the world. Either we have a GUI client or we don't, if you don't want a user-friendly UI then stick to the command line.

No. HTML is a document mark-up language based on SGML. IMO converting web-browsers into Operating Systems is not progress. HTML and Cascading style sheets were never intended exclusively for gui rendering. My favorite web-browser (lynx) is text-based, but has been stuck at about HTML 3.2 because it does not implement the Document Object Model (also used for stylesheets.) That browser uses external viewers for displaying things like images and video. This is a lot more convenient and secure than running a proprietary video player from the website you are visiting (every website using flash and silvelight video).

One other point: Client-side scripting takes control from the user. Before I can trust the EMCA Script in a web-page not to send my information to parts unknown, I have to review the source-code. Not user-friendly at all; as I have to check every time I load the page.

Hell beware - imo the client is just right - I can approve to some of the OPs suggestions, but it should still be rather functional than "look like some stupid iphone app". People use the client to do transactions, not to waste their time.

The official Bitcoin client looks just like it should look.

If for some noob it's too technical (the 3 items on the statusbar, connections, blocks, transaction count), then he must reconsider using Bitcoin and computers in general and return to using showel and axe.

Slightly off-topic, but are there any HTML rendering toolkits that are incredibly lightweight, cross platform and with minimal dependencies? Given all the progress made in the web over the past decade, it may be better to just go ahead and write apps in HTML as they're very flexible and well known by users. A desktop app that looks and feels web 2.0 would be rather nice IMO.

I don't really care beyond this, this level of nativeness is good enough for me.

Look harder. Its drawing its own emulated versions of the controls. It is re-implementing the behavior and it is emulating the look of each control by drawing its own stuff into *generic empty* windows. It is using some native graphics and theming API to draw its own things that look like the original native controls.

This has been implemented, you get a notification when a transaction comes in, with all that info.
A right-click context menu on the transaction list? What kind of options would you expect there?
A toolbar is pretty standard in any application these days.
Filtering has been implemented, by default it still shows all transactions in the list, but it is possible to only display the transactions of today, this week, this month etc.

Yeah I agree, but not because they're toy-ish but because they deviate from the standards that users expect. The example you gave is bad because of the background, wasted space, layout, tabs and buttons not looking like what users expect and the general clutter of it. Good design is not achieved when there is nothing left to add, but when there is nothing left to remove.

To paraphrase Donald Norman, as little knowledge of how to use the object as possible should be held in the head, it should exist in the "world" (in this case the UI). A good UI design is split into categories to reduce clutter thus preventing the need to memorize actions and locations (knowledge in the head), each item should use metaphor (icons to represent real-world items, pushables "sticking out", draggables that look like they can be grabbed) and logical mappings (sorting a list is done via its column header, use of colours to signify categories) to draw on knowledge that people already have and make things obvious. When there's no other option, use standards; *most* people know how to operate a drop-down list or combo-box because they've used loads of them before.

The problem with programmers or engineers being designers is that we believe we are normal users when we're not! I may have read Norman's design book and Spolsky's UI book, but I still suck at making user-friendly designs because as soon as I start hacking I my innocence is soiled by the technical knowledge I acquire. This is the greatest challenge of UI design and why most apps look like crap.