Mike Temporale
05-23-2006, 03:00 PM
<div class='os_post_top_link'><a href='http://blogs.msdn.com/fzandona/archive/2006/05/22/604080.aspx' target='_blank'>http://blogs.msdn.com/fzandona/archive/2006/05/22/604080.aspx</a><br /><br /></div><i>"Microsoft, as I mentioned earlier, is in charge of the core Operational System (Windows CE), the shell (user interface), a set of applications (Office Mobile, IE Mobile, WMP Mobile, etc.), RIL, and so on. We also expose several APIs (from both Windows CE as well as those specific to WM) and we include .NET Compact Framework/components to allow developers to extend the Windows Mobile platform. This is the kit we deliver to the device manufacturer – as you probably have already figured out, at this stage we still don’t have a cell phone or a PDA. In fact, we are far from having a functional device, it is just a bunch of software. It varies a lot among device manufacturers, but I would guess this kit represents only 60 to, no more than, 80% of all software inside a WM-based device. The other 20 to 40% (or even more) are from the device manufacturer and the mobile operator."</i><br /><br /><img src="http://www.smartphonethoughts.com/images/Temporale-20060523-WinMoBreakOut.jpg" alt="User submitted image" title="User submitted image"/> <br /><br />Fernando Zandoná follows up his Windows CE vs Windows Mobile <a href="http://www.smartphonethoughts.com/forums/viewtopic.php?t=11198">post</a> with another great article to help us all understand what part Microsoft, the Mobile Operators, and the OEM's all play in getting a Windows Mobile device to market. I didn't realize so much code actually comes from the manufacturer and the mobile operators. 8O