Epstein

Response from developer

We’re sorry you had a frustrating experience, but it is important to clarify where these issues come from. Our app pulls these files from the government source, and the speed, availability, and performance of document loading are heavily dependent on that source system. This archive contains over 6 million files and petabytes of data, so when the government side is slow, rate limited, or inconsistent, that directly impacts how quickly files can be delivered in our app as well. Those delays are not being created on our side locally. What we are doing on our end is organizing this enormous volume of material into a format that is far easier to browse than the raw government site, which many users find difficult, cluttered, and inefficient to navigate. We continue to improve the experience through design updates, navigation enhancements, and performance optimizations wherever we actually have control. But we also want users reading this to understand that no app can completely override the limitations of the source system it depends on, especially when dealing with millions of files and such a large amount of data. So while we respect your opinion on the design and usability, the loading issues you mentioned are largely tied to the government source itself, not because we are choosing to make the app slow. Our goal is to make this huge archive more readable, searchable, and accessible than the original source, and we will keep improving that experience.