We launched our Forge platform in January last year. We’re immensely proud of it. Nevertheless, many things have changed since then as we’ve iterated fast with new releases week after week.
Our goal is the same: to provide web developers with the best framework for developing mobile apps across multiple platforms.
There’s a huge shift to mobile underway right now and we’re really only at the start. Ranking #1 for a search for “phonegap done right” and #4 for “mobile development platform” with our article on how to understand mobile platforms we want to enable web developers to make the transition with helpful content as well as our platform.
If you haven’t already check out Trigger.io Forge to see how it can accelerate your app plans by letting you re-use your HTML / CSS / JS skills and code for your mobile apps for iPhone, iPad, Android or mobile web.
It’s been a while since I updated you on our build stats – you can see how they looked last summer. Compare that to now:
We’re pretty happy with that strong growth – 10x since March last year. More developers are more engaged than ever in our platform – you can see examples of what they’ve created on our site.
Our customers range from companies building apps for themselves, through contract web developers and studios to product companies that are building many templated apps for industry verticals.
With a stable core team of developers, we’ve been getting more and more productive at responding to your feedback and improving our product. At launch we were confident that our build / test cycle was far faster and simpler than the main hybrid app alternatives – PhoneGap and Appcelerator.
With the improvements we’ve made over the year, we’re now not only confident that our platform is the fastest and simplest to develop with, but it also allows you to achieve the best results. Basically it is the best mobile app platform out there. Don’t take our word for it, try it for yourself.
A huge part of that is Reload – the ability to push updates to your app contents and logic without needing to resubmit to the App Store.
We kicked off this feature during our away trip in Barcelona, and since launching it’s become one of the main reasons devs choose Trigger.io.
This is a unique feature amongst mobile platforms. It’s not possible to download and execute remote code with natively developed apps. Other hybrid mobile platforms let you reference remote HTML / CSS / JS but that doesn’t help if the user is offline and you’d have to write your own caching and synching logic.
Reload productizes all of that and gives you both offline performance and fast updates when network is available.
Native UI components
Using pure HTML5 for your front-end and Forge APIs to access native features is great for many cases, especially with emerging UI libraries like Lungo making this simpler than ever when used with Trigger.io.
But on mobile there’s sometimes no good substitute for real native UI. Can you have the best of both worlds? We think so and we have made native UI components available starting with the native topbar and tabbar:
We continued with native alert and confirm dialogs, including Android toasts, in our notification module and native date / time pickers. More are on their way.
Standalone build API
For our customers who build large numbers of apps, sometimes based off common templates, having a slick update process and native UI isn’t enough: automation is a must.
You wanted to be able automate your builds, testing, parameterize your apps, and even let your end-users create their own apps on your site.
To deliver the best mobile platform for these requirements we launched a standalone build API so you can automatically trigger builds directly without going through our Toolkit.
We didn’t stop there – pre and post build hooks together with our parameters module enable further automation.
While our customer value the ability to build native apps without needing to write native code, some of the time there’s no option but to drop down into native code to get that last 10% of differentiation, quality and functionality.
To that end we’ve made the platform plug-able and launched our native plugins beta last year.
Plugin development is now enabled by default on all of our plans and we expect to take the ‘beta’ label off soon.
In summary: Trigger 2.0!
Breadth of APIs is our #1 priority right now so you can access a wide variety of device features to differentiate your app. To that end we went to Berlin on an away trip in February and hammered out a major set of changes to enable that. You’ll see the results of that work in the product soon.
Don’t worry though – we’re concerned about backwards compatibility and Trigger 2.0 is not a re-write or pivot, it will build on the existing product. Some of our customers have called Trigger.io “PhoneGap done right”. We hope you’ll be able to think of Trigger 2.0 as “Trigger.io as we know it, but now even more awesome”.
As always stay in touch with us at firstname.lastname@example.org, we’re eager to hear from you.