EnduroSync (https://orandolabs.com) does exactly the same thing, and it already has syncing. It's available for iOS and Android now, with more platform support coming.
In response to this announcement, Orando Labs (https://orandolabs.com) has decided to offer EnduroSync and Identio with open source licenses and as paid AMI instances. We believe we have a unique solution to some difficult problems (identity and syncing), and want to see our solutions widely adopted. Read more at http://orandolabs.wordpress.com/2014/07/12/amazon-cognito
Orando Labs (https://orandolabs.com) has EnduroSync and Identio. Striking similarities between the products. EnduroSync is a full object store and does not have the data size limitations.
The similarities between Cognito and EnduroSync (Orando Labs, https://orandolabs.com - announced in May) are striking. Including the latin sounding names. Except that EnduroSync is an object store and has no data size limitations. Even the pricing is similar.
As far as Hacker New goes, we announced EnduroSync back in May, and got no promotion. Not one up vote?
EnduroSync (https://orandolabs.com) is a new service for syncing object stores. It has clients for iOS and Android now, with several others right around the corner.
Data is modeled with objects. The object store works offline and online. If you sign up for the service, then you get syncing.
EnduroSync also has a very nice permission model, enabling sharing of object stores in a variety of ways (per user, per app, ...).
Unfortunately, Angular 2.0 sounds like a project killer. Let's abandon the huge effort put in by the community, and build this shiny new framework with all the latest and greatest (and currently unsupported) tools. Let's support everything we can possibly foresee, and make the ultimate framework that will never need improvement. That is until Angular 3.0, when we'll need to support ES8...
Rewriting a successful framework with no backward support is suicide. Please read this link before continuing on this path: http://www.joelonsoftware.com/articles/fog0000000069.html. Another informative example is Perl 6. The 'rewrite' killed Perl. Microsoft also did this time after time, forcing developers to constantly rewrite their applications instead of spending time writing new products. Even Python 3, with it's limited incompatibilities, had a very negative effect on the community: https://programmers.stackexchange.com/questions/63859/why-do....
Why should I bother supporting Angular 2.0, since 2 years from now the developers are going to get bored and want Angular 3.0? The community is NOT going to take the time to rewrite all their code to scratch your itch. My time is very limited, and I need to be selective where I use it. I love Angular, but there is zero chance I will rewrite any of my code for Angular 2.0. It's not going to happen. I'm quite certain that my sentiments are shared by other developers who have put in far more time and effort than I have.
My strong advice is to fix and optimize what you have. If there are areas that need rewriting or rearchitecting, then do it, but leave a clear upgrade path and don't break existing apps where possible. Sorry, but that's how software works.
You have a ground breaking, beautifully designed framework. Please don't destroy it because it's not perfect. Nothing is.
Can someone at Google please talk some sense into the developers running this project?