Create mockups for edit plot, create order, and welcome screen about gardenhub HOT 11 CLOSED

I'm not ruling out the shaking.... :P

from gardenhub.

A submit order button, what do you mean? You mean the users can't just shake their phone and make it submit? 😜

My mistake. I'll update the design after completing the others, unless you implement something first.

from gardenhub.

Screen for when a user logs in and has no upcoming harvests

My inspiration for this design is elementary OS's "welcome screen" design standard. Example below:

elementary OS has a fantastic HIG and it's worth reading their recommendations for first launch experience and welcome screen.

This was a quick sketch, but down the line we may want to come back and also add "manage plots" or "manage gardens" as extra options alongside "submit an order". For now they're configured under the "manage" nav at the top. I have other ideas about that too though, such as only prompting for the creation of those items when the app detects that they user doesn't have any made.

from gardenhub.

This looks good! Thanks!

from gardenhub.

Submit new harvest screen

Here's a mockup for a "submit new order" screen.

Certain aspects of this design I don't consider to be final, such as the colors of the selected crops and the "add another" button. These are things we can adjust after it's coded, so I'd say go ahead.

I envision the input boxes having some special functionality. The date inputs should pop up a calendar to select from, and the "select a plot" should show the relevant plots organized by the garden they belong to.

from gardenhub.

This looks great! Thanks!!

from gardenhub.

I think there should be a submit order button on the new order design.

from gardenhub.

Here's the edit plot screen. Submit button intentionally omitted.

from gardenhub.

Android seems to like putting "submit" buttons in the floating navbar. My intuition is to do something like this, but I'm not totally sure. Some examples below.

My only hesitation is that icons without labels add complexity. We can't assume a user will understand them. For instance, I wrote the word BACK aside the back arrow because user testing shows that people a way more likely to open a hamburger menu that actually says the word "MENU" beside it. You have to really spell it out to people. It's kinda like how plain text emails perform better than fancy templates; the reality is that pretty design often overcomplicates things for the user.

from gardenhub.

RE: edit plot design:

How do users delete crops? Also we don't need the tap to select stuff here.

from gardenhub.

I think we can close this one. Let's open new, more detailed issues if necessary.

from gardenhub.