Redesign Brief's interface about brief

[ancestorak]

Pushed the new design but leaving this issue open for discussion about it.

[nohamelin]

Two visual issues; I assume that they are Linux-specific:

• The arrow...
• Double drop-marker for Options. Here I think that the native icon should be kept.

[ancestorak]

Thanks for the report.

The native icon cannot be used, by the way, because even though this one fits, it can look completely different and out of place on another system. When it comes to native styling, it's all or nothing.

[pwd-github]

The new interface makes it harder to use brief. It's now two clicks to get to the homepage of any feed and the images don't fit the rest of the UI. IMO Brief should've aspired to look more like the Add On Manager. That's the direction the in-Content Preferences are going in and Brief should look more native.

[ancestorak]

Well, it's design decision and it ultimately comes down to taste. Most of the feedback about the new design has been very positive. All I can do is address more specific usability issues.

It's now two clicks to get to the homepage of any feed

Do you open the homepage often? If so, why?

and the images don't fit the rest of the UI

Do you mean images in feeds themselves?

[pwd-github]

I go to the homepage on a daily basis on a few of my feeds. They often notify of the release of something, but to get the specific thing I want to view, I'm required to go the homepage and follow a link from there.

The images in the header mark all items read, view headlines/full feeds, etc. They're not as clean as the rest of the design.

On Monday, 18 November 2013, 20:41, Adam Kowalczyk [email protected] wrote:

Well, it's design decision and it ultimately comes down to taste. Most of the feedback about the new design has been very positive. All I can do is address more specific usability issues.
It's now two clicks to get to the homepage of any feed
Do you open the homepage often? If so, why?
and the images don't fit the rest of the UI
Do you mean images in feeds themselves?
—
Reply to this email directly or view it on GitHub.