Create a new project

To start, you'll create a new Alloy project in Studio.

To create a new Alloy project:

In Studio, select File > New > Mobile App Project.

Select the Default Alloy Project type and click Next.

On the Project Location screen, enter FaveBooks for the Project name and com.your- domain.favebooks. Replace your-domain with your personal or organization's domain. Leave the other fields at their default values.

Click OK.

The new project opens in Studio.

Create the data model

The heart of the FaveBooks app is the data containing the user’s books, so we’ll start by defining our data model. Alloy uses Backbone to provide its data modeling and collection features.

To create the data model:

Right-click or Control-click on the top-level project folder and select New > Alloy Model, or press Cmd+Shift+M (Mac) or Ctrl+Shift+M (Windows).

In the New Model dialog, make the following entries:

For Model name, enter books.

Select sql from the Adapter menu.

In the Schema table, add two fields named title and author and set their types to text.

Click OK.

This creates a new file in the app/models directory called books.js. This file describes the data model you just created. The config section, in particular, defines the data columns, adapter type, and collection name.

Initialize the book collection

Next you'll write code that creates a Collection from the model definition, creates a single book, and saves it to device storage. Eventually you will add features to let users add books, but for now this will give us some data to work with.

To initialize the book collection:

Open controllers/index.js and delete the doClick() function definition added by the project wizard.

Get a reference to our collection:

Create a new model object (book) and assign it a title and author:

Add the book to the collection and persist it to the database.

Save your changes to index.js.

Now that our application has some data, let’s display it in a table.

Add a TableView

In Alloy, collection data can be synchronized to a view object, or a single model can be bound to a view component. At runtime, Alloy monitors your application's collections for changes and updates any synchronized view objects with the new data. Specifically, the Backbone add, change, destroy, fetch, remove, and reset events are monitored for changes. In this case, each time we call the add() method on the myBooks collection the view is synchronized with the new data.

Open views/index.xml.

Delete the <Label>element that was generated by the project wizard and add a <TableView>element in its place.

Insert a <TableViewRow>element inside the <TableView> element, as shown below:

The <TableViewRow> element will be repeated for each element in our data set.

Add a <Collection>element to the top-level <Alloy> element and set its srcproperty to books. This corresponds to the name of the collection we created before.

To synchronize the collection with the view, assign booksto the TableView element's dataCollectionattribute.

Using curly-bracket syntax, assign the title from each book (that is, each model in the collection) to the title attribute of the <TableViewRow>. The final contents of index.xml should look like the following:

Open styles/index.tss.

By default, Android applications built with Titanium use the AppCompat theme, which uses a dark background with light text, while iOS defaults to black text and a black background. In order to see text, change the background to white for iOS only by adding the platform attribute to the container rule.

At this point we’re now ready to test our app. For comparison, we’ll run the app in both an iPhone simulator and an Android emulator.

To launch the app in the iPhone simulator:

From the Target menu in the top-right corner of Studio, select iOS Simulator > iPhone. By default, Studio is configured to automatically launch when you select a target platform. Wait for the app to complete launching in the simulator.

To launch the app in an Android emulator

When the application has finished launching in the iPhone simulator, select Android Emulator > titanium_1_WVGA800 to launch the app.

The titanium_1_WVGA800 string corresponds to the name of the Android virtual device that Studio creates by default. If you have installed other AVDs, you can select one of those.

The screenshots below show the app running on an iPhone simulator and an Android emulator. As you can see, the table is populated with the book from the collection.

Note the following:

On iPhone the top of the TableView is partly obscured by the iOS status bar. We’ll fix this later in this tutorial.

On the Android, the book is hidden under the app label. We'll fix this later in this tutorial.

The table length increases by a row each time you launch the app, since we are saving the (same) book to each time.

Android troubleshooting

The initial launch of the Android emulator can be quite slow and Studio may timeout before it can install and launch the application. If this happens just click Run in Studio again. Subsequent launches should not time out on the same virtual device.

Create a book detail view

Next you’ll add functionality to let the user select a book and view its details (title and author). To do this you’ll create a new Alloy controller. An Alloy controller is actually a logical collection of three parts:

In the New Controller dialog, enter bookdetails in the Controller name text field, and click OK. This creates the following new files:

controllers/bookdetails.js – The controller’s JavaScript controller.

views/bookdetails.xml – The controller’s view

styles/bookdetails.tss – Styles for the controller

Open views/bookdetails.xml in the editor.

Replace the <View> element with a <Window> element:

Add two <Label> elements to the <Window> element. Give the first one an ID of titleLabel and the other an ID of authorLabel, as shown below.

Open styles/bookdetails.tss and a background color for iOS to the .container rule:

Next we’ll add an event handler to the <TableView> that opens this new window and displays the book's information.

Display book details view on selection

To respond to user selection, you add an onClick attribute to the <TableView> element, and assign it the name of the function to invoke. The function creates a new instance of the bookdetails Alloy controller, passing it the title and author of the selected book, so it can display those values in the <Label> elements you defined there.

To display the book details screen on selection:

In the Project Navigator, open views/index.xml.

Add an onClickattribute to the <TableView> element and set its value to showBook.

Open controllers/index.js and add a function named showBook()that takes a single argument called event. This is the event object passed to the function that contains information about the selected item.

First, let’s add code to extract the title and author of the selected book from the event.source object.

Lastly, we create a new instance of the Alloy bookdetails controller, passing it the args object containing the title and author data, and open the view.

Lastly, we need to update bookdetails.js to display the title and author values passed to the createController() method, or display a default title and author if none were provided:

Save your changes.

Launch the app in the iPhone simulator or Android emulator. Select a book from the list to open the detail screen. You should see something like the following:

Clearly, this isn’t what we want – the two labels are occupying at the same space on screen. Next we'll modify the layout and styles of the book detail screen to fix this.

Modify the book detail layout

Titanium supports three layout modes: composite (or absolute), vertical, and horizontal. In composite mode, you specify a child view's coordinates on a grid relative to its parent container's top/left or bottom/right corner. If not specified, a child view is centered on the display. In this section you'll apply a vertical layout to the book details view, and then tweak the style.

Open views/bookdetails.xml.

Wrap the two <Label> elements within a <View> element, as shown below.

Add a layoutattribute to the <View> element and set its value to vertical.

Open styles/bookdetails.tss and add the following style rules to align the labels along the left side of the screen, and to set their font sizes. We also add some padding between the two labels by 10.

Also, we want to ensure that the labels aren't overlapped by the app's name and that the background of the main view doesn't use a white background with white text by adding the following to styles/index.tss:

Save your changes and build again for iPhone or Android. The title and author should now be positioned vertically within the view, and aligned to the left side of the screen. To get back to the original table, you can click the Back button on Android.

On iOS, the application is stuck here. Instructions on adding an iOS navigation controller is detailed in a later section of this tutorial.

Add platform-specific styles to the TableView

If you test the app on an Android device with a high-resolution display, you’ll notice that the default height of each table row is a bit small to comfortably read or select with a finger. For instance, the screenshot below was taken with a Pixel 2 emulator.

To fix this we will apply a platform-specific style to the <TableViewRow> element. During the build process, platform-specific styles are applied only to builds on the target platform. The following is an example of a platform-specific style that makes all Labels blue in iOS builds.

In this case we’ll increase the font size used by each <TableViewRow> element, and set the height of each row to provide some space around the text.

To increase the table row height on Android:

Open views/index.tss and add the following style rule to the end of the document:

Save your changes and build the application for Android. The TableView should look like the following screenshot:

Add a NavigationWindow for iOS

Unlike Android, iOS devices do not provide a physical back button for navigation. The NavigationWindowis an iOS-only UI control that provides an easy way to display and navigate hierarchical content. (In native iOS terms, the control is an implementation of the iOS navigation controller interface.) On Android, you get this type of navigation for "free". The NavigationWindow will wrap the original <Window> element and provide a title bar above the <TableView> control, solving this layout issue.

To do this we'll take advantage of an Alloy feature called platform-specific resources that lets you define platform-specific view, controller, and style files. At build time, only those resources specific to the target platform are included. There are two parts to this:

Creating a new iOS-specific entry point (a new version of index.xml) that includes the NavigationWindow element

Updating the controller code to handle the difference between the iOS and Android implementations. In this case we'll use platform-conditional code to handle the cross-platform code differences.

To create the iOS-specific view with a NavigationController:

In Project Explorer, create a new folder named ios in the app/views folder. Right-click on the FaveBooks project in the Project Explorer and select New > Folder. The New Folder wizard will allow you to navigate the project directories, select the parent folder, and name the new folder. Once you've done this, click Finish.

Create a new file named index.xml in the new folder.

Copy the contents of views/index.xmlto views/ios/index.xml.

Wrap the existing <Window> element with a <NavigationWindow>element:

Save your changes.

The NavigationWindow control has a different API than Window, so our code now needs to account for those differences. We could create a platform specific controller folder for iOS (controllers/ios/index.js), but the code differences are small enough that we’ll use platform-conditional code to include the proper code for each platform.

To update the controller code for platform differences:

Open controllers/index.js.

Modify the showBook() method to account for the platform differences when opening the details view. On iOS, you now need to open the book details view using the NavigationWindow object's openWindow() method:

As you can see, in the iOS case the handler now opens the window inside the NavigationGroup; the Android code branch uses the same code to open the window (addview.open()).

Save your changes and test again on an iPhone device or simulator.

The first screen should now display the TableView within the NavigationWindow.

Allow user to add books

Of course, we need a way for users to add their own books. Like we did for the book details view, we will create a new Alloy controller composed of three files: the XML view, the JavaScript controller, and the TSS styles file.

The UI will contain two input text fields where the user enters the book title and author, and a "Add" button to update the books collection with the new data. To take advantage of native UI components familiar to iOS and Android users, we'll use a Toolbar component on iOS and a Menu component on Android to contain the "Add" button.

To create the add book feature:

In the Project Explorer, right-click on the project folder and select New > Alloy Controller.

In the New Controller dialog, give the controller the name addbook. Click OK.

Open views/addbook.xml and add the following markup:

This creates input text fields where the user will enter the book title and author, and a button to add the new book to the collection. The button’s onClick handler will call the insertBook() function, which you’ll create next.

Open styles/addbook.tss and add the following styling:

Open controllers/addbook.js, remove the existing code in that file and add the following:

Define a new function named addBook() with the following code:

For iOS, open views/ios/index.xml and insert a <Toolbar>inside the <Window> element below the <TableView> element:

For Android, open views/index.xml and add the following <Menu>and <MenuItem>elements below the <TableView> element. Note: we cannot add specific node text to the menu item. Instead, we'll use attributes of <MenuItem>element to accomplish this:

Open controllers/index.js and add the following code to open the addbook controller when the appropriate native control is used. For Android, depending on the device, the Add button can either be accessed from the Action Bar at the top of the display or by using the Menu button. For iOS, use the toolbar at the bottom of the screen.

Save your changes and test on a device or emulator.

You should now be able to click 'Add' and add new books to the collection which persist between sessions.

Next steps

Review the guides in Alloy Framework to learn more about using Alloy to build your application; specifically, see the Alloy Views section to learn about creating the UI for your application. Also, review the Titanium SDK guides to learn more about specific categories of APIs, such as UI, media, geolocation, and so on.