And if you're dealing with images, you might want to also contemplate the idea of thumbnails v large images, handling the latter, in particular, in a lazy-loading model. And if you could return URLs for this binary data, rather than the data itself, that would definitely lend itself for lazy loading (as well as giving you the ability to easy download the binary information rather than a Base64 encoding which is 33% larger). By getting those out of the initial response, that will address many issues. Base64-encoded binary data such as images or sound files). the user goes to a detail screen).Ī particular permutation of the prior point would be if the JSON is currently including any large data elements (e.g. For example, the first request could return just identifiers or header information for all or a reasonable subset of the records, and then you could have subsequent requests for additional details (e.g. Given that additional server records can presumably be added between requests, you'll have to think carefully about that implementation, but it's probably easy to do.Īnother way of making the JSON more efficient, is to limit the data returned in the initial request. If the JSON is really large, you could always contemplate a 'paging' metaphor, where you download the first x records, and then make subsequent requests for the next 'pages' of server data.

So let me tackle what I presume is the underlying question, that you want to achieve improved user experience despite a very large server database: The term 'lazy-loading' might not be entirely well suited to a single JSON response, and it might predispose us to one approach over another.

Json editor download iphone