This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
20170612_ui_gra_telco_mm_review [2017/06/24 01:31] tmatsuzawa |
20170612_ui_gra_telco_mm_review [2017/06/26 00:48] (current) tmatsuzawa |
||
---|---|---|---|
Line 13: | Line 13: | ||
* Takashi Matuszawa | * Takashi Matuszawa | ||
* I think the spec should describe what are the concepts that are shown to the end-user and the actions (use-cases) that are provided. And vendors can freely implement their HMIs but providing what the spec specifies. | * I think the spec should describe what are the concepts that are shown to the end-user and the actions (use-cases) that are provided. And vendors can freely implement their HMIs but providing what the spec specifies. | ||
- | * e.g. | + | * e.g. |
* HMI should provide following set of applications. | * HMI should provide following set of applications. | ||
* 1) "all applications" | * 1) "all applications" | ||
Line 28: | Line 28: | ||
* Select (make active) one of them. | * Select (make active) one of them. | ||
* Quit one of them. | * Quit one of them. | ||
+ | * HMI spec should describe if there are class of applications that needs special treatment and what they are | ||
+ | * e.g. | ||
+ | * Navigation | ||
+ | * Audio | ||
+ | * Rear-camera | ||
+ | * HMI spec should describe common operations (if there are any, as AGL HMI standard feature) | ||
+ | * e.g. | ||
+ | * "back" operation | ||
+ | * Press "back" button | ||
+ | * Swipe screen to right | ||
+ | * (what button/gesture is bound to "back", and how this "back" is interpreted may be implementation specific?) | ||
+ | |||