Hacker News new | past | comments | ask | show | jobs | submit login

> If most of the apps a user uses follow the guidelines of Android/iOS, and they are primarily a user of one platform, and your app doesn't follow either, it seems obvious that they won't be able to use their built-up knowledge of how apps work in general to navigate your app.

I just checked my 8 most commonly used apps, exclusing Chrome / Gmail, FWIW I am using Android.

1. Spotify - Doesn't follow any sort of UI standards. Also randomly decides to go into drive mode.

2. Clock - Built in, follows guidelines. About 50% of the time I hit the "trash" icon when I want to reset a countdown timer.

3. Development tool, not counting this

4. Libby, awesome app to checkout books local libraries. They have some seriously cool (but not always discoverable!) UI elements that custom solve problems that have. Their audio scrubber and speed changer for audio books are really cool.

5. Tabata timer - Doesn't follow any guidelines, really really needs a "stop" button instead of relying on back button to stop a workout.

6. Audible - Custom purpose driven UI, similar to Libby but different enough it can be a bit troublesome going back and forth.

7 and 8. Games, always have a custom UI, no problem using them.

tl;dr normal doesn't exist.




> 1. Spotify - Doesn't follow any sort of UI standards. Also randomly decides to go into drive mode.

And lesson #1 in why to always follow some/any kind of UI standard.. Luckily their algorithms/service are decent.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: