This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
agl-roadmap [2020/03/25 12:57] waltminer [From App FW and Security EG] |
agl-roadmap [2020/03/25 13:20] waltminer [From App FW and Security EG] |
||
---|---|---|---|
Line 66: | Line 66: | ||
* Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | * Security workflow. Now that we have the building blocks in place, turn on security and put in place a mechanism for developers to sign applications, load them. | ||
* Changes necessary at binder level for V2C (SSL transport) | * Changes necessary at binder level for V2C (SSL transport) | ||
+ | * App Signing and Installation Mechanism | ||
* Developer workflow is needed for managing keys | * Developer workflow is needed for managing keys | ||
- | * //Development mode and Production mode for app management// | + | * Development mode and Production mode for app management |
* Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system. | * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system. | ||
- | * //Terminal app on home screen// | ||
- | |||
* App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5 | * App Launcher for web apps and strategy for managing code that can be downloaded on the fly by HTML5 | ||
* App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? | * App Framework API and strategy to stop non-privilege apps that are currently in the background (e.g., SIGTERM). Do those apps save their state so they can restart quickly? | ||
* App Framework binder communications shall be able to manage return from sleep mode. | * App Framework binder communications shall be able to manage return from sleep mode. | ||
- | * **GG Priorities for App FW** | + | * App Life Cycle |
* Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH | * Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH | ||
* Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread) | * Background app awareness on the home screen - (e.g. Current song on media player, phone call in progress, # messages unread) | ||
* Kill apps individually from life cycle manager | * Kill apps individually from life cycle manager | ||
* Need to define state diagram for app life cycle | * Need to define state diagram for app life cycle | ||
- | + | ||
- | * //Multi-user use case// | + | |
* API for abstraction of hardware mechanism for signing apps, packages, etc. | * API for abstraction of hardware mechanism for signing apps, packages, etc. | ||
- | * //Unit testing for app framework// | ||
* //Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms.// | * //Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms.// | ||
* //Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]]// | * //Split off the keys from the App FW. Currently are [[https://git.automotivelinux.org/src/app-framework-main/tree/certs | here]]// |