Skip to content
This repository has been archived by the owner on Jul 5, 2024. It is now read-only.

Please do not ever remove the "Classic" view #687

Open
esutton opened this issue Dec 8, 2017 · 4 comments
Open

Please do not ever remove the "Classic" view #687

esutton opened this issue Dec 8, 2017 · 4 comments

Comments

@esutton
Copy link

esutton commented Dec 8, 2017

The "Classic" view is much more efficient in my opinion.

I tried but cannot get used to the new UI.

Thanks for the best ( "Classic" view ) package search engine available!

@dmfrancisco
Copy link
Member

I'm afraid I'll eventually have to remove the classic view, as the system that powers it costs me $70/mo 😬 The new version is a lot cheaper, since the front-end is statically served by GitHub.

But I'm open to feedback on how to improve the new version. What specific changes you don't like? Is it the bigger typography, not having the two scrollbars (one for the list and the other for the readme), something else, all of the above? 😄

@esutton
Copy link
Author

esutton commented Dec 8, 2017

@dmfrancisco Bummer.

Classic seemed more efficient for browsing for packages. The last selected package stayed fixed on the right and I could scroll to this next package to select on the left.

  • I think I liked the options staying fixed at the right when scrolling
  • I did like the two scroll bars.
  • New version was not obvious, once I selected a package, how to get back to the gray-ed out list. I did not realize all I had to do was click on it.

Or maybe I just do not like change. :-)

I will go back to using the new version and try to give better feedback.

@dmfrancisco
Copy link
Member

dmfrancisco commented Dec 8, 2017

Interesting 👍 That makes sense, thank you for your feedback!

Regarding the issue of having to click the black overlay to go back, we can add a close button to make it more obvious, like Product Hunt does for example, and also support pressing ESC:

producthunt

@dmfrancisco
Copy link
Member

Leaving this here, #1006, which may be useful for guiding the design changes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants