From a cursory glance, it seems like it should be easy enough to use. Though I have a question. What happens on errors? One of my big frustrations from before was that underlying iOS errors would bubble up and I'd spend hours digging around in iOS, trying to figure out what the error really was talking about. It required an understanding of how iOS/Android apps were put together.
After playing with Trigger (or Forge is the actual product) I was rather disappointed.
somethings I've observed: 1) Forge is NOT free - You have to pay $50 A MONTH to remove their branding. Which is a big splash screen that is shown for about 3 seconds when the app is launched. This producing a terrible waiting period (not sure if they are doing work in the bg) but it defiantly doesn't feel as snappy as it could. Am I'm not paying $50 to find out.
2) I saw nothing that supports their claim 5x performance than phonegap. I've built a fair share of native and web wrapper apps. If anything it was a little laggy'er.
3) It's early in its life, many features are actually not cross platform. Many things only working in android or iOS.
I;m still sticking with phonegap. It's a way more mature system. And its Fee.
Trigger can also generate web apps (http://current-docs.trigger.io/web/index.html), so when not using native phone functionality (e.g. the camera) you might like to debug with a web app and use Chrome/Firefox developer tools in your desktop browser.
With liberal use of forge.logging (http://current-docs.trigger.io/api/logging.html) these techniques should be useful! I think you'll find things have progressed since you last used cross-platform frameworks. Any questions do drop us a line on support@trigger.io.
