Quote:
Originally Posted by crane3
If Google goes the crapple's ios way, then there will not be file sharing; a reader app cannot select a book from a folder to read but must have its own copy/duplicate of the book. Each app is sandboxed(?) within its own environment. Android CC will have to do like IOS CC where CC will have to send a copy of the book to a reader app.....lots of duplicates to use up memory/ram.
|
This part I understand. Slightly inconvenient and I would prefer it not be the case, but it just means adding one more step (or two) to my reading workflow. One would be deleting the book from my reader app when I finish reading it.
Quote:
Originally Posted by crane3
Read the Oreo specs(?)/features that any app that over-uses resources will be removed. Will CC be penalized for over usage when creating multiple copies of books for various reader apps? or will the reader app? What constitute "over use of resources"?. The Galaxy Tab S4 will be released with Oreo which is headed to be more like IOS & should be avoided by me.
|
Thanks for the explanation. I am less confused now. While I don't know what will come down the pike, as it stands now simple book storage, even duplicates across apps, will not constitute an overuse of resources. Overuse of resources targets background resources like battery, memory, cpu, execution limits. Items that will affect the overall experience or hinder the currently running app.