Slashdot Mirror
Windows Phone 7 To Get Multi-Tasking, IE9, Xbox Integration
geek4 writes "Microsoft is planning to introduce multi-tasking and full integration with Internet Explorer 9 in future updates to its Windows Phone 7 mobile operating system later this year. IE9 on Windows Phone 7 will use the same core browsing engine as on PCs. Microsoft also talked about the importance of multi-tasking, and claims it can now offer fast task switching without causing serious detriment to the battery life. In particular, Microsoft said, this will improve the experience of using third party applications. In a demo, a Microsoft engineer showed how a music application called 'Slacker' could keep music playing in the background while the user moved between different applications. By holding down the 'back' button, users can also see all their recently accessed applications, allowing them to switch easily between them."
Microsoft also demonstrated how they're integrating WP7 with Xbox 360 consoles, showing a video of players using their phones as an auxiliary touchscreen controller to interact with a Kinect game.
it would be extremely trivial for such a compromised phone to broadcast and infect all XBox 360's within range
A browser exploit can cause a phone to spontaneously sprout limbs, open your 360, connect itself to the JTAG header, and perform the NAND dumping and flashing nonsense currently required to run unsigned code? That's one hell of a phone!
Come on, be fair. It took Apple waaay longer than that to figure it out.
Am I the only one that's really surprised that multitasking wasn't already a feature? I thought it was weird when they announced it for the iPhone 4 like it was some huge breakthrough. Symbian might be a piece of crap as a smartphone OS, but, damn, they've had multitasking for 10 years now. It's not a hardware issue. How did this get ignored for so long in iOS and Windows phone?
This sentence no verb.
... iphones have been doing for years?
Tehehe
If Microsoft released a 3D modeling tool, would it be called Scatchup?
Windows Phone 7 was lacking a lot of functionality the earlier Windows Mobile had. It's just a new not-yet-complete OS.
This makes me wonder if they're using a more agile-style approach and releasing what functionality they have completely tested instead of releasing the complete functionality regardless of what they've had time to test? It does make sense in a phone OS.
Exactly. It's just awful, how slowly things are evolving in these locked down mobile systems.
Metro is such a clean, fast interface, lets me see just what I want to see exactly when I want to see it. There's very little hunting/searching for something, as if I use it more than once per day I just pin it to the front page. It just fits extremely well how I want to use a phone.
Although I do have to say, if I couldn't have test-driven it on an HD2 I probably wouldn't have taken the leap to full fledged WP7 hardware. Kudos to MS for not legalbomb XDA from orbit when DFT released the ROM into the wild. If they continue to be smart, they'll let the mod community flourish they way they did with WM6 - that's the only thing that made the platform stay as relevant as it did, for as long as it did.
"I'd make a wooshing sound, but the post was so far over your head it was inaudible..."
No. Xenix was introduced earlier in the '80s, and MP/M before that, on various (non-Commodore) personal computer architectures.
"National Security is the chief cause of national insecurity." - Celine's First Law
Multitasking on mobile devices is a different problem than multitasking on desktops. With a desktop, the challenges are primarily allocating memory and CPU. With mobile devices, network and battery are the resources that need to be optimized. So with a desktop app, you can shove it int he background, give it limited cpu cycles and memory without any architectural changes. With mobile devices, it is a lot harder to limit because you don't want the CPU running all the time and even if nothing else is using the network connection, letting some background app use it constantly will result in draining the user's battery and potentially costing them data usage fees.
A good example is push based notifications. If applications ping a server regularly to see if they have updates or if there is a message, that uses a lot more of both resources than if it subscribes to a network service that notifies the device when the same event occurs. The problem is, the former is easier to code and the way developers are used to doing things on desktops where they don't have to worry about battery and data nearly as much.
So when Microsoft says they are adding in support for multitasking, does that mean:
In short, multitasking for mobile devices is a difficult problem, with different challenges from traditional multitasking on desktops. Google engineers have repeatedly stated that they consider multitasking and battery life problems to be one of their greatest challenges and current failings. Microsoft announcing that they're coming out with something is, then interesting, although it may be a poor clone of one of the other vendors' implementations.
Almost! I think it would be called 'ScatUp'. As soon as I find a link to confirm this, I'll squirt it to you.
No, no sig. Really.
ThePromenader
How so? Serious question, what have you found that IE9 can't do but (mobile) WebKit can? The whole idea behind IE9 is that you can use exactly the same HTML(5) and CSS(3) as for other browsers, but IE9 will (sometimes) do it faster.
The current WP7 browser is based on IE7, so yeah, it's shoddy in that sense (it actually works well in the little testing I've given it, including some sites that mobile WebKit can't handle). The point of this announcement is that the next version of the WP7 browser *won't* be "shoddy" any more.
There's no place I could be, since I've found Serenity...