18 comments

[ 7.1 ms ] story [ 38.3 ms ] thread
There's few things that are as infuriating as having to write sync code, when you have other things to take care of. Glad this is around now.
I've used Firebase a lot (lucky to be in the beta) for my web apps and trigger for my hackathon projects that i want to quickly push to app store. Great to finally see an in depth tutorial getting written about Trigger and Firebase working together!
have they sorted out the security issues with having the sync code exposed to clients? what prevents others from accessing that information when they shouldn't?
Curious about this as well.
my 'build stuff with javascript' to-do list grows even further.

now...to find some time.

Curious. What are Firebase and Trigger.io help me solve that isn't already available in any other standard web framework (think LAMP)? Are they only really applicable for building real-time apps?
My understanding, from a cursory perusal, is that this isn't serving web content to the phone's existing browser, but rather packing up your html and javascript with a (thin, one hopes) custom browser to display them, which also exposes more native functionality than does the regular browser. So you aren't writing a web app, you're writing a native app with web technologies, sort of.

Someone please correct me if I'm off base.

Anyone have a firebase beta code? Never got an invite from 'em yet. Email dan'at'thestroots.com if you have one please!
Check your inbox :)
(comment deleted)
You can use firebase in any browser or html5 setting. You can also do the same with phonegap and firebase. I fail to see the extra value added by trigger.io here.
Trigger.io has numerous advantages over Phonegap, some of which being setup and speed.
Agree that trigger might be better.

But in this case both runs firebase the same

One step closer to completely serverless development. Love it.