amirnathoo

12 ms·

91.
by amirnathoo 15y ago
Ok, I can respond to this, but what about your agreement with the conclusion, and the arguments that you would make to support it? No, I would bet that there are not more developers on Android than iOS right now, and more money is being mad
92.
by amirnathoo 15y ago
> it's just a matter of time Sure. But if you're developing now you have to deal with what you've got - the Instagram founders did not say "we'll wait for this to become standardized".
93.
by amirnathoo 15y ago
The point with Android is that developers will follow what consumers adopt. They'll put up with Android fragmentation in the same way they put up with the App Store approval process - because they have to. Facebook have listed mobile as a
94.
Future of Mobile: a case of HTML5 or iOS… really?(trigger.io)
17 points by amirnathoo 15y ago|11 comments
95.
by amirnathoo 15y ago
"7 bullets vs 3 bullets. PlatformLayer is more than twice as good!" 'nough said. I'm with PlatformLayer.
96.
by amirnathoo 15y ago
If I understand right: instead of having to worry about calling a REST API for a back-end data store I can just have JS objects persist automatically and synchronize between clients. Dropbox for JS objects. If I've got that right, I think t
97.
Faster mobile apps by bundling backend API calls - with Trestle / Trigger.io(trestleapp.com)
20 points by amirnathoo 15y ago|6 comments
98.
by amirnathoo 15y ago
No, users who have already installed the app get the same experience as when they originally downloaded it. And there's nothing automatic in our wrapper that 'calls back' to trigger.io and modifies the user experience based on that. We simp
99.
by amirnathoo 15y ago
Thanks for the feedback. We definitely want to support indie devs, and will add tiers to reflect that soon. Our current pricing is more targeted at enterprises, web dev studies and funded startups.
100.
by amirnathoo 15y ago
If you click through any of these links: https://twitter.com/#!/search/instagr.am You'll be taken to a rich web experience that allows even non-iPhone users to engage and in turn share with friends via Twitter. So Instagram has done both
101.
What multi-platform means for viral loops(trigger.io)
34 points by amirnathoo 15y ago|5 comments
102.
Simple deployment of mobile codebase as web app with trigger.io(trigger.io)
45 points by amirnathoo 15y ago|0 comments
103.
by amirnathoo 15y ago
Great docs - looks super simple to get started, will definitely try this out. Do you support CORS out of interest?
104.
by amirnathoo 15y ago
The code is written to use some trigger.io APIs so you'd need to build the app per the instructions in the blog post.
105.
by amirnathoo 15y ago
There's no 'off' switch for apps in the store or if users have already downloaded them. But we ask for the subscription payment as long as you keep distributing the app if it is a paid app or if you want to put your own splash page in.
106.
by amirnathoo 15y ago
The code for the basic template app which we reference in the article is here: https://github.com/trigger-corp/Forge-Bootstrap
107.
by amirnathoo 15y ago
You're right in that we're mostly closed at the moment, with our command line build tool open here: https://github.com/trigger-corp/build-tools We think the biggest barrier to adoption of a platform like ours or PhoneGap's is complexity.
108.
by amirnathoo 15y ago
We'll do other articles and comparisons in the future - we haven't yet had a chance to benchmark against Appcelerator. Anecdotally we think a performance comparison of the bridge would be favorable, but actually the main reason people use u
109.
by amirnathoo 15y ago
Nice, can you say a bit more about the purpose of the app. And did you consider creating it for mobile or other browser platforms. Loaded question - I'm a co-founder of Trigger.io :-D
110.
by amirnathoo 15y ago
When thinking about the pricing model, you should compare us to a combination of PhoneGap's cloud build service (which is also fremium and restrictive) and their support packages: http://phonegap.com/support#support-packages The main diff
111.
by amirnathoo 15y ago
Yep, to be clear - trigger.io is not a fork of PhoneGap or downstream from it.
112.
by amirnathoo 15y ago
We're trying to optimize the development cycle for web devs. So it's not just about the bridge itself, but also keeping the code around it lean and fit in with our command line tools / cloud build service. All so the build / test cycle is s
113.
by amirnathoo 15y ago
Thanks, we'll do comparisons against other native bridges in the future also. Cool app by the way thanks for sharing... though I wish I could try it on my Android ;-)
114.
Why Trigger.io doesn’t use PhoneGap – 5x faster native bridge(trigger.io)
136 points by amirnathoo 15y ago|62 comments
115.
Coolest Startups in America(blog.rightsignature.com)
29 points by amirnathoo 15y ago|4 comments
116.
by amirnathoo 15y ago
Currently, you'd still have to upload new versions to the store manually. We're working on tools to ease that process also, but wanted to stay focused on the simplicity of the initial build process for our initial launch.
117.
by amirnathoo 15y ago
Yes, this isn't exactly a comprehensive study, I just looked up some ballpark figures to get an idea and was really surprised by just how big the diff was between where consumer attention vs developer attention seemed to be. I'm not sure it
118.
by amirnathoo 15y ago
I don't think it's about giving up on standards in favor of native in an either-or kind of way. If you're building an app nowadays, ideally you'd have a web, mobile web, iOS and Android version at launch. Because you want distribution and n
119.
by amirnathoo 15y ago
I'm more optimistic - Apple doesn't have a monopoly on the software stack like Microsoft did with Windows. Competition between Android, iOS and Windows Phone already seems to be spurring a race towards openness.
120.
Mobile shift: You’ve probably underestimated just how big this is(trigger.io)
231 points by amirnathoo 15y ago|114 comments

More ›