Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continuing improving the UI #47

Open
wants to merge 21 commits into
base: master
Choose a base branch
from
Open

Continuing improving the UI #47

wants to merge 21 commits into from

Conversation

jsimplicio
Copy link
Collaborator

No description provided.

@jsimplicio
Copy link
Collaborator Author

@maxogden hey max, been thinking of alternate ways to lay out the main header. I figured putting the back arrow next to the quit button to the right looks all right, but how about something more like what phone apps look like:
screen shot 2015-11-29 at 2 21 45 pm
That way we have a clear spot for returning arrows, the app name, and quit.

Let me know how you feel about this!

@max-mapper
Copy link
Owner

+1, reminds me of "Title bar with link buttons and icons" on http://goratchet.com/components/ (or more generally of phone UX which you already pointed out), which is a good thing.

@jsimplicio
Copy link
Collaborator Author

@maxogden Alright so here's the latest
screen shot 2015-11-29 at 4 59 19 pm
screen shot 2015-11-29 at 4 59 24 pm
screen shot 2015-11-29 at 4 59 57 pm
screen shot 2015-11-29 at 5 00 14 pm

@NickColley
Copy link

@jsimplicio looking niice, to make it more clear would it make sense to give the back button the label 'back'?

@jsimplicio
Copy link
Collaborator Author

@NickColley Do you feel like an arrow pointing back isn't enough? Or doesn't describe 'back' enough?

@jsimplicio
Copy link
Collaborator Author

Here we are
screencat-6
screencat-7
screen shot 2015-12-23 at 11 40 09 am

@max-mapper
Copy link
Owner

@NickColley
Copy link

@jsimplicio better to include text as an icon can be ambiguous even if it seems obvious http://uxmyths.com/post/715009009/myth-icons-enhance-usability

It's looking great though!

@jsimplicio
Copy link
Collaborator Author

@NickColley I think you don't always need a label. Some icons do work well. Like, I know everyone tends to hate on the hamburger icon for menus, for example, but by now that thing is most likely recognized everywhere.

I thought that back arrow was doing a fine job on its own, but you've pointed out something very valid 👍

@jsimplicio
Copy link
Collaborator Author

@NickColley 😄
screen shot 2015-12-27 at 12 18 03 pm

@jsimplicio
Copy link
Collaborator Author

@maxogden I tried making the main-header fixed but it somehow breaks the screens a little bit, it adds scroll bars to small screens that don't need them. I think it has to do with the margin I applied to the top of the body to push the content down since I gave position: fixed to the header. Not sure what to do, but want to avoid scrolling on these smaller height screens:

screen shot 2015-12-27 at 1 30 06 pm

@max-mapper
Copy link
Owner

hmm I suck at fixed header CSS actually. if i get a chance i'll try and mess with it

@jsimplicio
Copy link
Collaborator Author

@maxogden Ended up figuring it out. Gave a padding-top to a new class main-content I gave to <main>. Works out fine!

@jsimplicio
Copy link
Collaborator Author

I think my latest does a pretty decent job at choosing screens although I was wondering if a row of two screens per row instead of one is best? Some people may have thousands of stuff open and not sure how to best provide a better searchable list? I was thinking a pretty big rectangular pop up with all the screens would be best? Not sure how that's even feasible or if it even is. I don't mind the scrolling through screens thing but I'm just one user and I built it this way so I am biased :) @maxogden @NickColley thoughts?

screen shot 2016-01-18 at 9 01 24 pm

@NickColley
Copy link

@jsimplicio that looks great, I think you could try a grid layout for the screens so they always fill as much space as possible, but that's a lot more complicated than what you have so maybe just get this in as is and review later?

@jsimplicio jsimplicio changed the title Fixing QUIT button and other small bugs. Continuing improving the UI Jan 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants