Upload
roderick-warren
View
214
Download
0
Tags:
Embed Size (px)
Citation preview
Wireless Applications
PersonalPersonalTime and Time and KnowledgeKnowledgeManagemntManagemnt
Personal Personal Health &Health &SecuritySecurity
Personal Personal NavigationNavigation
Remote Remote Monitoring &Monitoring &ControlControl
Citizen Citizen ServicesServices
EntertainmentEntertainmentEdutainmentEdutainmentLearningLearning
E-commerceE-commerce
Social Social NetworksNetworks
WorkWork
Thin-client vs. smart-client
sms, mmshtml
J2ME, C++C#, Objective-C,flashlite,
applications
applications
Browsing
InternetWeb Browser
Web Server
User requests Document
Web server returns document data to web browser
Database Servers
web server looks for document
web server retrieves document
microBrowser
How many of us own…
• a car 800M
• Fixed Telephone 1.3B
• TV 1.5B
• Credit card 1.3B
• Mobile phone ?
• PC ?
How many of us own…
• a car 800M
• Fixed Telephone 1.3B
• TV 1.5B
• Credit card 1.3B
• Mobile phone 4.6B
• PC 1.1B
Where are the successful mobile applications?
• Voice call
• Short message
• Ringing tone down load
• Some isolated vertical applications
Mobile applications are still very young.
• 1994 Sms • 1995 Sms value added services• 1997 Ringing tone down load• 2000 First Symbian phone • 2001 First browser phone• 2002 First java ME phone• 2003 Multimedia Message Service• 2006 Mobile TV• 2007 Near Field Communication
Overall User Experience Makes the Difference
• Genuine Need• Limited device capabilities are acceptable• Penetration• Pricing = cost vs. benefit (for all parties
involved)• Awareness • Distribution
Characteristics of Mobile Devices
• Limited Display
Keyboard
Power supply
• QoS (off-line capability)
• Location awareness
• Access to data (address books etc) and phones capabilities (camera, communication etc.)
Mobile Application Development
• Mobile Applications– Classifying mobile applications– Successful mobile application?– Mobile device characteristics
• Application development environments
Thin-client vs. smart-client
sms, mmshtml
J2ME, C++C#, objective-C, flashlite
applications
applications
Smartphones
• ”Open” OS vs. Proprietary OS– Phone manufacturer
own OS– Symbian– Windows Mobile– Linux
• Development Environment– Java– .NET– C++– Objective-C, Cocoa
Touch
Development Tools
• VB / C# (.NET)– Windows Mobile
• C++– Symbian
• Java– Symbian– Linux
• Objective-C– iOS
J2ME
develop java applicationsfor MIDP devices
Web/App Server
Transfer usingcable or wireless connections
Download from the server
Mobile developer’s nightmare
Distribution Reach Device Penetration
Ease
Of
Dev
Touch UI
Access to device capabilities
S60/C++ Not in US
Iphone/ObjC
Windows
Android
Java ME fragmented ?
Browser
Widgets
Flash lite
How to Choose the environment ?
• Geographical reach required?
• Multidevice support?
• Thick client needed?
• Which phone capabilities will be used?
• What environments is the project team familiar with ?
• Type of UI? Pen/no pen, Graphics intensitivity?
Windows Phone vendors
• Samsung• HTC• Ericsson• Motorola• Palm• I mate• HP• Dell• Toshiba• …
62 Windows mobile devices on the UK market (3/2009)
Three Ways for Mobile Windows
• Native code (C++, .DLL)– for high performance– direct hardware access– the smallest footprint.
• Managed code (C#, VB)– user interface-centric applications– fast time-to-market– rapid application development– easy access to Web services
• Server-side code – For wide range of devices