performance - android client

[soundof-ferns]

There is an issue with some android phones whereby browsers that are based on chromium (i.e. all of them bar Firefox) will experience freezes on certain actions that get longer with larger libraries, and can lead to crashes in some cases.  Have you tried Firefox on the Android device?  It may perform a bit better.
I have a middle range android phone and can only get by with Firefox for moOde.

Thanks for the suggestion. I have used chrome, firefox, and opera on an android phone, in fact started with firefox.  I settled on opera lite.  I think my only solution is to put a more capable client in my listening room, maybe a chromebook or surface box.

with regard to tim's comments, I understand that my large collection may be a corner case - today.  I suspect I will be less an outlier in a few short years.  Also, from my time in the software world, a few hundred thousand tracks is not a large index in the database community.  There are likely known approaches to greatly ameliorate or eliminate this issue, though I realize this may not be a priority and may be an ambitious undertaking. I looked on github and did not see any sort of design document.  Is there anything above the source code level to look at if someone wanted to suggest performance improvements?