The button icons are a few px off - very unsettling.
Which ones? Perhaps this is a browser issue.
The next version of DuckDuckGo
151–160 of 331 posts
Re: The next version of DuckDuckGo
#152All my social media profiles, all my websites, every project I contributed to, even websites where people credited me for my work when they used it in their own projects, all neatly sorted and with great context information. Definitely on par, if not better, than Google and visually much easier to digest. Amazing job!
Re: The next version of DuckDuckGo
#153As mentioned in another comment, the contrast is really bad, I find it hard to read and focus on a given result. This is much worse when using f.lux.
I also disliked the left-align on everything, I rather have it centered as it currently is. When using big widescreen monitors there is a lot of whitespace in the middle of the screen and the results show up all the way to the lower left corner... It is pretty uncomfortable to look all the way there and this makes it harder on the contrast part too because there is so much bright light already coming from the background and the font color is a light greyish. This is specially worse in multi-monitor setups.
The image and video search tabs are great, and I really like the fact they replace zero-click results when you click on them, but I wouldn't leave them in the fixed header, there is just no need for them to be there. This would reduce the size of the fixed header and make it even better.
When scrolling results using j and k, the greyish background it adds to each result makes the contrast even worse. I remember when they were yellowish, they were better back then, imo. But current design works too. I also miss the current border around it, it makes it much easier for you to find yourself if you are switching tabs and going back to the results page. I haven't measured, but the font also seems a couple pixels smaller, is it?
It is also harder to distinguish between results. It all seems like a blob of text, hard to skim through results looking just at the title. In the current design this is fantastically easy, given titles are blue. I only read stuff below the title if the title is of interest. In the new design this is much harder to do, there is not enough contrast between the title and the text under it. Keep it blue, there is absolutely no reason to change this.
Re: The next version of DuckDuckGo
#154Re: The next version of DuckDuckGo
#155Earlier quoted context omitted.
Thanks for the feedback! Our current version also has a fixed header, and that can be turned off in the settings, which we plan to make work in this next version as well. Noted on contrast. We will look into it more -- that's exactly the kind of feedback we were hoping to get.
I'm in the camp that actually likes the new look. It conveys a modern minimalist view while the extras just get out of your way. I've been mostly against flat design for a number of reasons but IMO, you've achieved a great design. I really like the minimalism of the hamburger button. Again, everything just gets out of your way. Perhaps enlarging the font-size of the search result snippets might help with the contrast…
Re: The next version of DuckDuckGo
#156I use DuckDuckGo as my primary search engine and have had a positive experience using it. This redesign incorporates two of the worst design trends today: very low contrast text and gratuitously, obnoxiously large fixed headers. I dislike fixed headers on any non-phone/tablet UI because almost all laptop and desktop screens are widescreen. Fixed position elements on the sides of the screen make much more sense, altho…
A practical application for fixed headers is retaining access to search fields on pages with infinite scrolling (which is why they're doing it here). Otherwise, you might be ten pages deep and then have to scroll all the back up to search again. With this, search is accessible at all times.
Though Steve, who thought he was God, took it away from some of You.
Re: The next version of DuckDuckGo
#157Earlier quoted context omitted.
r.duckduckgo.com is actually there for privacy, to remove HTTP referers. See: https://duck.co/help/results/rduckduckgocom
If you search using POST, that isn't a problem. Also, referer headers aren't sent to unencrypted links so if https://duckduckgo.com sent me to http://example.com they would not see where I came from. Those two combined offer better privacy as no website can know what you were searching for and only secure websites know you came from DuckDuckGo. This setup doesn't give DuckDuckGo a chance to track what I'm clicking on…
But if you still don't want your clicks going through the r.duckduckgo.com domain, you can turn it off in the settings.
Presumably you also disable Javascript by default, right?
Re: The next version of DuckDuckGo
#158Based in US, the line "The search engine that doesn't track you" means nothing.
Re: The next version of DuckDuckGo
#159Search: åäö "Showing 35 åäö Images" Great.
Re: The next version of DuckDuckGo
#160I use DuckDuckGo as my primary search engine and have had a positive experience using it. This redesign incorporates two of the worst design trends today: very low contrast text and gratuitously, obnoxiously large fixed headers. I dislike fixed headers on any non-phone/tablet UI because almost all laptop and desktop screens are widescreen. Fixed position elements on the sides of the screen make much more sense, altho…
Thanks for the feedback! Our current version also has a fixed header, and that can be turned off in the settings, which we plan to make work in this next version as well. Noted on contrast. We will look into it more -- that's exactly the kind of feedback we were hoping to get.