Confirmed users
394
edits
Connected Devices/Projects/Project Tablet: Difference between revisions
Jump to navigation
Jump to search
Connected Devices/Projects/Project Tablet (view source)
Revision as of 10:32, 15 June 2016
, 15 June 2016Architecture overview
Benfrancis (talk | contribs) (Added device build instructions) |
Benfrancis (talk | contribs) (Architecture overview) |
||
| Line 58: | Line 58: | ||
* [https://docs.google.com/presentation/d/1N3CJPJysHtkLrCHwQH9CU_h2PiJ4769_TizzgqqfohE/pub?start=false&loop=false&delayms=3000 Early UI Mockups] | * [https://docs.google.com/presentation/d/1N3CJPJysHtkLrCHwQH9CU_h2PiJ4769_TizzgqqfohE/pub?start=false&loop=false&delayms=3000 Early UI Mockups] | ||
* See [https://www.youtube.com/watch?v=Ewvg_neKz4k video] of early prototype in action | * See [https://www.youtube.com/watch?v=Ewvg_neKz4k video] of early prototype in action | ||
== Architecture == | |||
The prototype for Project Tablet uses the build system and Gonk widget layer from [https://wiki.mozilla.org/B2G B2G] but has a much simpler architecture than B2G for smartphones. Simply put, it's Firefox browser chrome running directly on the lower levels of Android without an app runtime in the way. | |||
[[File:Project Tablet Architecture.png|600px]] | |||
Compared with B2G there is no packaged app runtime or permissions model (mozApps) and no built-in packaged apps (Gaia). The system apps are replaced with system chrome and everything else is standard web content. Our intention is to remove legacy device APIs from Gecko which are never going to become web standards and replace the ones we still need with web services running on a local Node server on the device, which talk to the Android hardware abstraction layer on the back end. The Android Linux kernel and HAL should remain as close to upstream AOSP as possible. | |||
== Meetings == | == Meetings == | ||