http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/ Engadget Comments for http://www.engadget.com/media/feedlogo.gif http://www.engadget.com en-us Copyright 2012 Weblogs, Inc. The contents of this feed are available for non-commercial use only. Blogsmith http://www.blogsmith.com/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
Now, I interpret this as having multitasking favoring MO and OEM access, but with waivers and a certification process. In essence, it has multitasking.

I'm glad MS is going to help preserve battery life via a process vs a wild west approach.

kudos to MS. Now I can't wait until MIX.]]>Feb 18th 2010 6:12AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 6:30AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
As long as the multitasking is allowed for apps that really benefit from it I am happy.]]>Feb 18th 2010 7:10AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 7:40AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
If this is indeed the case, then I'm satisfied as far as the multitasking controversy is involved.]]>Feb 18th 2010 9:01AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Apple can't write OSs for toffee. They finally gave up and used free UNIX for the CrApple Mac.

MS have always tried to write good multitasking OSs and since they "acquired" the VMS technology of the the VAX, they are now the best in the world at it thanks to Dave Cutler.

The way that WM 7 is laid down looks to be very good indeed. I too like the way that apps by default will probably not be able to run in the background. This, it seems to me, will force "simple" apps to be single tasking whilst the OS and presumeably some apps will need to run more than one job. The question is, who decides who gets what permissions?

That said, security for the OS will be much improved by MS's policies.

I thoroughly approve.]]>Feb 18th 2010 10:49AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
And I concur !]]>Feb 18th 2010 3:52PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/I think people are mildly misreading what it says in the documents regarding multitasking. It says: if you plan to sell your stuff in the marketplace/preload it onto devices, you're going to have to use our .NET-based APIs that may or may not support multitasking (it doesn't explicitly say they don't, but it seems to be implied), if you want access to native-level APIs that we don't approve of, you're free to distribute it on XNA Developers/sell it on your own, but not in our store. As well, it says that you will have access to additional "developer services and runtime services", which I'm guessing means background services.

Summary
Multitasking: .NET Layer maybe (probably not though), .NET + native (might not make it into the store/OEM) more likely, native goodness that we are used to on XDA almost certainly (but not in the marketplace).]]>Feb 18th 2010 4:01PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/I'm not as savvy as you guys. Does this mean I can listen to Pandora while browsing the web and chatting with my buddies on AIM as I ride the bus/train?]]>Feb 18th 2010 4:06PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
M$ apologists can spin this anyway they like but it will be an absolute mess for consumers to find out what can be used on their handsets.

Typical convoluted mess, build the matrix:

app by handset by network]]>Feb 18th 2010 5:13PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 19th 2010 12:33AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.scinotes.org/images/wp7_running_bg_apps.png

Just run any app and press the windows key, the app is sent to background where it is still running, then you can launch other apps aswell, in this image I have run two apps in background and launched the internet explorer in the emulator.]]>Mar 16th 2010 12:49PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
Microsoft fell down in its previous attempts as it relates to market - they have standardized the platform and guidelines with headset OEMs for instances to build a better experience across the ecosystem of WP7 offerings.

This is the experience that Apple has shown works and can be profited on. I think this strategy pays homage to both the past and the future realizing its distinct need to profit. Not discounting your complaints... just rationalizing the grand scheme here.]]>Apr 25th 2010 7:10PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 6:15AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
You know, techincally he did "bring balance" to the force... by whittling down the vastly over balanced light side to bring it to more equal footing with the dark :D They just read the prophecy wrong.

Oh yes, uh, multitasking is good :)]]>Feb 18th 2010 7:05AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
MeeGo and Symbian are still there buddy.]]>Feb 18th 2010 7:08AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 6:15AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 6:16AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/I do hope that they don't use XNA for applications though. Something WPF-based that works and looks like Visual Studio (whether it be the Express Editions) would probably be way better...
Then again, Microsoft's throwing in some big changes, who knows what they come up with for this :)]]>Feb 18th 2010 6:55AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 7:06AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 3:22PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 3:43PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 7:16PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/So, in all fairness, when I said WPF-based I wasn't actually off-base at all. It all uses XAML, and that's where I was going with that :)]]>Feb 22nd 2010 5:54PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 6:17AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/thats not really a clean break.. at all...?]]>Feb 18th 2010 6:28AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
were you expecting something other the .net cf?]]>Feb 18th 2010 6:54AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 7:14AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
Yeah, Engadget calling this a clean break really doesn't make any sense. I've developed plenty of .NET CF applications for WinMo and I can't imagine they've changed CF all that much. Should be pretty easy to port stuff.]]>Feb 18th 2010 9:19AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
Also, it's my understanding that current .NET CF applications will need minimal work to transition to WP7S, mainly on the UI front. If a dev has built a totally custom UI (think TomTom, which has no WM menus at all), then it will be even easier.]]>Feb 18th 2010 9:41AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
http://www.rgbfilter.com/?p=3147

Also has a link to a Slashgear video where an MS rep at MWC confirms that the sample device was made by ASUS.]]>Feb 18th 2010 3:49PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Silverlight doesn't use the compact framework. It uses the CoreCLR]]>Feb 18th 2010 7:15PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 19th 2010 12:09PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 6:39AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/yeah you just add 0.5]]>Feb 18th 2010 6:43AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
There is only 1 phone realeased (HTC HD2) and 2 phones announced (Toshiba K01 and TG02) that meet the requirements to run WinMo 7]]>Feb 18th 2010 6:48AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 9:16AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 1:50PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/they said in the press release that the phones would have 3 buttons: home, back and search, no more and no less.]]>Feb 18th 2010 4:59PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 19th 2010 1:01PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
As long as your app can do most useful things without getting MS approval (e.g. connect to the world outside via web, phone, SMS, GPS) then I can't see a problem. You'll be able to write useful apps but not screw with the core of the phone.

The only WM app I've written is designed to stay in the background. I'm hoping apps are paused in the background by default but can request to be kept running if required. I'm sure most apps hogging resources when not running are due to lazy coding rather than necessity.]]>Feb 18th 2010 6:42AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
What is had to predict is who will lose in this equasion. I actually do not think it will be Apple or Android based phones at all (while it is fun for the fanboys to wish for this black and white scenario to play out, it is not reality most likely). Plenty of space for these to co-exist - especially if you look at the global marketplace for smart phone. No, I think the big losers will be RIM and Nokia over the next two to three years (and I live in Europe and trust me, the Nokia luster is wearing off even over here). ]]>Feb 18th 2010 6:54AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
Maybe; I'm kind of disappointed with what I've seen of WinMo7's enterprise/business features. It's nice, but not courier-nice. Maybe they're intentionally splitting paths to specifically corner different parts of the market?]]>Feb 18th 2010 6:57AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 2:04PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 2:34PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
Overall, this sounds pretty standard though. ]]>Feb 18th 2010 6:54AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
As someone who has done a decent amount of development for MS products, Microsoft LOVES lock-in. It's almost impossible to tell what is being used to push what at this point.

There are some large, notable exceptions, like Office for the Mac. But for the most part, Microsoft tries to create a huge ecosystem where everything is locked into everything else.]]>Feb 18th 2010 9:29AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/Feb 18th 2010 5:03PMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
- The applications are good and make sense
- User friendly
- Very responsive
- Blazingly fast
- Stable
- Very good on battery live

Thats all!

I dont care if it is XNA or Silverlight or C++ or .NET
Sleep or paused in the background or not sleep at all :)

At the end is the "user EXPERIENCE" that matters !

]]>Feb 18th 2010 6:57AMhttp://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/http://www.engadget.com/2010/02/18/windows-phone-7-development-policies-and-guidelines-leaked/
That's kind of like saying "I'm going to get on a plane, and I don't care if it goes north, south, east or west, so long as there's great service!"

Different platforms have very different potential in terms of what *level* of services applications can provide. For example, making a great text editor or web browser is something people like, but if it's impossible to make it the default application, then it's still somewhat limited in use.

This especially goes for people who want to access the hardware, say for things like augmented reality, microphone access (recording calls, etc.. - I know it's illegal in many places, but I'm just thinking function), and here's a big one nowadays: storage access and location (probably can't change defaults for obvious reasons).

It will make a very big difference to your user experience depending on what platforms and what accessibility is given.]]>Feb 18th 2010 9:03AM