Julian Norton – Week 1
App concept
Solve for people who want to browse local farmers markets, and allow people to let farmer’s know beforehand what they’d like to buy. Once they get to the farmers market, all they’d have to do is pick up what they’ve reserved, and pay.
About Julian Norton
I have a BFA in Graphic Design, and experience with both coding websites and designing web & mobile applications. I’m as comfortable with github repositories and writing LESS (CSS), as I am with UI/UX. I’ve been designing at PublicStuff since 2012.
New things learnt from Android Design Guidelines
- Tablets will combine what are multiple views on mobile, into a single view for tablet
- While scrolling, boundaries should become apparent once the user reaches the edge of a screen.
- Spacing between each UI element is 8dp.
Jun 18, 2014 @ 01:28:47
We talked about this in class, but your app map seems to be less visually organized than your thinking actually is. It’s worth reorganizing it to make sure that things are clear. Particularly strange are 2.2 and 4.0 bending over to to line up with other views.
Once you’ve chosen a particular farmer’s market, you’re currently only allowing browsing by item. I wonder if it’s worth allowing people to browse by farmer as you do at a physical farmer’s market. Maybe this is covered by 4.0’s also selling; just want to make sure this is a considered choice.
On 4.0 single item, you’re using eggs right now, and so your interface has been made a little more specific than you’d want. You’d certainly want to allow people to choose a number of items (though if was something like chicken breasts, maybe I’d want to get 15 for a dinner party?), but perhaps the item should hold the amount if needed (e.g. “a dozen eggs”), making your interface more extensible. I also think you’ll want to use something like an android spinner (http://developer.android.com/design/building-blocks/spinners.html – reading about spinners led me down a whole android interface rabbit hole, but anyways) for your selection to make the number more open ended.
Also in my Android reading saw that they recommend not using the “>” to indicate that you can drill down for platform consistency (http://developer.android.com/design/patterns/pure-android.html).
I’d say to take 5.0 to be completely full screen, instead of with the close button. You’re already filling the screen basically, and the close button is pretty awkward for a mobile context. The popover can help keep context, but I don’t think that anyone will be confused about the fact that they’ve made the decision to buy the eggs. We’ll also want to make sure that the “Reserve for Pickup” button is a strong enough call to action, but let’s worry about that more during design, though it might be something to test for next week when prototyping.
What’s in settings? Is that where the action overflow triple dots takes me?
Other things I know I said in class, but just to record again:
– Should I be able to filter the markets by time or other factors?
– It’s worth doing a black and white version of a map in the background of that page, just so there’s no confusion about what’s going on
– Will there be rules for releasing reserved items at certain point?
– The search area feel unconnected from what things you’re actually searching, so move it down to be by the content you’re actually searching
You’re doing some good thinking here. Looking forward to seeing this week’s iteration!