McLean, VA (PRWEB) August 03, 2012

Managing and assuring quality in a widget development effort presents some challenges in regards to best practices and defining areas of responsibility. Due to the varying nature of functionality from the data sources widgets may be using, defining what layers or tiers are needed by a widget in general is challenging. The design choices that are made to satisfy the needs of a widget will also affect the basic architecture. This document sketches out general patterns seen in widget development and what implications these patterns have for implementing best practices. Additionally, this document attempts to define what constitutes a widget to establish the area of developers responsibilities for development and support.

Highlights from Ozone Widget Development Standards white paper include: