Titanium 3.X
Alloy Styles and Themes

Alloy Styles and Themes

Titanium Style Sheets

The Titanium Style Sheets (TSS) file uses a JSON-like syntax to define the styling elements. All style attributes are the properties of the Titanium object. For instance, when defining the style for a button object, the TSS file can set the style of the backgroundDisabledColor, backgroundFocusedColor, backgroundSelectedColor, etc.

Styles are defined at three different levels: markup element, class attribute (prefixed with .) and the id attribute (prefixed with #). When mixed together, the id attribute overrides the class attribute, which overrides the markup element.

The following code defines a style sheet (index.tss):

// This is applied to any element with the class attribute assigned to "container" 
".container": {
// This is applied to all Labels in the view
"Label": {
        width: Ti.UI.SIZE,
        height: Ti.UI.SIZE,
        color: "#000" /* black */
// This is only applied to an element with the id attribute assigned to "label"
"#label": {
        color: "#999" /* gray */

which pairs to this view markup (index.xml):

    <Window class="container">
        <Label id="label" onClick="doClick">Hello, World</Label>

In the example code above, the label object in the view inherits styles from both 'Label' and '#label'. Since '#label' is defined at the id level, the color of the label will be gray ('#999') instead of black ('#000'). As seen in the TSS code example, you can add single line or multiline comments unlike regular JSON files.

Use the following values and operators in your TSS file:

  • JSON values, that is, Strings, Numbers, Objects, Array, Booleans and null

  • Titanium SDK constants, for example, Ti.UI.SIZE

  • Localization functions, either Ti.Locale.getString() and its shorthand L()

  • Variables from the Alloy.CFG or Alloy.Globals namespaces

  • Bitwise operators, which includes bit shifting ('>>', '<<', and '>>>'), bitwise AND ('&'), bitwise OR ('|') and bitwise XOR ('^')

For example, in the alloy.js file, you can assign some values or functions using either the Alloy.CFG or Alloy.Globals namespaces:

Alloy.CFG.myValue = "#999";
// OR
Alloy.Globals.rotateLeft = Ti.UI.create2DMatrix().rotate(-90);

Then assign these variables in the TSS file:

"Label": {
    color: Alloy.CFG.myValue,
    transform: Alloy.Globals.rotateLeft

Alloy does not support the CSS concept of child or descendent selectors, that is, specifying and applying styles based on the tag hierarchy.

Global Styles

You can create a global style file, called app.tss, which applies all styles defined inside it to all views, but does not override the non-global styles or property attributes in the markup. For example, suppose you have the following three files in your project:

    backgroundColor: 'white',
    layout: 'vertical'
    color: 'gray',
    backgroundColor: 'transparent',
    font: {
        fontSize: '12dp',
        fontStyle: 'normal',
        fontWeight: 'normal'
    backgroundColor: 'blue'
    top: 20,
    left: '25dp',
    right: '25dp'
    width: Ti.UI.FILL,
    font: {
        fontSize: '16dp',
        fontWeight: 'bold'
    <Window titleid="story_title" modal="true" exitOnClose="true">
        <Label id="subtitle" color="orange" textid="story_subtitle" />
        <Label top="25" color="white" textid="story_content" />

By default, every view in the project will have white windows with a vertical layout and gray, left-justified, 12-dp Helvetica labels with a transparent background, as defined by the app.tss file.

However, in the styles defined in the index style file (index.tss) take precedence over the global style file, making the window blue and specifying margin and offset values for all labels in the index view-controller. Additionally, the subtitle ID styles override the styles in the Label element in both index.tss and app.tss.

Finally, any style attribute set in the view XML takes precedence over both the global style and view-specific style files. The orange and white color will be used instead of the gray color specified in global style file, and the larger top offset is used instead of the one set in index.tss.

Platform-Specific Styles

As with views, separate styles may be defined based on the platform (android, blackberry, ios, mobileweb, or tizen) and device size (handheld or tablet) in the Titanium style sheets. The sample style sheet below defines styles for iPhone, iPad, Android and mobile web devices.

// Any device that does not fit any of the below platforms 
"Label": {
    backgroundColor: "#fff",
    text: 'Generic'
// iPhone
"Label[platform=ios formFactor=handheld]": {
    backgroundColor: "#f00",
    text: 'iPhone'
// iPad and iPad mini
"Label[platform=ios formFactor=tablet]": { 
    backgroundColor: "#0f0",
    text: 'iPad'
// Android handheld and tablet devices
"Label[platform=android]": { 
    backgroundColor: "#00f",
    text: 'Android'
// Any Mobile Web platform
"Label[platform=mobileweb]": {
    backgroundColor: "#f0f",
    text: 'Mobile Web'

You can also create subfolders, named as the platform, in the styles directory as another way to create platform-specific styles. Refer to Alloy Concepts: Platform-Specific Resources.


Themes provide a way to change the appearance of an entire GUI, allowing you to customize the styles and assets of the application.

To create a theme, create a folder called themes in your Alloy app directory. In the themes folder, create a folder for your theme. The name of this folder references the name of the theme for configuration and compilation. In your theme folder, create assets and styles folders for your custom images and styles, respectively. The example below creates a theme called 'mytheme'.

  • app

    • assets

      • appicon.png

      • background.png

    • controllers

    • styles

      • index.tss

      • window.tss

    • themes

      • mytheme

        • assets

          • background.png

        • styles

          • app.tss

    • views

      • index.xml

      • window.xml

For assets, all files are overwritten by the copies in the theme's assets folder. In the example, the background.png file in the theme overwrites the file app/assets/background.png, but the app/assets/appicon.png file is used since there is not a similar file in the theme. All asset files are copied to the Titanium project's Resources directory, so all references to assets only need to include the path after the assets folder. The theme's assets folder can have platform- and density-specific folders.

For styles, styles defined in the theme's styles folder merge with and take precedence over the styles defined in app/styles. You can define individual styles per view as well as the global style file app.tss. For example, if a color was specified for a label in the themes/mythemes/app.tss file, this color overwrites the individual style files in app/styles for all labels. However, if a style was defined in one of the individual style files but not in themes/mythemes/app.tss, the styles in app/styles/ are applied. The theme's styles folder can have platform-specific folders.

To use a theme, add it to your config.json configuration file with "theme" as the key and the name of the theme folder as the value. For example:

    "global": {
    "env:development": {}, 
    "env:test": {}, 
    "env:production": {}, 
    "os:ios": {
    "os:android": {
    "dependencies": {}

The theme changes based on the platform. Android uses the 'blue' theme, iOS uses the 'green' theme, and Mobile Web uses the 'mytheme' theme.

Style Priorities

When mixing themes, the global style file, view style files and defining styles inline in the XML markup, Alloy applies the styles in the following order from lowest to highest priority:

Style Defined in the...


Global Style File


Global Style File in a Theme


Global Style File with Platform-Specific Styles

styles/app.tss with the [platform=<platform>] syntax

Global Style File in a Theme with Platform-Specific Styles

themes/<theme_name>/styles/app.tss with the [platform=<platform>] syntax

View-Controller Style File


View-Controller Style File in a Theme


View-Controller Style File in a Theme with Platform-Specific Styles

themes/<theme_name>/styles/<view_controller>.tss with the platform attribute

XML Markup


XML Markup with Platform-Specific Styles

views/<view_controller>.xml with the platform attribute