However I wouldn’t be writing this without the knowing that still it’s possible to solve that issue on a mobile client without getting OutOfMemoryException. And of course we shouldn’t forget about GraphQL. The first and I believe it to be the best solution is to make you backend developer implement a pagination or, maybe, you should ask him for the access to the repo with the backend source code to implement it yourself. And looks like you’ll have to deal with it.
But there is one issue - your backend developer doesn’t care about his clients (means he doesn’t care about you), so he considers that it’s ok to respond with a 30MB JSON on a GET request.
Also you are trying to be on a bleeding edge of the technology stack so you are using Kotlin and RxJava in your project. Lets image that you are developing an Android app that communicates with your REST backend via Retrofit which already became an industry-standard.
0 kommentar(er)
