"Android and iOS" or "Android vs iOS"
In next week's project, I will design a new mobile e-learning platform to be launched on both Android and iOS. My primary personas are Alicia. She is International Buyer at Mango. She wants to learn digital marketing and growth hacking to move to the marketing team at her company.
Focused on Android and iOS differences platform, there will have five points of the different designs. I'll show it in the presentation this Friday, which is: 1. Typography 2. Button 3. Moving between states/screens 4. In-app Navigation patterns 5. Floating action button.
3. Moving between states/screens
4. In-app Navigation patterns
5. Floating action button
However, there is one thing I would like to share over here as well. In the beginning, I felt confused that I needed to separate one app into two different styles for Android and iOS. However, after I read the article in the reading lists, "You don't always need to follow native Android or iOS patterns when designing an app", I agree with its idea. As a learner, I know it is good to practice all the tasks we will meet in the future.
Here are the quotes which I would like to share:
"This thinking ultimately leads us to create a separation between iOS and Android users, rather than simply seeing them all as human beings."
"It limits our design, our approach, and our understanding by assuming that we should and must solve the problems we encounter in a certain way; that is, by following platform conventions."
https://medium.muz.li/differences-between-designing-native-ios-apps-and-native-android-apps-e71256dfa1ca
https://medium.com/@vedantha/interaction-design-patterns-ios-vs-android-111055f8a9b7
https://uxplanet.org/you-dont-always-need-to-follow-native-android-or-ios-ui-patterns-when-designing-an-app-2a361a21c342