Seems like my post was pretty specific on that point. Update correctly in the background, which is apparently asking too much. I can't tell you how many times I hit update then flip to another app and when I come back, its sitting back at the waiting to install screen. So I have to watch it until at least the download bars start on the second batch of apps before I can safely navigate away.
My issues aren't with any specific app (or dev), but a clear pattern than has emerged among them, including 1st party ones developed by MS. Regardless of where you want to place blame, the problem is still there. Additionally, the technical handling of background apps/resources is an area MS needs to keep working on and that is clearly their problem.
So much like Vista, you can blame (rightfully in most cases) the hardware vendors for releasing ****ty drivers, but at the end of the day its MS that will take the PR hit. So considering how much ad money they are dumping lately, it simply seems counterproductive to me to play the blame game.
Apple was meticulous about its early apps because they realized how critical that perception would be. MS gives me the impression that it wants to run a walled garden without taking any responsibility for what is inside it.
You have something else wrong, then. Apps update while the Store is in the background just fine for me. They even pop up a notification toast when they're done. They don't (obviously) update if you close the Store app while it's downloading.