I was under the impression that both the Android and Apple multi-tasking implemntations were limited in various ways, but that the Apple one was more limited, so you could probably still count that if you wanted to.
The Android way has less (if any) limitations (you register a service/daemon which behaves as an application server, it's headless but other than that does whatever it wants). Apple's solution is much more limited (you register tasks against the OS and the OS runs it, which limits what you can do to what the OS itself provides) but the tradeoff is that "debatable" programming has lower chances of eating your battery alive (and the OS can more efficiently handle some services e.g. if 5 different applications asked for GPS/movement notification, the OS can poll the chip once and it will then dispatch that one message to everybody, whereas with the Android solution you'd have 5 different services polling the location API)
Unfortunately the talks on such subjects are filled with opinions of bystanders ... insightful articles/comments comparing X vs Y from people that used both in production are few and far between.
