Microsoft Wants You to Port iPhone Apps to Windows Mobile, Nay Windows Phone
The Windows Marketplace for Mobile has not been launched yet, as a matter of fact it is currently it is accepting apps for the Windows Mobile 6.5 platform. If you already have a great smartphone-dedicated app, but you developed it for the iPhone and not Windows Mobile, Microsoft has now come out to announce details on how you can port that app to the Windows Mobile platform.
Microsoft Dynamics ISV Architect Evangelist, John O’Donnell, comments: “With Microsoft Mobile devices running version 6.5 of our mobile OS coming to the market towards the end of the year, now is the time to be thinking about porting your iPhone applications to Windows Mobile. With the launch of our Mobile Marketplace you will not only be able to build a compelling application but also have a place to market it. With many millions of Windows Mobile devices already in the marketplace there cannot be a better time to get start in Windows mobile development but where do you start?”
Microsoft has published a technical article on MSDN entitled “Porting the Amplitude Application from the iPhone to a Windows Mobile Device – a Case Study” which presents in much details what a developer has to go through when porting an iPhone app to Windows Mobile. In this case the app is called Amplitude – it detects sounds, amplifies them and turns them into a graphical representation.
Perhaps we should stop using the term “Windows Mobile” and start using “Windows Phone.” Why, you ask? Simply because news has come to light that Microsoft will ditch Windows Mobile and rebrand it as Windows Phone. The change applies to previous Windows Mobile platforms, like Windows Mobile 6.0 and 6.1, as well as the upcoming Windows Mobile 6.5. To put it bluntly, Windows Mobile is out, Windows Phone is in.
According to Microsoft, the rebranding is meant to depict how a PC user enjoys the same Windows experience when he uses the PC as well as when he uses Windows Phone. For the time being the Windows Mobile brand will be kept as a means to identify the OS version, but the end goal is to reach a point where a customer can simply walk into a store and say something like “I want a Windows Phone.”
Microsoft Dynamics ISV Architect Evangelist, John O’Donnell, comments: “With Microsoft Mobile devices running version 6.5 of our mobile OS coming to the market towards the end of the year, now is the time to be thinking about porting your iPhone applications to Windows Mobile. With the launch of our Mobile Marketplace you will not only be able to build a compelling application but also have a place to market it. With many millions of Windows Mobile devices already in the marketplace there cannot be a better time to get start in Windows mobile development but where do you start?”
Microsoft has published a technical article on MSDN entitled “Porting the Amplitude Application from the iPhone to a Windows Mobile Device – a Case Study” which presents in much details what a developer has to go through when porting an iPhone app to Windows Mobile. In this case the app is called Amplitude – it detects sounds, amplifies them and turns them into a graphical representation.
Perhaps we should stop using the term “Windows Mobile” and start using “Windows Phone.” Why, you ask? Simply because news has come to light that Microsoft will ditch Windows Mobile and rebrand it as Windows Phone. The change applies to previous Windows Mobile platforms, like Windows Mobile 6.0 and 6.1, as well as the upcoming Windows Mobile 6.5. To put it bluntly, Windows Mobile is out, Windows Phone is in.
According to Microsoft, the rebranding is meant to depict how a PC user enjoys the same Windows experience when he uses the PC as well as when he uses Windows Phone. For the time being the Windows Mobile brand will be kept as a means to identify the OS version, but the end goal is to reach a point where a customer can simply walk into a store and say something like “I want a Windows Phone.”
