[DavidPP]

I did a proof of concept with Trigger and I must say that it's a pleasure to work with. But in the end, we still decided to go with Phonegap because of two issues :

1) What happen if Trigger.io close their door? 2) Ability to add native features if required

From what I'm reading, #2 is not an issue anymore, but what about #1 ? I understand that for any commercial product, but usually, if a company close their door, you can still use the product (but without any update). What about Trigger? Would all my apps developed with it still work after they shutdown?

[amirnathoo]

There are no run-time dependencies on Trigger.io servers except for using our Reload feature that allows you to push updates to your live app code: https://trigger.io/reload

=> Your apps keep working for end-users even if our servers disappear

We're backed by top-tier angel investors and value our own reputations which protects you when it comes to 1. That said, we do have some more upcoming announcements that will hopefully do more to assuage those concerns.

[DavidPP]

Ok thanks for the clarification, that exactly what I meant. I can live with the fact that I have a small risk of having to rewrite my apps if needed if there is no runtime dependencies on your server.

I'm pretty sure that I tried to find that info on your website and couldn't. Maybe you could explain this somewhere in your FAQ ?

[enjo]

For me it's subscription pricing. It's expensive and I'm not really sure what it provides that PhoneGap does not.

[amirnathoo]

We provide native UI components and Facebook SDK integration out of the box.

Our customers tell us they value our super fast and simple build / test cycle and Reload feature: https://trigger.io/reload

You can develop for free.

When you want to package for launch or build with a premium modules, you need to pay at least for that month. You can downgrade at any time.