# Style and Conventions

In this section, we'll examine the Titanium SDK recommended best-practices for coding style, including naming conventions, code formatting, and commenting.

# Language rules

Many references exist that describe JavaScript language rules to follow. We'll lay out a few of the most important here, then direct you to the References section below.

We have codified our set of internal formatting and linting rules for ESLint at our repository: https://github.com/tidev/eslint-config-axway (opens new window)

This is the set of lint rules we apply to our own JavaScript source for any SDK-related NPM packages, CLI code, etc.

# Coding style best practices

# Naming conventions

# Variable and function names

Variable names start with a category noun (lowercase) so that they are easier to categorize and associate with related variables.

Variable examples

personName, personAddress
personNameLast, personNameFirst

Function names follow a similar convention, though we start with a category verb (lowercase) and are often followed by an associated variable name (if any).

Function examples

getPersonName, setPersonAddress
driveCarBlue, stopCarRed

Both variables and functions (or properties and methods, respectively) start with a lowercase word so that they are easier to differentiate from major namespace objects or 'classes'.

⚠️ Warning

Titanium SDK does not support the use of Hungarian Notation.

# Object and 'class' names

Major objects and class-like functions (constructors) follow a standard pattern of capitalized words. Though not necessarily a naming convention, 'class' names that end up rather large is an indicator that the 'class' is most likely designed to do too much. 'Class' names may also start with an abbreviation of a library.


Car, GarbageCollector
IKSystem, MCStyle

# Namespace

Here, convention is similar to 'class' naming.


  • App.UI.Widget

  • App.Network.Request

⚠️ Warning

'app.ui' should be 'App.UI'

# Factories

Factory functions are located within a major namespace object, start with 'create' and return an object.



# Operators

Type data and operators should always be separated by a single space.


var nameFull = nameFirst + nameLast;
for (var i = 0, cl = content.length; i < cl; i++) {}

# Indentation

Both K&R/1TBS and Allman styles are acceptable. Consistency is most important and a combination is not to be used on the same project. Clean indentation is required.

// K&R/1TBS Style
if (x < 10) {
  if (y > 10) {
    // do this
} else {
  // do this
// Allman Style
if (x < 10)
  if (y > 10)
    // do this
  // do this

// but never do this within a function:
  foo: 'bar'

As noted, you should never put return on its own line followed by an object literal definition. Doing so will return an undefined value rather than the object. See this blog post (opens new window) or Crockford's JavaScript: The Good Parts (opens new window) for more info.

# Primitive types

Concatenation Strings concatenated using the + operator must always use a space be added before and after the + operator to improve readability:

var someString = 'My name is ' + firstName + 'and I am a developer';

Primitive type construction Do not use the primitive type object constructors unless you have a very clear reason for doing so.

// Don't do this
var test = new String('My String');

# Control statements

Switch statements have a single space before the opening parenthesis of the conditional statement and also a single space after the closing parenthesis. Switch statement content is indented with one tab. Content in each case is indented one tab as well:

switch (someTest) {
    case 1:

    case 2:


# Comments and documentation

Single-line comments are required to reduce programmer error. However, specialized block commenting is preferred when documenting functions. Inline statement comments should be used at a minimum or not at all.

// Calculate position using initial
// and offset x coordinates.
var finalPos = initPosX + offsetPosX;

 * @param {String} customerName Customer's full name.
function getCustomer(customerName) {}

# References and further reading

# Summary

In this chapter, you learned the Appcelerator recommended best-practices for coding style, including naming conventions, code formatting, and commenting.