I’ve written mobile apps in the past, but only simple toys like an RSS reader, a Tamagotchi, and an app that tells you how much your meeting has cost. I enjoy Java, but I found writing these Android apps laborious and finicky, particularly using the cumbersome (although powerful) hulk that is Eclipse. I was recently tinkering in jQuery mobile which was great for rapid development, but how to get the resulting app onto a device? I asked around the Box UK office, and perennial tinkerer Steve Anderson made the suggestion of Trigger.io, so I gave it a go!
What is it?
Getting to grips
After a signup stage on the Trigger.io site (yes, you need an account, but free ones are available), it installed no problem at all, it just runs as a Python script through a single command which kicks off a web-based tool called Forge:
Starting Trigger.io from the console
It opened the web server in Chrome automatically:
Home screen of Trigger.io running on my laptop
Clicking “create” simply showed me a dialog and all I had to enter was my app name and it set up a skeleton project for me.
Creating a new app
It then went on to a “preparing your app” screen. Occasionally, at this point, an error would be raised – it seems that Forge does a lot of pulling code and templates from servers to get you the latest project template. I found that on the rare occasions that happened, running it again sorted the problem. My home broadband is pretty sketchy at the best of times so I gave Forge the benefit of the doubt.
From there, I had the option to run my app, or even package it up for distribution – this really is great, such a simple workflow to be able to just use a web browser for this stuff! I deployed to Android. There was a slight hiccup whereby I had to tell it where the SDK was, and I had to do that on a per-project level, which seems a bit clumsy (I’d like to set a global default), but that was just a case of editing local-config.json in my project root.
Uh oh, better tell local-config.json where the ‘Droid SDK is…
Once that was done, I just hit “run again”, then it asked me for a device, I selected “Attempt to automatically launch the Android emulator” and in a matter of flipping ages the emulator was up and running!
(The delay is not Trigger.io’s fault – the ‘Droid emulator is full emulation, rather than a simulator like in the iOS ecosystem, and it tends to take a while to start up first time. My bro tip is not to stop the emulator once it’s running, just redeploy your app.)
Sample app, up and running
Soft Paws running in Chrome
The only library I used was hammer.js, a jQuery plugin that does a fantastic job of recognising touch screen input (that’s for another blog post, though!). I got pretty excited when I started setting the icons for the game to be pictures of my girlfriend’s cat, but then I hit my first major snag: no sound support. I found a post on Stack Overflow where a Trigger.io developer suggested that sound support is on the roadmap, but low priority at the moment. I mentioned this on Twitter and Amir from Trigger.io got in touch with me directly and made some good suggestions and I eventually got sound working – albeit as a workaround using the video tag, and it has some lag on the sound. The support I received was excellent, which gives me a great deal of confidence in TriggerCorp.
The lack of sound support means this tool isn’t ideal for games development at the time of writing. This is a shame as for very simple games, just adding sound would make this a good platform for hobbyists like myself who don’t want to spend hundreds of hours building games in Java.
Kitty enjoying Soft Paws
For a game, a super slick and polished app, or something really specific, you may prefer to build natively rather than use a tool like this. Overall, though, this seems to be a great product for rapid cross-platform development, particularly when paired with something like jQuery mobile. It is highly useful for prototyping and mockups to mobile to get a better experience than just a web browser and to provide offline support. Products like Trigger.io have significantly lowered the barrier of entry to mobile device development; I can see many smaller companies being able to get much better quality apps, much cheaper, because of this tool. Being able to cross-compile to multiple devices from a single source file is potentially incredibly useful, although inevitably there will be edge cases. I’d strongly recommend having a look and seeing if it works for you, and if you’ve already experimented with it, let us know what you think using the comment box below.
Want to see more?
Want to find out more about the tools our dev community have been exploring? Take a look at our regular tech round-up series - and sign up to our mailing list to have them delivered direct to your inbox.