I know, but it actually froze with 100% cpu usage, after 10 minutes still jamming my cpu, I killed it. The state it was comparable to the create chat button, it takes time. I only mentioned that as example as it was in the "same" state.

Another example: If you switch to yappari main-window, you sometimes can't scroll the openened chatlist, because it's syncing or doing whatever.

You might want to disable those background-syncs, to increase fluidity.

I know "create chat" can take some time, I have a huge contactlist (about 600) and about 350 of them have whatsapp I guess. Unfortunately it doesn't give any signs thats its loading, instead it freezes the UI without giving any respons.

I know you talked about that N900 is slow, you are right, conversations is slow too but yappari jamming my cpu at 100% (98% actually) for 10 minutes, the N900 can't be THAT slow.

--
Try to see the difference between the To: button, when sending sms: conversations -> New SMS -> To
and yappari

You see when writing SMS it pop-ups after about 3-5 sec, and while it's processing that list, the button is in "pressed" state, so the user "knows" it's loading

When you press yappari create chat, it freezes the UI (disabled chat scrolling, no sign of loading) and after 10 - 15 seconds it pops-up. Yappari doesn't keep the create chat button highlighted, so the user doesn't know it's processing something. That 10-15 seconds, well it's long but if there is shown some progress it makes it all more bearable. Or reduce the pop-up time by factor 3

Sorry for this massive post, but I try to be crystal clear