View Single Post
Old 02-23-2018, 01:41 PM   #18
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by ilovejedd View Post
The problem with iOS is each application is sandboxed.

If one used CC for managing books, one would still have a copy of the book in CC and export/copy the book via share sheet to the reader of choice. For obvious reasons, native HTML, OPDS or Dropbox support in-app is quicker than exporting books one by one from CC.

Hence, I use CC on Android (where I can just point the reader to a shared folder containing my books) but not on iOS.
That also means that you don't use CC as your library manager, which in fact is what we designed it to be. No reader app (that I know of) can operate on calibre metadata as well as CC does, for example grouping and sorting on calibre custom columns and syncing "book read" information back to calibre.

If you use CC mostly as a transport then I suspect there are better solutions even on Android, for example dropbox with dropsync.
chaley is offline   Reply With Quote