In mock below, note there is no horizontal divider below "January 22".
Note: horizontal dividers *remain* above nearby cells.
Mhurd | |
Feb 1 2016, 10:58 PM |
F3287068: nearby.png | |
Feb 1 2016, 11:14 PM |
F3287070: featured.png | |
Feb 1 2016, 10:58 PM |
In mock below, note there is no horizontal divider below "January 22".
Note: horizontal dividers *remain* above nearby cells.
@JMinor this is very important. Let's not execute a visual design half way. IMO this is high priority for headers. The visual design change is sort of based on this. I would even want to revert to old headers without this.
The nearby is an (only) exception to this because of the layout of nearby cells, we will fix that inconsistency in 5.1
@JMinor - I don't believe @Nirzar's mock implies there are horizontal lines for some but not others, although at first glance it may appear so. Take another peek at the second screenshot. Those horizontal lines are above each *nearby* cell, not below the header. In this one case it just appears that the line in the nearby screenshot is part of the header, but it's actually part of the top nearby cell.
Yeah, no problem, just wanted to be sure the nearby being different wasn't just an oversight.
@Nirzar @JMinor I don't think if we should remove lines for everything but for nearby - this looks weird.
Let's not execute a visual design half way.
I wholeheartedly agree with this - to me this means NOT changing the design of every section EXCEPT nearby and then updating nearby in 5.1. Lets be self-consistent. If we want to remove
the lines, lets execute it in one go.
Also I think we should discus MVP and design freeze - this looks nice - but we really need to put finalize the scope of design changes for 5.0 - I want to app to look good for launch but I also want to launch.
Did we solve the issue of having an inconsistent line on nearby but not on any other headers?