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

Hard to distinguish which input field contain what kind of data #440

Open
schiessle opened this issue Jun 23, 2016 · 8 comments
Open

Hard to distinguish which input field contain what kind of data #440

schiessle opened this issue Jun 23, 2016 · 8 comments

Comments

@schiessle
Copy link

schiessle commented Jun 23, 2016

If you start with a empty contact the placeholder tell you which kind of data should be added to which field. But if you look at a existing contact there is no indication about the input fields data.

For example look at this screenshot:

contacts

Can you tell me what data is stored for John Doe?

Here is the answer (but I only know it because I created the input fields and added the data):

From top to the bottom:

  • Home phone number (this people might be able to guess, but it could be also any other numeric id, e.g.a fax number)
  • work email
  • home email
  • no, not again my home email address, this time it is my instant message id (jabber/xmpp)
  • this is not a second home email address but my federated cloud ID

As you can see this is highly confusing. I think we should have some kind of labels for each input field.

cc @owncloud/designers

@skjnldsv
Copy link
Contributor

Do you suggest some header title for the fieldset types?

@schiessle
Copy link
Author

schiessle commented Jun 23, 2016

Do you suggest some header title for the fieldset types?

Yes, a header title could be a solution. Or a label next to each input field? Maybe "home", "work",... could also be extended to "Home Email", "Work Email",... or something like that? Or a tooltip on hover, but might be also hard to detect and doesn't work on mobile.

I don't have a special solution in mind. I'm happy to let the developers and designers decide what fits best. But I think there should be definitely something added to distinguish the input fields.

@jancborchardt
Copy link
Member

Yes, we need to bring back the small header inbetween the fields, like we had in the old Contacts app. :) @skjnldsv do you want to take care of that?

(Should be the size of the text, same opacity/greyscale as the field labels, and left aligned with the fields themselves – not on the far left.)

@skjnldsv
Copy link
Contributor

skjnldsv commented Jun 23, 2016

This could be compatible with the way the page is calculated. All the fields are grouped by types.

@jancborchardt I don't have the time right now. But I should be able to work on the app again and continue my work on #411.
#411 is compatible with some heading here. I will see what I can do :)

@MorrisJobke
Copy link
Contributor

I like how the android input field labels are shifted up once you type something in:

screenshot_20160623-163549
screenshot_20160623-163603

@skjnldsv
Copy link
Contributor

I'm on the opposite side :p
I hate this way of displaying a placeholder. This seems like a new thing a lot of webdev start doing. This confuse the hell out of me! ^^

I think we should keep it simple. :)

@jancborchardt
Copy link
Member

@MorrisJobke this is not about the same labels though, and also this switching is weird. For addresses e.g. there is a top »Address« label and all the fields like street, city etc have their own labels.

@skjnldsv awesome! Sure, take your time. I would say it should not be part of #411 though since it’s unrelated. And having big pull requests is never ever good! :) Just do a separate pull request for it.

@skjnldsv
Copy link
Contributor

Of course :)

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

No branches or pull requests

4 participants