---

Deliverables for analysis of mobile device interoperation with Chandler

---

PDA Platform Metrics

OSAF needs to understand what the mobile device will look like and how these devices will be used in 2004 and beyond in order to make decisions now on how Chandler should interoperate with these classes of devices and plan to incorporate the necessary architecture/infrastructure/APIs/etc. at appropriate points in the Chandler product road map.

We need to understand the convergence of PDAs and smart phones.

Parameters that may help us to decide what methods we should use to interoperate include:

Hardware

• Class of Devices
  • PDA
  • smart phone
  • future platforms?
• processor(s) (CPU performance/speed; functionality, i.e. built-in BlueTooth, 802.n, etc.)
• memory
  • RAM (performance, concurrent applications)
  • storage (non-volitol internal/removable, local Chandler repository/cache; sync. via memory card/stick transfer)
• Local bandwidth (sync through a wire (cradle/connector)or IRDa: serial, USB, 1394)
• WAN bandwidth (protocols: 802.n, BlueTooth, celphone nets); cost of service barriers (data service plans)?
• screen real estate

Software

• device operating systems (Palm, PocketPC, Symbian, mobile Linux, ...)
• programming tools [cross platform] (wxWindows, Python, Java, Covingo, iConverse )
• sync/communications protocols
  • Pocket PC: ActiveSync
  • Palm: HotSync Conduits
  • Phones: SyncML, SMS, TCP (POP, IMAP)
  • Redirectors (website push, client PC forwarding, email server/Exchange server forwarding)

Service providers (data service options)

• ISPs
• mobile phone companies

---

Chandler-side PDA Interoperation

Sync PDA built-in applications with Chandler Desktop

Web Browser interface to Chandler

PDA Client

• Full Chandler Client (replacement for built-in PIM applications)
• Chandler meta-data/outline browser to supplement built-in apps
• PDA built-in PIM apps. include: (do we sync and/or replace?)
  • email
  • contacts
  • calendar
  • To do
  • Notes
  • ...

Chandler technologies that may need to be on PDA

• Chandler Repository
• underlying stack
  • Python
  • wx tools

What about phones ?

• just how smart are they going to be in 2 years?
• convergence with PDA road map?

---

OSAF needs to identify

1. level of effort for the various interoperation approaches above
2. minimum functionality for interoperation (sufficient to lower barriers to adoption of Chandler in our early adopter target users)
3. what might be considered 'charming' functionality (for our early adopter target users that use smart phones or PDAs)
4. market state change forecasts (phase transition events)
5. ISP services/redirector software as an intermediary for data exchange from Chandler to mobile device

---

---

Pieter is going to ask his his contacts at various sources if they can provide any background info.

One source has volunteered to provide market sizing, segmentation, projection, and some of the other items of information the 1st week in October. (Too busy the end of Sept. to put the info together for us.-- PieterHartsook - 10 Sep 2003)

See notes from conversation re. SyncML here: PhoneMeetingOnSyncML20031015

---

Information it would be good to have...

1. any whitepapers
2. Size of Market by platform and projections: US, WW (can we subtract pure enterprise segment)
3. what % of users actually store/read email on their palm
4. Profile(s) of User/Use (excluding Enterprise/custom applications):
5. any applicable standards for API or data interchange
6. Open source projects for the platform
7. methods of interoperability: sync, desktop, data import/output
8. Commercial I/O products available
9. I/O libraries available
10. time horizon 1-2 years - changes in the above?
    • future User profile
    • internet connectivity modes (always on (how?)
    • IM on palm
    • integration with phone
    • will people store email on their PDA
    • where are the new high growth markets (coincident with Chandler market?)
    • changes in sync. technologies/process

---

PDA Platforms

• Palm
• PocketPC
• RIM

Identify typical use, needs, gaps, problems, for interoperation with Chandler. Identify basic (crawl before you walk) strategies for Canoga timeframe.

• import/ export
  • email
  • calendar
  • contacts
  • other (to do's, notes, etc.)
• cradle syncronization of data with Chandler
  • Palm conduits
  • PocketPC ?
  • RIM ?
• wireless sync of data with Chandler
  • redirectors from Chandler to carrier websites for push
    • T-Mobile/Cingular
    • ATT
    • Sprint
    • Verizon
  • direct connection (or VPN) to POP or IMAP
  • what about Calendar (bi-directional)
  • what about Contacts (bi-directional)

---

Page to collect external information on the market: PDAarticleCollection

---

PDA analysis project timetable/deliverables

Primary goal is to recommend what PDA/phone interoperability we need to provide for Chandler, particularly in the Canoga timeframe. We need both a minimal feature set as well a desired set. Secondary goal is a project timeline for delivering the following. I would expect that most of the questions can be answered with a reasonable degree of confidance by Oct. 20.

How does OSAF expect the mobile device landscape in 2005 to impact either the design or functionality of Chandler.

Create a framework for decision making regarding work to support this market. This framework would include:

• assumptions regarding the intersection of Chandler desktop functionality and the mobile device market.
• major trends in this market that will specifically effect Chandler design?*

In the handleld device ecosystem:

1. what devices/platforms do we need to interoperate with and why
2. how are we going to interoperate (sync, I/O)
3. what protocols/methods/APIs should we use
4. what resources/costs are associated with these
5. when do we need to engineer for this (timeline/roadmap)
6. what is the expected ROI/benefit derived from this cost

---

IRC conversation with "setuid", on 21 Nov 2003

• http://aloha.osafoundation.org/~jbotz/irc-logs/chandler.log.20031121

---

PieterHartsook - 12 Aug 2003

-- ElizabethGrigg - 25 Feb 2005

I would like to see the focus of PDA and phone interop/sync for chandler be on data entry. This is solving the use case of capturing calendar information discovered on the go and syncing it with the "cloud" without having to pause for T9 or graffiti. Data entry is a major hurdle for digitizing this information. Sync is only important if data entry is painful, but it doesn't solve the use case of new data. Ideas: barcode scanning, aliases, audio files with tagging, SMS.