Robbit wrote:Hi camel,
thank you very much for your quick reply. First let me say that I'm talking about the list mode, only. The point is, I understand, that the amount of data shown for each contact is bigger than in stock version by two items: company and group. That is meant by "stock contacts is totally limited", right? But then at least the same amount of steady information as in stock contacts (picture, name and phone number) should be possible without straining the memory. Or maybe I haven't understand the difference between the behaviour of stock and DW contacts properly!? And I must admit that I really couldn't follow the explanation for the background sync of the stock contacts, as I expect it is operating anyway, despite its gorgeous replacement
I have about 500 contacts which are eating up 2,5 MB (after your calculation), which is a reasonable value of memory occupied by the phone list (as my Desire S has 786 MB). This leads to the question: which pic size is used by either stock and DW contacts: original or thumbnail size?
Please do not feel bothered by my insisting, but your app has grown to my most important one indeed, since the last update of HTC's Sense deteriorated the stock contacts heavily: the formerly brilliant contact pics (line-size big and with an unbelievably dynamic border!!!) are now unnecessarily small with a dropdown arrow, which COVERS THE RIGHT PART OF THE PIC!!! I was really shocked about this foolish layout. BTW: also the unadjustable homescreen transitions (the smooth sliding with the tender following background picture has gone for a 3D animation with fixed background picture), unstoppable wobbling of some widgets and other parts are really annoying in the new Sense.
So let me say thank you very much again for developing this valuable app and staying in touch with your customers
Robbit
first - you gave me info for yoir internla memory, not the space of your free availible "free system memory" or "system memory cache" ... anyhow. maybe your phone have enough space free, but not some other buggy devices, which are having only 20MB system memory left or less, and also maybe your phone is not one of the buggy sony x-10, which would also like to have it working ...
and maybe you are only having 500 contacts, but we must also think, that it is possible on devices, which are having 10MB left + 10.000 contacts, and they also want to use it ....
an average user is having 500 contacts and 20 of them is having a picture for them...
so, the picture is notm the highest priority til now, maybe in future, the users will getting more contact picture, and then maybe we will add an option to preload the pictures, and then it will be getting crappy -but user can descide ...
but, it is much more complicated as i told you, you must also think on several different databases, where contact infos are stored. in a bad case, there will be made several queries to get all information about 1 user, then, think, how it would be funny, if user wants to scroll, but the android API wants to show the pictures at first in the list for whole 5000 contacts and is making 15.000 sql queries ?
and why should we calc for all 5000 user the displaying the contact pictures and all informations + displaying it + space for it + space for all temp queries, which would also need memory (before garbage will happen on used mem), if the user wants only to jump to alpha "T" and show contacts,m whicha re beginning with "T" ?
as told - i will keep an eye on it, but our politic, speed is highest priority.
cu camel