putting the file-loading in 'core' also means that's where the caching lives.
seems like the app layer would know best how to find & cache files for its platform.
this refactoring would also be useful for when loading data files from HTTP (lots of handy android utils to do this efficiently).
reading files from classpath is slow. http://blog.nimbledroid.com/2016/04/06/slow-ClassLoader.getResourceAsStream.html
putting the file-loading in 'core' also means that's where the caching lives.
seems like the app layer would know best how to find & cache files for its platform. this refactoring would also be useful for when loading data files from HTTP (lots of handy android utils to do this efficiently).
this needs a lot of design thought