Board Thread:Game Discussion/@comment-10983288-20130828042729/@comment-11490363-20130828210554

Timformer wrote: as a programmer i laugh at the prospect of memory/performance limitations preventing higher deck size limits. even if you're needing to sort the cards, as you can, 200 is not a big number for the average smartphone/tablet processor.

but then again, that doesn't stop the software engineers from making stupid decisions that make their deck code unscalable. It is not just the sorting, but the data transfer. Constantly transferring 1000 card inventories consumes 5x more bandwidth than 200. I remember when the help request queue was real time, and then it was changed to update every 20 seconds instead. Partly to reduce sniping I am sure, but also to reduce the load on the servers. Standard comp sci stuff. real time connectivity is very resource heavy, while a 20 second heartbeat is very light.

I don't think you understand scalability if you think it is just their bad decisions. No one wants to just waste bandwidth or resources for no reason. The app is already a CPU hog, why would we want them to increase the limits with the existing code? I barely get charge increase when plugged in and playing the game, that is poor programming to be sure, but I think it has to do with graphics and flash more than the size of a player's inventory.

I wish they would figure out why there is a 4 second delay whenever you switch from one screen to the next. IF it is just an android thing then they are dumb asses for not doing proper QA.