Where the design community meets.
Designer at flypay Joined about 4 years ago
Yeah I miss the downvote button as I've never seen a worthwhile post from Jamal.
Especially here as he is conflating working for a brand that has personal values to yourself against one that doesn't. I.E. Lot's more people feel aligned with Nike and the like, therefore want to work there.
He's also conflating consumer services vs enterprise, but it's more clickbaity to mention "cool/boring" companies as the issue.
How is it collaborative?
I can't tell from their website. Do they have tools to assist in collaborating with others, further than say a Rebound on Dribbble?
How about making up/downvote weighted based on the user voting.
E.G. more karma = higher weight on a vote. So if a post has 10 ups and 10 downs, but the 10 ups were from high karma users, and the downs were from new accounts, the post would show 0, but rate higher in the backend.
E.G.2 Downvotes are weighted 0 (or close to it) until the user has more karma.
E.G. A user (bot) that just downvotes without upvoting, or has an overly negative proportion gets weighted down.
Just some ideas, as I don't believe every vote should be counted equally. Youtube have recently been talking about how their trending page works and they give each video a "temperature" that scores the video on the speed that it's gaining engagement and then ranks the videos on that. Therefore the highest viewed video isn't the highest rated, but the one gaining traction quickest.
P.S. Please can you fix the comment box! It's like less than 3 lines tall and not expandable (at least for me).
Why does your logo type bounce on hover instead of the ball on the paddle!?!?
Are you a bot?
50-50 doesn't just mean that they are both good.
For example if I want to A/B test a design with signup pre and post an action, my hypothesis might be that a pre signup screen will reduce conversions. If my results are 50-50 that shows that there is no significant drop off by forcing a user to share their details. And therefor that should be the pushed out design, as it collects more data and doesn't have any more dropoff whilst doing so.
So it depends on what your hypothesis behind the A/B test was.
The comment you replied to has no mention of "bottom navigation". And with that I'm not "always" recommending it as the only option.
I'm concurring with Perttu and the notion that we as an industry are moving away from it as a primary form of navigation. And that any "up front navigation" (be it bottom nav or what ever) is a better alternative, then say obscuring primary features of an app behind mystery navigation.
p.s. please don't discard a bottom nav as an option because you have more than 5 items. Restructure your main nav until all/most primary actions are simply discoverable, then relinquish any lesser nav items to overflows.
I agree we are moving away also. But in regards to it being a primary navigation method. You can see this with Googles eventual adoption of bottom tabs. And with more interfaces switching from Hamburgers to upfront visual navigation.
Except for Amazon, who though a hamburger and a back button belong in the same space!?!?
People are more familiar with the icon yes. But it's use is still lesser than having up front navigation. Due to the hamburger hiding its contents.
Up front navigation within apps should always be recommended: https://www.nngroup.com/articles/hamburger-menus/
Using both is also a good option, and usually Google uses a mix of upfront navigation for the core parts of an app. And hiding sub content within the hamburger (settings, share, account switch, login/out).
Abstract has "collections" which is a way of spacing out your screens into groups.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.