New feature roundup: native date / time picker, analytics with Flurry, Android events

Trigger.io is about using the best of native and HTML5 to build amazing apps like these ones, and iterate them fast. So we’re delighted to announce native date / time picker enhancement on Android amongst other improvements.

While we’ve released Native Plugins and Windows Phone 8 as major new features in the past couple of months, we’ve also quickly iterated the core platform and here, we’ll walk you through a few of the new modules we’ve added. If you like what you see, check out the awesome apps our customers are building and sign-up now to build for yourself!

Native date / time picker

Accepting date / time input using regular HTML5 is simple, and on iOS it looks great since the native picker is triggered automatically when you click on the form element.

<p>Birthday (date and time):</p>
<form>
	<input type="datetime" name="bdaytime">
	<button>Submit</button>
</form>

But on Android, not so much…

But now, enabling a native date / time picker on Android is as simple as enabling our new native ui module and using the JavaScript API once your HTML has rendered:

forge.ui.enhanceAllInputs();

See the difference on Android:

Analytics with Flurry

Many of you have asked for an analytics solution and we’ve added the first of these by integrating the Flurry SDK. Use the Trigger.io module for Flurry by simply enabling the module and using the JavaScript API where needed.

Just by enabling the module, simple information such as sessions, active users and new users – will be available in your Flurry dashboard. With the API you can send custom and timed events to really get to grips with how users are using your apps. Let our integration with Flurry handle all the offline caching and synching. Just register the events with the API and forget about it until you visit your dashboard.

Android events

The back button on Android works fine with Trigger.io apps – use a library such as backbone.js and it’s support for pushState / hash-based URL fragments for history.

But sometimes you want finer grain control, such as exiting the app after a certain number of back button touches. Or intercepting it to change the default behavior. To enable that we’ve added two new event APIs:

forge.event.backPressed.preventDefault(function() {

	forge.logging.log('Success preventing default back button action');

}, function(content){

	forge.logging.log('Error: '+ content);

});

forge.event.backPressed.addListener(function(closeApplication) {

	//Close application instead of navigating back in webview history
	closeApplication();

});

That’s it for now…

Sign up now to take advantage of these new features or get in touch with us at anytime at support@trigger.io