Confirmed users
112
edits
WebAPI/DesignGuidelines: Difference between revisions
no edit summary
No edit summary |
|||
| Line 4: | Line 4: | ||
Designing APIs for the web is not an easy task. Here are some suggestions to help. | Designing APIs for the web is not an easy task. Here are some suggestions to help. | ||
=Considerations= | ==Considerations== | ||
* user privacy and data/hardware security | * user privacy and data/hardware security | ||
* fingerprinting | * fingerprinting | ||
| Line 16: | Line 16: | ||
* web APIs are "forever" so be very careful with what you expose to the web! | * web APIs are "forever" so be very careful with what you expose to the web! | ||
=Process= | ==Process== | ||
* discuss motivation and design sketches early, often, and widely (e.g. [[IRC]], applicable W3C/WHATWG lists, [https://lists.mozilla.org/listinfo/dev-webapi dev-webapi], [https://lists.mozilla.org/listinfo/dev-platform dev-platform], [https://lists.mozilla.org/listinfo/dev-gaia dev-gaia], blogs, Twitter, GitHub issues, etc.) | * discuss motivation and design sketches early, often, and widely (e.g. [[IRC]], applicable W3C/WHATWG lists, [https://lists.mozilla.org/listinfo/dev-webapi dev-webapi], [https://lists.mozilla.org/listinfo/dev-platform dev-platform], [https://lists.mozilla.org/listinfo/dev-gaia dev-gaia], blogs, Twitter, GitHub issues, etc.) | ||
* work with other UA vendors to build consensus | * work with other UA vendors to build consensus | ||
| Line 24: | Line 24: | ||
* in the majority of cases, work through an appropriate W3C or WHATWG group to publish your specification | * in the majority of cases, work through an appropriate W3C or WHATWG group to publish your specification | ||
=Resources= | ==Resources== | ||
* http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F | * http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F | ||