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

Receiving URL commands in your own app

Now that we've configured our application with a URL scheme, it's time to add some code that can detect the app being launched from the URL and parse the commands so that we can act and execute commands issued via the URL.

How to do it…

If you're using Alloy, the following code examples can go into the alloy.js file. Otherwise, add them to your app.js file.

The way we can find out the arguments passed to the app upon launch from a URL is by using the Ti.App.getArguments method. This returns an object that has two properties we're interested in, source and url. These respectively tell us the identifier of the app that invoked the URL and the URL itself, including any parameters.

Firstly, we need to add some code to handle the detection of the URL when the app is launched or resumed, so add the following lines at the bottom of your app.js or alloy.js file:

var checkURLArgs = function() {
    var args = Ti.App.getArguments();

    if (args.url) {