Microsoft’s Smartphone and Future Trends in Handheld Computing. Sandeep Sibal Technologist <[email protected]>. May 21, 2003 Planet PDA Sheraton Ferncroft Resort Danvers, Massachusetts. Microsoft’s Smartphone Why build a Smartphone? Smartphone as PPC successor Smartphone Platform
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Why build a Smartphone?
Smartphone as PPC successor
Using Web Services
Obstacles to Dominance
Future Handheld Trends
The Magic Wand?
New Products and Services
Disclaimer: This presentation does not reflect Microsoft or any other company’s views.
Available later this year:Smartphone 2003 (powered by WinCE 4.2) has .NET Compact Framework shipping in ROM; Bluetooth; and support for a built-in camera.
Many familiar Win32 APIs reused: Winsock, TAPI etc.Desktop and PocketPC apps can run on the Smartphone with modificationsApps written for GSM networks may be re-run on CDMA networks
Very similar to building apps on Win32 or WinCE except that .NET (Compact) Framework functionality is missing. Since a SOAP Toolkit is unavailable, the following classes need to be built:
Example architecture of a Map Mobile Web services
Europe Handheld 1Q 2003 Mkt:
PDA (WinCE): 320 K
Smartphone (Win CE): 60 K
“Smartphones” (all**): 860 K
Palm: 285 K
Operators and countries*:
Europe Handheld 2003 Mkt Est.
Symbian/Smartphone: 3.3 million
*the list of operators is possibly incomplete
**this category includes Symbian handhelds
Short to mid term:
Mid to long term:
Widely varying analyst predictions over the next few years:from leadership to annihilation!
Cross-functional value of integrating functionality is significant.Market for PDAs is stagnant, but for telephony-enabled smartphones is rising!
These fundamental limitations bound what will be possible in the future on handhelds
*See the W3C Multimodal Interaction Working Group for efforts to standardize such interfaces. Also see Kirusa’s website for demonstrations of multimodal interfaces on various handhelds.
Unlike a computer, you “wear” your handheld all the time. It is a personal statement of who you are. Its look and feel are therefore very critical.
Some aspects are:
Moore’s law and the maturation of existing and future scientific discoveries & inventions will substantially improve the handheld’s capabilities with respect to:
Fused into the handheld (e.g., Camera-phones)
Expansion slots (e.g., CF slots)
Personal Area Network (e.g., Bluetooth). See IXI’s PMG.
Promiscuous binding with surrounding capabilities (Project Oxygen)
How will these architectures evolve?
Location of Computation
Embedded (computed locally in the handheld). Can operate in disconnected mode. Limited by CPU, memory, battery power.
Network (computed in network). More compute resources but limited by connectivity, bandwidth & latency.
Distributed. Part-embedded, part-network based. (e.g., Distributed Speech recognition)
How will these architectures evolve?Emerging Architectures