MOBILE APPs DEVELOPMENT PLATFORMS

  • Published on
    14-Dec-2014

  • View
    41

  • Download
    3

DESCRIPTION

This ppt contains the topic like,, Java 2 Platform, Micro Edition (J2ME) - Wireless Markup Language (WML) - Compact HyperText Markup Language (cHTML) - eXtensible HyperText Markup Language (XHTML)

Transcript

<ul><li> 1. Workshop on Mobile Services and Android Applications MOBILE APPs DEVELOPMENT PLATFORMS S. Amirtharaj </li> <li> 2. Topic: MOBILE APPs DEVELOPMENT PLATFORMS MOBILE APPs DEVELOPMENT PLATFORMS - Java 2 Platform, Micro Edition (J2ME) - Wireless Markup Language (WML) - Compact HyperText Markup Language (cHTML) - eXtensible HyperText Markup Language (XHTML) </li> <li> 3. An Overview of J2ME Technology </li> <li> 4. Topic: MOBILE APPs DEVELOPMENT PLATFORMS JavaTM 2 Platform, Micro Edition (J2ME) What is J2ME? The JavaTM 2 Platform, Micro Edition (J2ME) is the Java platform for consumer and embedded devices such as mobile phones, PDAs, TV set-top boxes, in-vehicle telematics systems, and a broad range of embedded devices. Like its enterprise (J2EE) and desktop (J2SE) and smart card counterparts, the J2ME platform is a set of standard Java APIs defined through the Java Community ProcessSM by expert groups that include leading device manufactures, software vendors and service providers. What J2ME provide you? 1. It delivers the power and benefits of Java technology tailored for consumer and embedded devices (a flexible user interface, robust security model, broad range of built-in network protocols) 2. It supports for networked and disconnected applications. 3. It allows you to write applications once, and download them dynamically and leverage each devices native capabilities. </li> <li> 5. Topic: MOBILE APPs DEVELOPMENT PLATFORMS J2ME Architecture Optional Packages Personal Profile Personal Basis Profile Foundation Profile Connected Device Configuration (CDC) JVM Mobile Phones &amp; Entry-level PDAs Optional Packages MDP Connected Limited Device Configuration (CLDC) KVM High-end PDAs TV set-top boxes Embedded devices </li> <li> 6. Topic: MOBILE APPs DEVELOPMENT PLATFORMS J2ME Architecture J2ME architecture defines configurations, profiles, and optional packages as elements for building complete Java runtime environments Meet the requirements for a broad range of devices and target markets. Each combination is optimized for the memory, processing power, and I/O capabilities of a related category of devices. The result is a common Java platform that fully leverages each type of device to deliver a rich user experience. Three types of basic elements: Profiles provide a complete runtime environment targeted at a specific device categories. Configurations provide the base functionality for a particular range of similar devices. Optional packages provide a base for further extension based on related setting. </li> <li> 7. J2ME CLDC &amp; CDC Connected Limited Device Configuration (CLDC): - CLDC is the smaller of the two configurations. - It is designed for devices with intermittent network connections, slow processors and limited memory. Typical examples: - Mobile phones Two-way pagers PDAs, - These devices typically have either 16-bit or 32-bit CPUs, and a minimum of 128 KB to 512 KB of memory for the Java platform implementation and associated applications. Connected Device Configuration (CDC): - CDC is designed for devices that have more memory, faster processors, and greater network bandwidth, such as - TV set-top boxes, residential gateways, two-way pagers, POS terminals - in-vehicle telematics systems, and high-end PDAs. CDC includes a full-featured java virtual machine (JVM), and a much larger subset if the J2SE platform than CLDC. - Most CDC-targeted devices have 32-bit CPUs and a minimum of 2MB of memory. Topic: MOBILE APPs DEVELOPMENT PLATFORMS </li> <li> 8. Topic: MOBILE APPs DEVELOPMENT PLATFORMS J2ME CDC Connected Limited Device Configuration (CLDC) Key Features: - Easily implemented by consumer electronics and embedded device manufactures. - Comes with a JavaTM virtual machine (JVM), class library, APIS, and Foundation Profile. - Standardized by the Java Community ProcessTM program for devices with 2MB or more memory. - Devices currently using the Personal JavaTM application environment can be ported to CDC. - CDC VM is built with the same specification as the Java 2 platform, standard edition (J2SETM) virtual machine. - Available today as a free download. - The CDC is a class library with a minimal set of APIs from J2SETM, including java.lang VM system classes java.util underlying java utilities java.io java File I/O java,.net UDP datagram and File I/O java.text bare minimal support for error messages java.security minimal fine-grain security and encryption for object serialization </li> <li> 9. Topic: MOBILE APPs DEVELOPMENT PLATFORMS J2ME Profiles J2ME Profiles: Provide a complete runtime environment targeted at specific device categories, configurations. A) Mobile Information Device Profile (MIDP): -It is designed for mobile phones and entry-level PDAs. -It offers the core application functionality required by mobile applications, including a) user interface, b) network connectivity c) local data storage, d) application management B) Foundation Profile (FP): - CDC profiles are layered so that profiles can be added as needed to provide application functionality for different types of devices. - It is the lowest level of profile for CDC. - It provides a network-capable implementation of CDC that can be used for deeply embedded implementations without a user interface. - It can also be combined with Personal Basis Profile and Personal Profile for devices that require a graphic user interface (GUI). </li> <li> 10. Topic: MOBILE APPs DEVELOPMENT PLATFORMS J2ME Profiles C) Personal Profile (PP): - PP is the CDC profile aimed at devices that require full GUI or Internet applet support, such as high-lend PDAs, communicator-type devices, and game consoles - It includes the full Java Abstract Window Toolkit (AWT) libraries and offers Web fidelity, easily running Web-based applets designed for use in desktop environment. - It replaces Personal JavaTM technology and provides Personal Java applications through J2ME platform. D) Personal Basis Profile (PBP): - PBP is a subset of PP. - It provides an application environment for network connected devices that support a basic level of graphic presentation or require the use of specialized graphical toolkits for specific applications. -Typical device examples are: TV set-top boxes, in-vehicle telematics systems, -And information kiosks. -Both PP and PBP are layered on top of CDC and FP. </li> <li> 11. Topic: MOBILE APPs DEVELOPMENT PLATFORMS J2ME Optional Packages Optional Packages: - PP is the CDC profile aimed at devices that require full GUI or Internet applet support, such as high-lend PDAs, communicator-type devices, and game consoles - It includes the full Java Abstract Window Toolkit (AWT) libraries and offers Web fidelity, easily running Web-based applets designed for use in desktop environment. - It replaces Personal JavaTM technology and provides Personal Java applications through J2ME platform. </li> <li> 12. Topic: MOBILE APPs DEVELOPMENT PLATFORMS J2ME MIDP Architecture Optional Packages Game User Interface Media Application Management End-to-End Security CLDC KVM Local Data Storage Push Registry Connectivity OTA Provisioning MIDP </li> <li> 13. Topic: MOBILE APPs DEVELOPMENT PLATFORMS Mobile Information Device Profile (MIDP) The MIDP combined with CLDC, is the javaTM runtime environment for todays mobile information devices such as phones and entry level PDAs. - MIDP is defined by through the Java Community ProcessSM program - MIDP defines a platform for dynamically and securely delivering highly graphical, networked applications to mobile information devices. - MIDP provides the core application functionality required by mobile applications as a standardized java runtime environment and set of java APIs. - Using MIDP, developers can write applications once that are optimized for todays mobile information devices. Deployment Status: - It has been widely adopted as the platform of choice for mobile applications. - It is deployed globally on millions of mobile phones and PDA, supported by leading Java technology integrated development environment (IDE). </li> <li> 14. Topic: MOBILE APPs DEVELOPMENT PLATFORMS Mobile Information Device Profile (MIDP) MIDP is designed for mobile users: - Allow them to write networked applications for mobile devices. - These mobile applications can be download dynamically and run on the mobile devices. - They can be easily updated and removed by the end user. Mobile user interface support based on a high-level user interface API. This helps developers to build easy to use, highly graphical and portable applications optimized for mobile information devices. MIDP user interface functionality includes: - Pre-defined screens for displaying and selecting lists, editing text, popping up alert dialogs, and adding scrolling tickers. - Each form (or screen) can include any no. of predefined items images, ready-only text fields, editable text fields, editable date and time fields, charts, and choice groups as well as any custom items added by developers - All screens and items are device-aware with built-in support for the native display size, input and navigation capabilities. portable and flexible. </li> <li> 15. Mobile Information Device Profile (MIDP) Multimedia and Game Functionality MIDP is ideal for building portable games and multimedia applications. - A lower level user interface API provides developers great control of graphics and inputs when they need it. - A game API adds game-specific functionality, such as sprites and tiled layers that takes advantage of native device graphics capabilities. - Built-in audio provides support for tones, tone sequences and WAV files. - Mobile Media API (MMAPI) can be used as an optional package for MIDP to add video and other rich multimedia content. Over-the-Air Provisioning - The MIDP specification defines how MIDP applications are discovered, installed, updated and removed on mobile information devices. - The MIDP also enables a service provider to identify which MIDP applications will work on a given device. - Its OTA Provisioning model has been defines to delivery a reliable, secure provisioning solution. Topic: MOBILE APPs DEVELOPMENT PLATFORMS </li> <li> 16. Topic: MOBILE APPs DEVELOPMENT PLATFORMS Mobile Information Device Profile (MIDP) Extensive Connectivity enable developers to fully leverage the native data network and messaging capabilities of mobile information devices. - It supports leading connectivity standards: HTTP, HTTPS, datagram, sockets, server sockets, and serial port comm. It also supports the Short Message Service (SMS0 and Cell Broadcast Service (CBS) capabilities of GSM and CDMA network through the Wireless Messaging API (WMA) optional package. - It supports a server push model. A push registry keeps track of applications registered to receive inbound information from the network. When information arrives, the device decides if to start the application based on user preference. The push architecture enables developers to include alerts, messaging and broadcasts in MIDP applications, and leverage the event-driven capabilities of devices and carrier network. </li> <li> 17. Topic: MOBILE APPs DEVELOPMENT PLATFORMS Mobile Information Device Profile (MIDP) End-to-End security based on a robust security model (with open standards) to protect the network, applications and mobile information devices. - The use of HTTPS leverages existing standards such as SSL and WTLS to enable the transmission of encrypted data. - By default MIDP applications are not trusted, and are assigned to untrusted domains that prevent access to any privileged functionality. - To gain privileged access, a MIDP application must be assign to a specific domains that are defined on the mobile device, and are properly signed using the X.509 PKI security standard, installed and granted associated permissions. It must be successfully authenticated. </li> <li> 18. An Overview of cHTML Markup Language </li> <li> 19. An Overview of cHTML Markup Language What is the Compact Markup Language (cHTML)? Similar to WML and XHTML, cHTML is another thin markup language. It is a well-defined subset of the HTML(2.0, 3.2, and 4.0) specifications. It can be viewed as a content description language to generate pages for iMode devices. Objective of cHTML: 1. It was designed for small information...</li></ul>

Recommended

View more >