View Single Post
Old 05-03-2014, 11:31 AM   #4
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
You can filter the Aa menu, yes (with a few tweaks possible on a JailBroken device), but that's not what's slowing down the device. At worst, it'll slow down the Aa menu itself, but that's all.

As was said, indexing is most likely the culprit in terms of perceived slowness.

Apart from that, the only other thing having a perceivable impact on UI responsiveness is the size of the catalog: the more books you have, the slower the navigation on the Home/Collections screen.

Once you're in a book, you're home free though, nothing impacts that very much (unless you're using a very, very, very crappy font that Amazon's renderer doesn't like, but it usually just crashes in fun & interesting ways instead of slowing down).

Last edited by NiLuJe; 05-03-2014 at 11:33 AM.
NiLuJe is offline   Reply With Quote