Mobile Widgets Business Issues

Slide 1: Mobile Widgets: 2008 4th April 2008 Scott Weiss scott.weiss@humanfactors.com Desk +44.0.207.290.3432 or Mobile +44.0.7717.413.379

Slide 2: Widgets: Definition • Small, vector graphic, data-capable, handset-resident, persistent data applications (at least within the widget environment, which can be the idle screen of the phone)‫‏‬ • Client-server optional © 2008, Human Factors International Mobile Widgets 2

Slide 3: Deep Integration or Just RSS Readers?  Presence  Contacts Deep Integration  Security? RSS-Enabled  Malware? Widgets Email Calendar Extranet Non-Resident Personal/Enterprise Information © 2008, Human Factors International Mobile Widgets 3

Slide 4: Requirements • Cache Memory • Internet Access • UI Support • Maintenance—Versioning – Engine – Policy – Widget-based – Pull, not Push! © 2008, Human Factors International Mobile Widgets 4

Slide 5: Ecosystem Model • Will Consumers Create Widgets? NO • Should widgets be customizable? YES • URLs: Too long to type in • Widgets should be acquirable from the engine • Widgets should be side-loadable © 2008, Human Factors International Mobile Widgets 5

Slide 6: Widgets: Value Chain Store Front Advertiser Payment Handlers Advertising Platform Manufacturer Consumers Operating Authoring System Technologies Content Owners Certification Developers Body Platform Operator Vendor © 2008, Human Factors International Mobile Widgets 6

Slide 7: Operator-Oriented Value Chain Operator: Pay to Play: • Store Front • Developer • Brand • Advertiser • Platform Authoring Content • Ad Platform Operating System • Certification Consumer Manufacturer • Payments © 2008, Human Factors International Mobile Widgets 7

Slide 8: Data: Policy Required • No Consensus: • Budgeted or Disposed When Inactive? • Cost (Flat Rate?)? • Battery Issues • Network Impact © 2008, Human Factors International Mobile Widgets 8

Slide 9: Security vs. Trust • No guaranty • OS-Enabled • Device Integrity: No Crashing • Network Integrity: No Malware Security is a key differentiator in the • No Disruptions competitive landscape. • No Central Authority? OMA? Security policies are needed by the market place. © 2008, Human Factors International Mobile Widgets 9

Slide 10: Interoperability © 2008, Human Factors International Mobile Widgets 10

Slide 11: Shared Music Experience A B Cowboy Crazy © 2008, Human Factors International Mobile Widgets 11

Slide 12: Widget vs. Application Widget Application  Single/Partial Screen  Multi-Screen  More Client-Server  Stand-alone/ Client Server  Narrow Functionality  One at a Time/Full-Screen  Faster/Easier Access  Rich Functionality  NotePad  Word Processor  Notifier (Mailbox Flag)‫‏‬  Email or IM  Alarm/Next Appointment  Calendar  Friend, etc. Finder  Map © 2008, Human Factors International Mobile Widgets 12

Slide 13: Who Wins? • Nokia • Qualcomm Engine must support easy acquisition of new content! • Opera • Openwave • Plusmo Fears about interests: manufacturers don't • W3C want to buy from other manufacturers, and • ... GSM operators fear further involvement with Qualcomm. Plusmo is an unknown— where are their proven successes with security? And so it's Openwave and Opera that offer the best promise for widget frameworks. They are solid, secure companies with known interests. © 2008, Human Factors International Mobile Widgets 13

Slide 14: Thank you. Scott Weiss Scott.weiss@humanfactors.com