canmove, Confirmed users
901
edits
WebAPI/DesignGuidelines: Difference between revisions
→Design considerations
| Line 74: | Line 74: | ||
* standardization is sometimes not necessary for APIs designed for very narrow use cases or those that have no hope of being implemented by other UA vendors. | * standardization is sometimes not necessary for APIs designed for very narrow use cases or those that have no hope of being implemented by other UA vendors. | ||
* bringing existing technologies to the web gives a chance to mask details that aren't of interest or important to web developers. | * bringing existing technologies to the web gives a chance to mask details that aren't of interest or important to web developers. | ||
* 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! maintain web compatibility! | ||
* Be consistent. No special cases in the APIs. | * Be consistent. No special cases in the APIs. | ||