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

Misuse of circumference field due to positioning in mobile applications #321

Open
hadleystein1 opened this issue Oct 13, 2016 · 2 comments

Comments

@hadleystein1
Copy link

TreeFolks, an Austin, Texas-based customer, reported that users regularly put input the circumference into the diameter field, because the diameter field appears above circumference on the mobile application.

Question from Tree Folks:

  • Is it possible to make the diameter field editable like another field so that you can remove it from the app and/or drop and drag to the ideal location (i.e. below circumference)?
@dboyer
Copy link

dboyer commented Oct 17, 2016

I like the idea of letting the tree map owner customize whether diameter can be entered as diameter, circumference, or both. That's probably a feature that happens on the website in general and trickles down to the apps.

@hadleystein1
Copy link
Author

I agree, @dboyer. I assume most trees are being added via mobile or bulk upload (something we will not know for sure until analytics are implemented), so it will perhaps be more important for the feature to trickle down to mobile than for it to be available on the Add A Tree process on the web application.

@jwalgran jwalgran added the bug label Jan 20, 2017
@dboyer dboyer added the high label Jul 5, 2017
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

3 participants