So we come at last to the end of our first project for Mobile Media, our food-app for either iOS or Android.
It’s funny, but my biggest reflection doing this – besides always do more user testing (which I learned hard last semester) – was actually on iOS UI elements and navigation.
Although I took the iOS class last semester and learned how to code in Swift, what all the apple UI elements were called, the Human Interface Guidelines etc., it really didn’t occur to me until this semester that I’m basically a wolf in sheep’s clothing (who can’t design his own wolf pelt???)
What I mean is that I have been, am, and unless something drastically changes, going to be an Android user first and foremost, at least as far as my primary screen – my phone- is concerned. This was actually less difficult to deal with last semester, as we never really focused on the integral components that make up good user experience. While I knew how to programmatically create different transitions, it never occurred to me why I should be using them. Everything else was actually built into xCode to make it easier on me.
However throughout this project, I frequently caught myself treating my iOS app – which I wanted to design after doing the backend for iOS and no front end – as an android app, just with different buttons. One place this became clear to me was with the back button. On iOS it is much less frequently employed, and pretty much always in the top left corner. It is really used for table views, UI collection views, and other arrays of information that lead to individual detail pages (master-detail). With Android, on the other hand, it is built into the very operating system itself. You get home, back (and something else depending on hardware). So when I built my interactive prototype I was in hot water a couple of times, because the back button on iOS usually goes back to the last screen, which works in a master-detail application for example. However this treatment doesn’t really work as an effective UX tool the same way. Looking back, I probably should have used less of the back button, and maybe sucked it up and added a bottom nav tab bar or other navigation element to help me not need to use this feature.
Anyway, that isn’t the point of this post, but just found it a really interesting experience, being an Android user who sometimes uses an iPad for programming, I have been embedded with a certain flow and tactile sensation of navigation through my device which is very very different on Apple (I’d argue worse… but people would say same about Android.)
User Feedback on Last Weeks Model
- Some of wording is still unclear, especially whether it is a button or a label. E.G. Review on the Detailview.
- I want to be able to click on the trending and nearby labels right from the main view. You should make them clickable instead.
- The filter page is good, but it isn’t clear to me right now where this goes to and how it works. If you will have subfilters, build views for them to show the relationship, and then how to get from them to the detail view page.
- Unclear how the rate screen processes the info. Link rate button to another page to show that it is posted.
- Link the reviews at the bottom of profileView back to the detailView page. They should be clickable links so that you can use them for navigation.
- Link more of the extra pictures and ratings that you have for stock images to the detailView. It’s more fun to be able to click on anything and have the navigation work.
- I want to be able to see the menu and order the food, where can I do that? Isn’t that one of the points you mentioned is key?
Interactive Feedback Link & Presentation