Helios
helios.io
helios.io
This looks fantastic, I'll definitely be checking this out!
My favorite album: https://soundcloud.com/_type/sets/helios-eingya
His soundcloud: https://soundcloud.com/keithkenniff
A lot of the music is on Spotify, and here's a link to a set of it on Soundcloud: https://soundcloud.com/keithkenniff/sets/goldmund
https://github.com/mattt/rack-in-app-purchase
https://github.com/mattt/rack-core-data
https://github.com/mattt/rack-passbook
https://github.com/mattt/rack-push-notification
That is why codebase looks very clean and simple.Although "an extensible open-source mobile backend framework" seems to say that it also applies to non iOS, it doesn't seem that it does. Is it more suited for iOS, or iOS only?
Admittedly, this is one of the best things that ever happened to open source w.r.t mobile development in the last few months!
But I worry about how it would hold up in terms of performance, given this recent benchmarking fest featured on HN. http://www.techempower.com/blog/2013/03/28/framework-benchma...
A massive limitation of Parse.com is with their Javascript SDK - you have to expose your app keys to the client and the SDK doesn't work at all on any version of IE unless you have SSL enabled.
2) Wouldn't any similarly-situated Javascript library face the same problems, with Access Control Lists probably being the most practical solution?
3) Moreover, with any mobile backend, you must assume that the keys that ship within the code of your native app will be public. So you should be using Access Control Lists if you're using the iOS SDK, for example.
Can this potentially also work for other mobile platforms?
The code would have better test coverage and more people to support the project.
I wondered in the subway while coming back home if Helios helps to sync backend-made changes to the app through push notifications, in an automagically fashion.