Gaia/New-Architecture-Program: Difference between revisions
mNo edit summary |
(Added web app bridge link and minor edits.) |
||
| Line 1: | Line 1: | ||
= Program Overview = | = Program Overview = | ||
The new Gaia architecture (or, the next generation Gaia architecture) proposes a new application framework that aims to create a more webby Firefox OS application platform. | The new Gaia architecture (or, the next generation Gaia architecture) proposes a new Firefox OS application framework that aims to create a more webby Firefox OS application platform. | ||
The proposal is documented in https://wiki.mozilla.org/Gaia/Architecture_Proposal | The proposal is documented in https://wiki.mozilla.org/Gaia/Architecture_Proposal | ||
Each components of the architecture will be validated by applications | Each components of the architecture will be validated by converting applications to use these components. For example Music will be converted to have its front-end separated from its back-end with the app bridge being the protocol machine for the front- and back-ends. | ||
Initially two apps are chosen to be converted to the new architecture to evaluate the new architecture's APIs as well as to evaluate the "new" apps' performance and memory profiles. In the process of conversion we will also focus on the useability of the APIs for apps developers and best practices on Firefox OS apps | Initially two apps (Music and SMS) are chosen to be converted to the new architecture to evaluate the new architecture's APIs as well as to evaluate the "new" apps' performance and memory profiles. In the process of conversion we will also focus on the useability of the APIs for apps developers and best practices on Firefox OS apps development based on the new architecture. | ||
More details on the the validation plan is here: https://wiki.mozilla.org/Gaia/Architecture_Transition_Validation | More details on the the validation plan is here: https://wiki.mozilla.org/Gaia/Architecture_Transition_Validation | ||
| Line 17: | Line 17: | ||
= Team Wiki's and detailed Team Status = | = Team Wiki's and detailed Team Status = | ||
* SMS | |||
* Music | |||
* [https://github.com/gaia-components/threads Web app bridge] | |||
* Service worker | |||
* Telemetry | |||
* Navigation | |||
* Data sync | |||
= Contacts = | = Contacts = | ||
Revision as of 01:29, 20 April 2015
Program Overview
The new Gaia architecture (or, the next generation Gaia architecture) proposes a new Firefox OS application framework that aims to create a more webby Firefox OS application platform.
The proposal is documented in https://wiki.mozilla.org/Gaia/Architecture_Proposal
Each components of the architecture will be validated by converting applications to use these components. For example Music will be converted to have its front-end separated from its back-end with the app bridge being the protocol machine for the front- and back-ends.
Initially two apps (Music and SMS) are chosen to be converted to the new architecture to evaluate the new architecture's APIs as well as to evaluate the "new" apps' performance and memory profiles. In the process of conversion we will also focus on the useability of the APIs for apps developers and best practices on Firefox OS apps development based on the new architecture.
More details on the the validation plan is here: https://wiki.mozilla.org/Gaia/Architecture_Transition_Validation
Status
Several components of the architecture have teams identified. Initial team meetings have taken place to discuss teams' high level goals and technical approach for the components. After the initial meetings, the teams will deep dive offline and when they are ready, they will share their findings and plans with the Gaia community at kick-off meetings.
Team Wiki's and detailed Team Status
- SMS
- Music
- Web app bridge
- Service worker
- Telemetry
- Navigation
- Data sync
Contacts
- EM: Francisco Jordano
- EPM: Jacob Shen