Skip to content
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.

The History Application is supremely broken for a Mobile Layout. #358

Open
vshivam opened this issue Feb 26, 2016 · 13 comments
Open

The History Application is supremely broken for a Mobile Layout. #358

vshivam opened this issue Feb 26, 2016 · 13 comments

Comments

@vshivam
Copy link
Member

vshivam commented Feb 26, 2016

  • Some screenshots from chrome using the device mode. It'd be great if everything fits on the screen and looks good.
  • screenshot from 2016-02-26 15-35-38
  • screenshot from 2016-02-26 15-43-16
@prastut
Copy link

prastut commented Feb 26, 2016

True.
Taking this up after my PR get's approved.

@vshivam
Copy link
Member Author

vshivam commented Feb 26, 2016

Sounds good. It'd be great if you could rethink the approach rather than just trying to fix the existing one. I believe we can do much better.

@prastut
Copy link

prastut commented Feb 26, 2016

If we are going there, I feel the whole website could be rethought in that perspective. I was talking with @irdan on IRC about this only, and I did a get a good grasp about the vision Privly is trying to build. I am a big fan of Don Norman's work in cognitive science, and I feel we could bring in more user-centric elements too. Privly is a lot more than just being an extension. I just feel it needs to convey that too.

We could discuss further if you guys agree too.

@opg7371
Copy link

opg7371 commented Feb 26, 2016

histroy_chrom

Looks cool on my chrome...atleast..it is resizeing properly
am i missing something...@vshivam
can you tell me how to generate it @vshivam

@prastut
Copy link

prastut commented Feb 26, 2016

@opg7371 We need to redesign the approach taken by the History page. We could collaborate on this if you want? I would love to brainstorm the design process with you.

The table can be rethought. Some suggestions:

screen_shot_2016-02-01_at_8 35 19_pm

Sorry for the long screenshot but I wanted to make my point noticed in the context where we have a lot of entries.

  • I really love YouTube's history page. We can divide the page into 2 sections.
    • One for the preview. Reduce clicks by:
      • Doing away with the modal that get's triggered. The options present on the modal can be brought in the form of dropdown only.
        • One issue I can think of is the length of the message being posted. Would have to make it a scroll-able content -> than modal seems a better option.
    • The second containing all the details of the post (updated_at). We can have the content filter floating on the sides.
    • The details can be shorten down to icons:
      • Is it necessary to show the length of the entire period in full detail. Can probably round off and on hover show them the actual time. 3 icons for the each detail.

The content filter on the sides:
fireshot capture 14 - 38 your content - quora - https___www quora com_content

@smcgregor
Copy link
Member

@prastut doing a complete redesign of the History app is a good thing, but many of the changes you propose will take a lot of development time and effort to get the UX right. The immediate problem (which always seems to be problematic) is that the app's display on Android is terrible because the width is too small.

Regarding your design:

  • Automatically previewing all the links means gracefully handling cases where the keys are not known to the current scripting environment.
  • Some content can be quite long, so all the privly-apps will need to support some notion of a "preview" length.
  • The performance of the app, particularly on mobile, might not be very good if too many links are processed simultaneously. The History app will likely need to conditionally load previews as users scroll through the list. Otherwise the app will hang for a few seconds every time it is launched.

If your goal is to get a GSoC project selected (conditioned on Privly becoming a mentoring organization in 2016), you should either develop your ideas for the history app into a complete proposal for a sort of Privly dashboard, or submit a patch for the current Android problem and move onto something more related to what you would want to propose.

@opg7371
Copy link

opg7371 commented Feb 27, 2016

@prastut @smcgregor if this project does not get selected, we will love to work on it on the coming time.

@smcgregor
Copy link
Member

@opg7371 Sounds good. Let me know if I can point you to resources for something.

@opg7371
Copy link

opg7371 commented Feb 28, 2016

@smcgregor it would be great...but if you can point me towards what is causing this histroy layout.....
Small suggestion would be appreciated...

@vshivam
Copy link
Member Author

vshivam commented Feb 29, 2016

@smcgregor
Copy link
Member

@opg7371 Patching the current approach requires playing with Twitter Bootstrap's responsive columns. The current layout is having issues responding to the smallest of screens.

@prastut
Copy link

prastut commented Feb 29, 2016

Since @opg7371 was working on this for a long time, I won't take this up until he says. :D

@opg7371
Copy link

opg7371 commented Feb 29, 2016

@prastut. Thanks bro....
@smcgregor. Fixed the issue... I have Internet problems in my area today
I will create a pull request once that settles

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

4 participants