Create pointer node extensions on the Object Navigator home page only for major applications and solutions. This approach provides consistent and meaningful user experience for the customized vSphere Web Client.

When you create a view for your Flex extension, use the vSphere Web Client SDK Model View Controller framework (Frinje) and the Data Access Manager APIs to achieve better performance and scalability.

When creating action set extensions for a particular type of vSphere object, you must use the extensions filtering mechanism. The defined action sets must be visible only when the user selects the relevant vSphere object type. For more information about how to filter extensions, see Filtering Extensions.

If your Flex-based solution extends the com.vmware.flexutil.proxies.BaseProxy class, make sure that you are not hard-coding the channel URI. Use the getDefaultChannelUri() method of the com.vmware.flexutil.ServiceUtil Flex class.

Use the Data Access Manager API for retrieving data from the service layer. You must use proxies only for adding, editing, and deleting issued data requests.

For better performance, avoid making proxy calls that require more than several seconds to return a response. A best practice is to design your extensions to submit a task that returns immediately, and to track the task progress.

If you use proxies for data requests, verify that you receive the request response before sending another one through the proxy.

If you want to use localization data for your plug-in package, follow these recommendations:

<plugin id="com.vmware.samples.helloworld_i18nui"
   moduleUri="Helloworld.swf" defaultBundle="com_vmware_samples_helloworld">

   <resources>
      <resource locale="{locale}">
         <!-- relative path of the .swf generated by the build script.
            {locale} will be set at runtime to the current vSphere Web Client locale
         -->
         <module uri="locales/helloworld-{locale}.swf"/>
      </resource>
   </resources>

....

</plugin>