Pocket Outlook Object Model Application Development
A version of this page is also available for
The Pocket Outlook Object Model (POOM) API is a COM-based library that provides programmatic access to Personal Information Manager (PIM) data on mobile devices. It provides functionality for manipulating PIM-item collections and folders. This section contains topics that explain how the object model is structured, its design objectives, the similarities and differences between it and its desktop counterpart; and how you can interface your custom application with it.
In This Section
- Design Goals for the Pocket Outlook Object Model
Describes the POOM design philosophy.
- Basic Object Model
Illustrates the POOM architecture.
- Differences Between the Pocket Outlook Object Model and the Outlook Object Model
Describes the differences between the Outlook object model and the Pocket Outlook Object Model.
- Integrating Applications with Outlook Mobile
Outlines the structure of the Pocket Outlook Object Model, and explains how the pieces fit together.
- Customizing the PIM User Experience
Describes how you can change the look of the PIM applications, and how to launch them straight into the New Item card.
Windows® phones include a messaging sub-system for sending, receiving, storing, and manipulating e-mail and Short-Message Service (SMS) text messages. The Microsoft messaging client application, Messaging (formerly Inbox), provides the user interface for creating and reading messages, and for accessing and manipulating the message items in local and remote message stores. The Windows Mobile version of the Messaging API (MAPI) is a COM-based library that provides programmatic access to this functionality. It mirrors the Microsoft Exchange Server version of MAPI, but has a smaller scope of functionality to accommodate the practical constraints of mobile devices.