Apps Too Many Views = Bad For Performance

[Loopback]

Hi all,

After spending the last 4 hours creating my activity with a bunch of textviews (i have 86 of them) and feeling pleased with myself because it looks great. I notice that the android studio is complaining that anything greater than 80 view is bad for performance.

It works fine in the emulator so am I missing something obvious here (i'm only displaying text in these views, and not a massive amount of it) or is this a stupid way of doing things? If there is another (better) way, i would appreciate any advice.

Thanks.

edit: No worries, i think i've worked this out now. Cheers.

 

[HeavensSentSword]

Why do you have so many textviews? I think what android wants you to do is to place all the strings that you have into one textfield. But I understand where your coming from. It is sometimes easier for us to keep things separate and then we can keep track of what we have and have not assigned.

I think android is just being lazy and saying that there could be issues with lower end phones. They will have issues with displaying and rendering all of the 86 fields. Most new phones won't have a problem I would think. Try it on a real device and tell us how things go, I am kind of curious to know. But from what I gathered and personal experience I think the emulator is slower and has more trouble than a real phone.

 

[Loopback]

Thanks for the reply mate. I was doing things too literally, by adding a text view for pretty much every string I was adding. I remembered that I can use \n and I've dropped it down to 30 ish.