Cookbooks UI Wireframes Review about supermarket HOT 11 CLOSED

Before we start talking about mobile versions, does anyone have numbers of how many people actually use the community site on a small screen device? Not sure if that's a good use of time or added complexity.

from supermarket.

Overall it seems like the goal was to preserve the interaction patterns and UX of the current site. I think this is not in the best interest of the community and doesn't address the actual needs of having a package repository.

from supermarket.

I have occasionally used the current community site from phone on the couch, mostly to look at changelogs of subscribed cookbooks. Haven't had any sever usability issues with that.

I really like the proposed mobile UI, its very readable and the platform icons really pop out.

The only comment, in general, I don't think the light grey font has enough contrast with the white background for good readability, especially when the font is smaller. The large total numbers at the top have good contrast against the white/grey theme, but given their size there shouldn't be a problem reading them.

from supermarket.

@atomic-penguin bear in mind, these are wireframes, and as such, colors & graphics are likely not representative of the final, designed output.

from supermarket.

@coderanger I'm interested to know what you see as the "actual needs of having a package repository" That might be a discussion best moved to the Supermarket Google Group.

Even the current site does a good job of playing the role of a package repository. You develop your cookbooks on github, or wherever you like, decide it's time to release a version, and publish that version to the community site. As a consumer of the packages, you have versions that you can track, check for updates, etc.

What am I missing?

from supermarket.

@coderanger last time i checked, [Correction: about 3% - Explanation of correction below - gabeweaver] of views were from mobile devices. While the primary use cases will be facilitated on the desktop, it's still nice to be able to find and digest certain pieces of information on a mobile or tablet device. It actually doesn't add that much complexity and is a good practice for helping us build a better user experience regardless of device.

from supermarket.

Maybe this is an inversion of @coderanger's comment, but it is difficult to give good feedback without understanding the scope of the effort - I imagine the major constraint is the currently available data, and that there won't be any radical changes at this stage. (I'm fine with that, but I hope I'm assuming correctly).

Two data changes I noticed, an addition and a deletion. The addition of "View Issues" is great, and something I miss from CPAN - if a maintainer has recorded the URL to their issue tracker, that's a good sign. Being able to quickly find it and see whether issues are logged (and responded to) is useful when deciding whether a cookbook is healthy and worth using.

On the other hand, the cookbook rating appears to have disappeared entirely. I'd concede that it's not particularly useful at the moment - the number of people rating cookbooks is very low, and 5 star ratings are problematic anyway (thumbs up/down might be better). Still, I'd rather see an effort to make ratings more useful than to abandon them entirely.

from supermarket.

@zts thanks for the feedback. Yes, we've removed cookbook ratings for now because the existing implementation isn't useful. We intentionally made the decision until we could build a rating system that was useful. Here is the milestone roadmap for Supermarket. The 5th milestone is focused solely on solving for this in a meaningful way by deriving various data points from the cookbook to determine overall health and value.

Let us know if you have any other suggestions before we get there!

from supermarket.

@gabeweaver - re: ratings, makes perfect sense and seems like the right decision. Looking forward to it!

from supermarket.

@gabeweaver Touché, I stand corrected on mobile numbers :-)

from supermarket.

@coderanger not so fast. My trusty and very smart teammate @brettchalupa pointed out inconsistencies in the data I posted about mobile devices. The last time I thought about the numbers - nearly 3 months ago - I did so from an inaccurate data set. In the name of transparency, here is the correct data using February of 2013 and 2014 to better understand trends instead of absolutes:

Desktop

• Feb. 2013 - 97.87%
• Feb. 2014 - 97.55%

Mobile

• Feb. 2013 - 1.07%
• Feb. 2014 - .86%

Tablet

• Feb. 2013 - 1.05%
• Feb. 2014 - 1.59%

So you are correct that the existing numbers are very low, but I still stand by my comment that adding some basic responsiveness to the UI is not that complex given the framework we are using. Based on the nomenclature outlined in this article, I would say we are going for the responsive treatment where we are designing primarily for desktop, but providing an adequate mobile/tablet experience beyond making people pinch and zoom :) The UI Wireframes are intended to be an exercise to make sure we thought through the ramifications of making the desktop UI responsive.

With that said, I stand corrected and I apologize for the incorrect information originally. I hope this helps us have better conversations and more disciplined prioritization of effort.

from supermarket.