388 reputation
17
bio website neuromodule.com
location Mountain View, CA
age 36
visits member for 1 year, 11 months
seen May 5 at 4:35

UX Designer


Jan
9
awarded  Yearling
Aug
28
revised How to handle multiple versions of same application with different set of features
deleted 1 characters in body
Aug
28
comment How to handle multiple versions of same application with different set of features
Thanks. Everything you say makes total sense and I agree with it 100% however the problem exists due to the fact that we would have users on both versions.Most users will be on either 1 or 2 but some have requested to be on both. The goal would be to move towards V3 and port everyone to that version when ready while supporting users on V1 and V2 in the best way possible.
Aug
28
comment How to handle multiple versions of same application with different set of features
Thanks for your comment. Could you elaborate a little bit more on the hot keys. Not sure I understand where it fits in this picture. This application would not make use of hot keys, but if it would, what we they be used for?
Aug
26
revised How to handle multiple versions of same application with different set of features
added 31 characters in body
Aug
26
comment How to handle multiple versions of same application with different set of features
Should have clarified. This would be a web application and the reason the two versions could not share content is due to being built on two different code bases.
Aug
26
asked How to handle multiple versions of same application with different set of features
Jan
16
comment Should email verification links expire?
My answer of course only applies if the confirmation email include the expiration date, which I assume it would.
Jan
16
answered Should email verification links expire?
Jan
16
comment 'Mark as read' on items that can not be 'opened'
I see. Good point. I like it due to the fact that it "forces" the users to read all updates which is definitely a good thing, on the other hand it adds a lot of friction. but perhaps it wouldnt be too bad.
Jan
15
comment 'Mark as read' on items that can not be 'opened'
Yeah, the updates can be of varying length, some just a few words, some a couple paragraphs of text and could also include links.
Jan
15
awarded  Commentator
Jan
15
comment 'Mark as read' on items that can not be 'opened'
Got it. So that would mean that if I have no updates, I can not open the dropdown, correct? Or should the dropdown still open but show a message saying there are no new updates? What if I want to read old updates?
Jan
15
comment 'Mark as read' on items that can not be 'opened'
So the difference between how it works today and your suggestion is that we show only one update at a time? Lets imagine you have 10 updates, wouldnt it be cumbersome having to click next 10 times to read them all instead of directly clicking the View All link and see them all but still being able to tell unread from read, or old from new?
Jan
15
comment 'Mark as read' on items that can not be 'opened'
I see. So instead of marking them as read when you visit the page with updates, you do it as soon as the dropdown is opened? So, lets say you have 5 updates, but only 2 of them are 'unread', how would you handle that?
Jan
15
comment Where to put a global “add item” button?
1) I think StackExchange would be better off with having the Ask Question closer to the left side. They get away with having it on the right since its very prominent but on wider screens it still almost disappears out of view. 2) The blue button in twitter is not nearly as prominent as it should be however they do this to be consistent with their mobile app and they also back it up with having a 'compose new tweet' field on the left on the start page. 3) I dont see the main 'add item' button on the right in google however they do have a very prominent red compose/create button the left.
Jan
15
awarded  Scholar
Jan
15
accepted Group settings depending on state
Jan
15
comment Group settings depending on state
Thanks @obelia, I'm thinking this is probably the best solution.
Jan
14
comment Group settings depending on state
I did consider this but the problem is that each "feature" can have names that take up most of the page width and in most cases you also need to be able to read the whole feature name without tooltips, mouseover effects etc.