Quote:
Originally Posted by mrowz
Ahh... so I would use CC to get & manage books from the content server, and then open them on my device in any reader I like?
|
In theory, yes. I am the developer of Android CC (I don't own any Apple hardware) so I can't pontificate about "any reader". I know from comments in the CC forum that it works with lots of reader apps.
Quote:
|
Will the read position syncing across devices e.g. in MapleRead still work?
|
Short answer: I don't know.
Longer answer: this depends on how the reader app matches books on different devices when syncing. On iOS, Apple says that CC cannot hand a book file name to a reader app. Instead CC hands the entire file (contents) to the app, which stores it however it does. If a) the app uses some filename as the sync ID and b) picks some random name when a book is handed to it, then I would expect syncing to be problematic. If instead it syncs using some internal algorithm based on metadata or uses the base file name CC hands it then I would expect sync to work. It also could be that the app syncs by moving the book into cloud storage. That should work with books handed over by CC.
One experiment that might answer the question: put a book into Dropbox (or some cloud provider), use the cloud app to "Send the book to *reader app*", then see how the reader app syncs. AFAIK iOS CC "Sends the book" so it should behave in the same way.
If this is important to you then I suggest you post the question
in the CC forum. Some iOS user should be able to shed light on how specific reader apps behave.