Trigger.io Blog

I get where you're coming from. As a web developer I'm all for the web in general. I suppose my frustration stems from how an evaluation of a new web framework leads to a frustrating back and forth on native vs. web. It's a hot topic. I'm currently working on my first iOS app (yes I know I'm late to the game) using Trigger.io: https://trigger.io/ Still working my way through the documentation but so far it's amazing. Consider having a look. EDIT: Hello from Auckland :)

I agreed that writing app in HTML5/CSS/JS is easy to mantain. But why not get access to those native features too? Hybrid apps seem to be very logical way to build apps now. Take a look at many emerging services like http://trigger.io and get the best of both world.

There's a few different solutions around. I believe one of them (https://trigger.io/) is even YC funded.

I've been building hybrid apps (HTML/CSS/Javascript) for quite some time now. It's getting better and better, and there are quite a few resources available. Just follow these simple steps: - Get Apache Cordova (https://cordova.apache.org/) - Try Ionic Framework (http://ionicframework.com/) - Try Ratchet (http://goratchet.com/) - jQuery Mobile, obviously (http://jquerymobile.com/) - If you need more help, try Codiqa (https://codiqa.com/) - Try Trigger.io (http://trigger.io) Cordova makes it super simple to deploy to app stores, and it's awesome. I make mobile apps all the time. Though not as good as native, it certainly has been improving, especially in the recent years.

And now their website, http://trigger.io, is also not working. Just takes forever then returns a message saying "Sorry, there has been an error".

We use a true hybrid approach for the mobile app, meaning in addition to using phonegap we also use some native UI elements; namely the top and bottom nav bars. It does add some overhead because you have to write that stuff in java/objective-c but it helps the app feel much closer to a native app than pure HTML5 does at this point. I would check out http://trigger.io if you're not interested in writing any native code and don't have any special requirements for your UI design. Our backend is a ruby on rails app.

We'll add more case studies and user comments to our homepage, but in the meantime we've blogged about some examples: Hojoki (my favorite): http://trigger.io/cross-platform-application-development-blog/2012/08/… Wine Box: http://trigger.io/cross-platform-application-development-blog/2012/05/… Need An Accountant: http://trigger.io/cross-platform-application-development-blog/2012/05/…

What version of IE? Looks OK for me on IE9 (and IE7/8 mode)... Can you get to our main site https://trigger.io/ ?

Irony: I'm a new Ruby developer spending a lot of time in the Rubysphere and have never heard of your company before. But I can tell you how I've heard of most products, services and companies that have turned me into a user or potential user. 1. Blog posts celebrating the way your product makes 'x' way easier and/or faster and/or better than the way I'm used to. See http://trigger.io/cross-platform-application-development-blog/ 2. Blog posts/guest blog posts/screencasts by your users showing how your product makes them awesome at doing 'x'. You could aim high (Railscasts) or target a growing niche (Spree users, etc.) - though you want to be careful not to push this too hard. The best recommendations will be totally organic, but you can nudge things by mentioning developers/apps on your own blog, etc. 3. Blog posts by partners (e.g. Sendgrid talking about their Heroku integration). I didn't mean for all my points to be calls for blog posts, but I guess there's a lesson in there. Use your blog to SHOW what you and your users are doing and you're on the right track. I'm not even sure this is marketing - more like developer outreach. But I'm assuming the goal of your marketing is more developers using your platform.

AppHub co-founder here, we realize that this is something that would seem to be prohibited by Apple, but updating JavaScript code is explicitly permitted by the iOS Developer Agreement [1]. This same technology is used by Meteor [2], Trigger.io [3], and Adobe Hydration [4], and also used by Facebook and Palantir [5] in their apps. [1] https://developer.apple.com/programs/ios/information/iOS_Program_Infor… [2] http://info.meteor.com/blog/apple-hot-code-push-mobile [3] https://trigger.io/ [4] http://docs.build.phonegap.com/en_US/tools_hydration.md.html [5] https://medium.com/@clayallsopp/a-dynamic-crazy-native-mobile-future-p…

trigger.io claim it is possible for their apps on Android 4.4 [1] that uses Chromium as basis for the webview, but I didn't have the chance yet as I am still on 4.3. [1] http://trigger.io/cross-platform-application-development-blog/2013/11/…

The last example on: https://trigger.io/examples/ has a quote from a previous example. Both are from the CTO of Famium. Just a heads up.

Trigger.io rocks. On top of mobile app development, they also help with browser add-ons. Check out what they allow for the zemanta add-on - http://trigger.io/cross-platform-application-development-blog/2012/07/…

We did something similar in Barcelona earlier this year: http://trigger.io/cross-platform-application-development-blog/2012/06/… Money well spent!

Prior art: https://trigger.io/reload/ https://build.phonegap.com/docs/hydration Plus every app that has ever had to solve this problem. There is nothing non-obvious in this patent.

There are a few good options for debugging. Trigger has the Catalyst debugging tool which brings a Webkit-style debugging interface to mobile development (https://trigger.io/catalyst/). You can run apps in the simulator and on connected devices then remotely view the DOM and debug Javascript in the web interface. 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 [email protected].

We totally agree that when things have a solid foundation it makes sense to build on top of them. The problem we saw with Phonegap was several design decisions we disagreed with (as we described briefly in the blog post). This left us with the option of putting up with it (and ending up with an inferior product), or writing our own bridge, and writing our own bridge made sense. Of course you are right in that writing anything new means you have to work hard to get it to as high a standard as the alternatives, which is why we work hard to test our platform - see http://trigger.io/cross-platform-application-development-blog/2012/01/… It's also important to remember that the native bridge is just one part of our product, we also write the code that generates and builds the app, which we want to integrate as tightly as possible. Writing our own bridge makes this a lot easier to do well.