Week 2
Hi! I’m a designer from San Francisco. I like sci fi and kayaking.
PROJECT
HIG NOTES
1. Avoid customizing core components without a great reason.
“Don’t create custom UI that prompts users to sign into Game Center.”
Apple constantly reminds people to avoid customizing iOS fundamentals. My guess is that this is to make it so that people enjoy using iPhones. For example, it wouldn’t be the worst thing if one or two apps customized how game center login works, but if every app did, people might start to be confused about what game center is.
2. Write good copy
“Write a title that makes it unnecessary to add a message,” “Avoid sounding accusatory or judgmental when you need to deliver negative news,” “The best button titles consist of one or two words that describe the result of tapping the button.”
Apple gives a lot of great copy advice. They seem to care deeply about making clear labels that people will understand, not duplicating text, and making sure that punctuation and capitalization is appropriate.
3. Don’t make people think
“If you vary the transition styles for modal views in an app, do so in a way that makes sense to users. Users are quick to notice behavioral differences in an app and will assume that they mean something.” “[Having more than two options in an alert] …is a disconcerting experience for users, because they must spend extra time to distinguish the choices.”
Apple finds lots of ways to drill in the idea of reducing cognitive load (via recognition over recall, reducing options, shortening copy, etc). They constantly suggest ways to avoid making users think in unnecessary cases. At the same time, they also say things like:
“Give users different ways to sort multiple transit options. Lots of factors influence people’s transit decisions—such as time of day, weather, and how much they’re carrying—so it’s important to make it easy to compare transit options.”
In this case, Apple is saying that 80% of people actually want multiple sort options, so having more options is necessary.
4. Make simple load screens
Load screens should be a text/imageless version of an app’s main screen, not a splashy intro page.
Jul 24, 2015 @ 09:36:58
It could be cool to go into more detail about what your notification content will be.
You mention that 1.1 needs work, and I’m not totally sure what all is going on there. I think what you’re doing is showing other suggested things from that restaurant that go well with the main dish. That seems to make sense.
On 1.1.1 add address, I probably need room for a 2nd address line, city, and state.
It’d be cool if your credit card could be saved for future ordering. You may want to give people the option to create an account after ordering if they’d like to do that to make ordering even faster in the future.
The step by step, here’s what’s happening, is interesting, but I’m not sure the infrastructure that would be necessary to accomplish that.