I'm so glad I'm not the only person finding it awesome but frustrating! I'm currently scheduled to give a talk on couchdb for mobile (specifically ios) in London but just know that the Q&A is going to be full of 'isn't couch dead / isn't everyone using mongo now' type questions.
To look at your specific question on Android - have you considered an alternative architecture where you persist couch objects locally and then sync each object to the remote database when required? It could well be that your use case requires a heavier client side solution, but for the projects I'm working on I find this works really well when the number of objects in flight at any one time is low. I basically deserialise documents into custom objects which are persisted client side and then serialised on the way out again. I get the real benefit of couch when it comes to searching (I have some entertaining views) and also storing photos etc as attachments and in my case I can restrict this to being when the user is online. Obviously this approach is a compromise and may not be suitable for your use case. TouchDB looks like a really interesting option too ... although maybe not production ready yet. https://github.com/couchbaselabs/TouchDB-iOS Roger > If anyone wants to give me word on whether Couchbase Mobile Syncpoint > is the route I should go for Android, I would appreciate it! Still > trying to figure this out! ;) > > Jonathan Porta
