Core roles
Experience | Product & Engineering |
---|---|
Hilary Gordon
| Poornima Hanumara
|
Bronwyn Hawkins
| Colin Brash
Mian Khalid (Khalid)
|
Communication
Slack Channels:
#mobile-design-sync for design related conversations
#mobile-engage-sync for Engage squad and Mobile squad crossover collaboration
#mobile-team for product delivery team happenings, internal chatter only
#mobile for broader communications
Aliases
@ edx-mobile for the whole mobile squad
@ mobile-ios for the iOS team
@ mobile-android for Android team
Key Mobile App Design Decisions
- We will add mobile components and styles to the Low Fi figma library as we go.
- Whoever is working in hifi will identify component to add to the common library and publish them.
- We are not careful about what is published in this common library since only one team depends on it. There is no requirement to review patterns at the Paragon Working Group meeting.
- The mobile library will have its own type styles, but will inherit colors from the web Paragon library
- We’ll maintain a Figma library “Supplemental Mobile Components”, named specifically to indicate our preference for native controls.
Mobile App Accessibility
Relevant Guidelines:
[Jeff to help fill in]
Process:
[Hilary and Jeff to fill in]
Mobile Design Guiding Principles
How do we determine what parts of the app should be native components or custom, designed components?
Consider native:
“When it makes no, difference use the native control in design”, in other words, bias towards native unless there’s a good reason not to
If the interaction is the same and color is the only difference, and the difference is small we should use native. For example: we will not implement a custom design for the switch control on android.
Consider custom if:
Interactions are heavily branded and specific to edX
We want a consistent experienced for our learners across both platforms
How do we determine what parts of the app should be native or web views?
On a case by case basis, we’ll evaluate the needs of the experience and determine how to move forward
The key benefit of a web view is that we inherit the enhancements that is implemented on the web
The key benefit of a native experience is that we can leverage native functionality for the device, which enables deeper and more bespoke interactions
Resources
Native iOS and Android resources and pattern libraries
https://material.io/components?platform=android for Android
Official Figma: https://www.figma.com/@materialdesign
Human Interface Guidelines for iOS
edX specific
Mobile supplemental components Figma library - hi fi components for mobile use