I don'tknow enough of Android or object oriented architecture to be useful perhaps, but thrre thoughts occur:
1. Are there not existing platform libraries to handle things like what your Fetcher class does? 2. Is there any point in scaling incoming images on the client? Or is this something that ought to be implemented server side? Agree that reducing outgoing images is important, since smartphone cameras often have crazy pixel sizes. 3. Whether or not it's in the initial iteration, I think it's important to think in terms of a local store that syncs for offline use. I'm not sure whether that's allowed for above or not.
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2016-02-22 12:35 pm (UTC)1. Are there not existing platform libraries to handle things like what your Fetcher class does?
2. Is there any point in scaling incoming images on the client? Or is this something that ought to be implemented server side? Agree that reducing outgoing images is important, since smartphone cameras often have crazy pixel sizes.
3. Whether or not it's in the initial iteration, I think it's important to think in terms of a local store that syncs for offline use. I'm not sure whether that's allowed for above or not.
Hope that's of at least some little help :-)