I know of no such effort already underway, so if this is something you think will be valuable, then go for it.
I do have a few questions, though:
- What kind of service are you thinking of? SOAP-based or REST? Or something else?
- I'd be interested in understanding what benefit a remote repository would provide. Why wouldn't you just use a repository that lives close to where the connection is made? For example, in the case of Android, why wouldn't you store the connection locally on the phone?
- Even if you have a good reason to store it remotely, then how are you going to secure that connection between your app and the service? It seems to me that you'd need some form of token or credentials locally to be able to access the connection details kept remotely.
I don't mean to tear down your idea, but am just wondering what benefits this provides. To me, it seems to bring about an unnecessary amount of complexity. But I'm willing to be convinced otherwise.
Spring Social Project Lead