Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
android_brands [2014/06/05 16:35]
ybarajas [Applying the Brand to a Profile]
android_brands [2014/06/05 20:37] (current)
ybarajas [Applying the Brand to a Profile]
Line 1: Line 1:
 +====== Branding ======
 +
 +
 +Branding capabilities are optional and may not be available for your enterprise. If available, you can brand the client on the **Account** tab in the Open Mobile Portal.
 +
 +===== Before Creating a Brand =====
 +
 +Branding requires that you make design decisions, create product and component names, and upload image files for client components. You should assemble the required files and text labels before beginning the process of creating a brand.
 +
 +===== After Creating a Brand =====
 +
 +Once you have created one or more client or portal brands, you can publish them to production. Only one brand may be active at a time, and it cannot be deleted. (Deleting a brand could cause conflicts with deployed profiles that use an existing brand.)
 +
 +
 +===== Branding Your Client =====
 +
 +
 +A client brand comprises the set of icons, images, text strings, additional help content, and colors you choose to include in the client’s look and feel. The complete list of client branding options includes these selections. If no element is selected, the default is used.
 +
 +
 + ​[[:​android_branding_elements|Please click this link]] for a complete list of branding options.
 +
 +
 +===== Creating a Custom Package Name (Optional) =====
 +
 +
 +Creating a custom package name is optional. If this capability is enabled for your enterprise, attaching a custom package name to a client will prevent that client from automatically upgrading with each iPass release in the Android Market. In turn, this will prevent certain branded elements from reverting to their defaults with each upgrade.
 +
 +
 +**To create a custom package name**:
 +  - On the **Configuration ** tab, select **Register Packages**.
 +  - In the **Package Name ** field, enter the custom package name.
 +  - Click the **+** button.
 +  - Click the **Save ** button.
 +===== Creating a Brand =====
 +
 +
 +**To create a new client brand for a supported platform: ** 
 +  - Log in to the Open Mobile Portal, and select the **Configuration** tab.
 +  - Click **Manage Brands**, and then click **Create Brand.**
 +  - On the **Create a Brand** tab, enter values for the following:
 +    * In **Brand Name**, enter a new brand name.
 +    * For **Platform**,​ select //​Android//​.
 +    * If **Class **   is shown, select a class from the dropdown.
 +    * After **Software Version**, select the software version from the dropdown.
 +    * If **Package Name **   is shown, select a package name from the dropdown.
 +  - Select the branding tabs as needed to enter your desired branding elements. The Image Map interactively displays the components of the user interface, as you change them, so you can preview your brand before you save it.
 +  - When the brand is complete, click **Save**.
 +
 +<note important>​Once created, you can publish the brand so that you can include it in your client profiles.</​note>​
 +
 +===== Editing a Brand =====
 +
 +**To edit an existing client brand:**
 +  - Under** List of Brands**, select the brand you wish to edit.
 +  - In the **Actions **   ​column,​ click **Manage**.
 +  - Enter the requested text strings, or upload the requested files.
 +  - When complete, click **Save**.
 +
 +<note important>​A published brand may not be edited.</​note>​
 +
 +===== Publishing a Brand =====
 +
 +A published brand can be included in profiles, and can be shared with your child accounts. A published brand may not be edited.
 +
 +**To publish a brand: ** 
 +  - Create a brand (see above).
 +  - From the **List of Brands**, select the brand you wish to publish. Then, in the **Actions **   ​column,​ click **Publish**.
 +  - On the **Publish Client Brand **   page, click **Publish**,​ and then click //Yes //   to confirm publication.
 +
 +===== Sharing a Client Brand =====
 +
 +
 +Once a brand is published, it can be shared with your child accounts. These accounts will be able to include the brand in their own client profiles. (You can only share a brand one level down—that is, with your immediate child accounts.)
 +
 +
 +**To make a brand shareable: ** 
 +  - On the List of Brands, select the published brand you wish to share. Then, in the **Actions **   ​column,​ click **Share**.
 +  - On the **Share Client Brand **   ​dialog,​ select the direct child accounts with which you wish to share the brand.
 +  - Click **Share**, and then click //Yes //   to confirm sharing.
 +
 +
 +===== Applying the Brand to a Profile =====
 +
 +Once you have created and published a brand, you can apply it to a profile.
 +
 +**To apply a brand and styling to a supported client: **
 +  - Go to the **Configuration** tab and select **Manage Profiles**.
 +  - Choose the appropriate profile and select **Manage** under the Actions column.
 +  - Under Client Look and Feel, click on **Configure**.
 +  - In the Select a Brand drop-down menu, select the appropriate brand. ​
 +  - Click **Save** > **Publish to Test**.
 +
 +===Version Name/​Code===
 +
 +If you choose a package name other than **com.iPass.OpenMobile**,​ you will be prompted to enter a:
 +
 +  * **Version Name**: Any name is acceptable in this field.  ​
 +  * **Version Code** Please use a small digit that can increase incrementally every time a new APK is published.
 +
 +<note warning>​Please do not enter a date in the **Version Code** field. </​note>​
 +
 +
 +  ​
 +===== Distribution =====
 +
 +Branded clients have to be distributed using a private installer created in the Open Mobile Portal, and if the branding has changed, the private installer has to be redistributed (a profile update and migration will not generate the branding changes).
 +
 +===== Upgrading from a Previous Version =====
 +
 +There are two upgrade scenarios:
 +    * If the default package name is used, software upgrades are managed through the Android Market and users will be notified when a new software version is available.
 +    * If a custom package name is used, software upgrades are controlled by the Administrator,​ who will have to redistribute the software (the private installer available on the Open Mobile Portal) with each upgrade.
 +
 +Go to: **[[android_help|Open Mobile for Android]]**
 +
 +{{tag>​branding android}}
 +
 +
  
 

©2015 iPass Inc. All rights reserved. Terms of Use