|
My problem is that we are really going to push performance boundaries. The more "options" we have the slower to work out what to show, which directly translates into slower flings and scrolls, which directly translates into unhappy users. We already get complaints that cover rendering is too slow, and this is going to make it slower. It is easy to forget that these devices are slow and memory challenged.
To overcome the problems it might become necessary to limit the number of choices to 1 or 2 fields, and/or to limit the layout choices in some way such as fixed width regardless of device size. Entering an empty line because there is no data to show requires processing both in CC and in Android widget layout. Etc.
|