Book Image

Appcelerator Titanium Smartphone App Development Cookbook

By : Boydlee Pollentine, Jason Kneen, Jason Kneen
Book Image

Appcelerator Titanium Smartphone App Development Cookbook

By: Boydlee Pollentine, Jason Kneen, Jason Kneen

Overview of this book

This book will take you through the process of building cross-platform, native UI applications for the mobile from scratch. You will learn how to develop apps, how to use GPS, cameras and photos and how to build socially connected apps. You will also learn how to package them for submission to the App Store and Google Play. This cookbook takes a pragmatic approach to creating applications in JavaScript from putting together basic UIs, to handling events and implementation of third party services such as Twitter, Facebook and Push notifications. The book shows you how to integrate datasources and server APIs, and how to use local databases. The topics covered will guide you to use Appcelerator Studio tools for all the mobile features such as Geolocation, Accelerometer, animation and more. You’ll also learn about Alloy, the Appcelerator MVC framework for rapid app development, and how to transfer data between applications using URLSchemes, enabling other developers to access and launch specific parts of your app. Finally, you will learn how to register developer accounts and publish your very own applications on the App Store and Google Play.
Table of Contents (21 chapters)
Appcelerator Titanium Smartphone App Development Cookbook Second Edition
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Integrating data using models and collections


A key part of many applications that you might create is data. For a contact app, this could be a list of contact details; for a newsreader, it could be a list of articles; and for a task app, it could be a list of tasks.

In Alloy, data can be integrated into your application using Collections and Models. If you're familiar with backbone.js, you may well have used Collections and Models already. If you haven't, note that a Model is a data object. In this case, it could be a single task item, so it could consist of a description and a status (complete or not). A collection is a list of models, in this case a list of tasks.

Because models and collections are event-driven, they respond to changes as they happen. This means that as you change a model, say its status being changed to completed, the change is instantly reflected in the model and any collection that contains it.

How to do it…

The first thing you need to do is create a simple user interface...