This issue won't be fixed anytime soon. If will ever be fixed. In order clan roster page not to be reseted once you tap "back", must be kept in RAM memory therefore increasing KaW app footprint in RAM memory. While this is not a problem on iOS because only system apps are allowed to run background processes while 3th party apps are sandboxed and the amount of permitted processes is close to none (push notification and music streaming only) it is a problem on an multitasking operating system like Android where 3th party apps are running in background. Yes, on high-end devices is not a problem. 2-3Gb RAM memory is a norm for 2013-2014 flagship devices. But there's many low-end devices out there with 512Mb RAM memory. From those 512Mb around 300Mb are used by operating system. So increasing RAM footprint of KaW app will affect the experience of less fortunate users who can't afford a flagship device or just don't feel like spending 5-600 euro ($7-800) for a smartphone.
Just grow and you wont have to scroll so far down on rister. Lol. Im.on android to.. kinda sucks. Happy kawing
I haven't warred for a while on mobile device. Last time I did was the galaxy s3.. it was horrible, and very much at a disadvantage. I now have the note 3. But haven't warred with it. So definite support from me.
Not much. Couple of megabytes. But enough to ruin the user experience on low-end devices. On low-end devices every megabyte matter.
Vlad, is there anything I can personally do to make it better on my phone since I do have a 2GB RAM or is it all in the dev's hands?
I'll give you an example about how a minor feature can affect KaW user experience on low-end device. There's several devices out there that have a built-in menu button or a menu button on virtual navigation bar. Those devices can access the quick menu in any section of KaW even where the KaW app built-in 3-dots button is not available (clan chat, world chat, private message, etc.). Tho couple of months ago the quick menu in those sections was changed and now consist on "home" only. Why? Because a full quick menu (home, profile, search, marketplace, allies and clan) let a higher footprint in ram memory a footprint that was affecting low-end devices.
Are you talking about fixing the "scroll issue"? If yes, if you are familiar with Eclipse or Android Developer Studio yes you can fix it for yourself. But this would be reverse engineering and against ToU. Exactly what keep me away of fixing this issue for me personally.
Thanks for the answers vlad there's really no way of fixing this without losing some players then so /lock
Scrolling indeed sucks. But slower? The actions even on mid-range devices are faster than any iPhone out there. That's why I'm not bothered by scrolling issue. The time i lose with scrolling is compensated by faster actions.