Confirmed users
71
edits
DeveloperExperience/Mozilla-App-SDK: Difference between revisions
DeveloperExperience/Mozilla-App-SDK (view source)
Revision as of 02:01, 28 August 2012
, 28 August 2012no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
* Web Components | * Web Components | ||
* Documentation (app-specific APIs) | * Documentation (app-specific APIs) | ||
== Developer Tools == | == Developer Tools == | ||
| Line 16: | Line 17: | ||
* third-party web sites/apps | * third-party web sites/apps | ||
* JS frameworks for testing | * JS frameworks for testing | ||
== Layouts & Bootstraps == | == Layouts & Bootstraps == | ||
| Line 26: | Line 26: | ||
* Layout markup should be constructed in a way that ensures the apps produced look and operate flawlessly from device to device at any resolution, in both touch and non-touch environments. | * Layout markup should be constructed in a way that ensures the apps produced look and operate flawlessly from device to device at any resolution, in both touch and non-touch environments. | ||
* Bootstraps should not require command line knowledge to generate. A developer should be able to assemble a layout or bootstrap package via GUI | * Bootstraps should not require command line knowledge to generate. A developer should be able to assemble a layout or bootstrap package via GUI | ||
== Web Components == | == Web Components == | ||
As an emerging standard that will radically reduce developer effort, we should create a stock set of components that provide the UI and behavioral elements common to complex web applications. Each component shall be tested x-browser, look and operate well on different devices/resolutions, and have touch capabilities built-in where applicable. All components should emphasize the declarative abilities inherent to the native elements and be composeable in markup the same way native elements are. | As an emerging standard that will radically reduce developer effort, we should create a stock set of components that provide the UI and behavioral elements common to complex web applications. Each component shall be tested x-browser, look and operate well on different devices/resolutions, and have touch capabilities built-in where applicable. All components should emphasize the declarative abilities inherent to the native elements and be composeable in markup the same way native elements are. | ||
== Documentation (and Tutorials) == | == Documentation (and Tutorials) == | ||
The SDK should collect and present documentation for all the app-specific pieces a developer needs to create, debug, publish, and support an HTML5 app. Documentation of all Mozilla-specific services, such as the Marketplace and payments APIs, should be included in the SDK as well. | The SDK should collect and present documentation for all the app-specific pieces a developer needs to create, debug, publish, and support an HTML5 app. Documentation of all Mozilla-specific services, such as the Marketplace and payments APIs, should be included in the SDK as well. | ||