Book Image

Appcelerator Titanium Smartphone App Development Cookbook Second Edition

Book Image

Appcelerator Titanium Smartphone App Development Cookbook Second Edition

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
About the Author
About the Reviewers

When should you use app properties?

Application properties should be used when one or more of the following are true:

  • The data consists of simple key/value pairs

  • The data is related to the application rather than the user

  • The data does not require other data in order to be meaningful or useful

  • There needs to be only one version of the data stored at any one time

For example, storing a string/string key pair of api_url and would be a valid way of using app properties. This URL could be reused across all your application screens or windows and would be related to your application, rather than your data.

If your data is complex and needs to be joined, ordered, or queried while you are retrieving it, then you are better off using a local database built with SQLite. If your data is a file or a large blob object (for example, an image), then it is better stored on the filesystem.

What object types can be stored as app properties?

There are currently six distinct types...