Familja Java dhe J2ME

Separates build environment from target environment.

Platform-independent API using a mainstream programming language like JavaScript, Ruby or Java.

The cross-compiler then transforms the code into platform-specific native apps.

The software artifact generated can be deployed and executed natively on the device.

ADVANTAGES:

Improved performance and User Experience.

Full access to functionalities of underlying mobile OS and device specific capabilities.

DISADVANTAGES:

Highly complex as cross-compilers are difficult to program.

Need to be kept consistent with fragmented mobile platforms and operating systems available.

A virtual machine is used to abstract the target platform details from the application’s running code.

• A virtual machine is used to abstract the target platform details from the application’s running code.

• The framework provides both the API and runtime environment.

• The runtime executes on the mobile device and enables interoperability between the device’s OS and the mobile application.

• ADVANTAGES:

• Improved performance and User Experience.

• Full access to functionalities of underlying mobile OS and device specific capabilities.

• Portability: VM’s are easier to maintain & more flexible to extend.

• DISADVANTAGES:

• Slower due to runtime interpretation latency.

Use standard web technologies such as HTML 5, CSS 3 & JavaScript.

• Use standard web technologies such as HTML 5, CSS 3 & JavaScript.

• Features of HTML 5 - Advanced UI components, access to rich media types, geolocation services & offline availability.

• Increasing popularity of HTML 5 in rendering engines such as WebKit.

• Runs on a standalone mobile web browser.

• Installed shortcut, launched like a native app.

• UI logic resides locally; makes the app responsive and accessible offline.

• ADVANTAGES:

• Multiplatform support.

• Low development cost.

• Leverage existing knowledge.

• DISADVANTAGES:

• Limited access to OS API’s.

Combines native development with web technology.

• Combines native development with web technology.

• The web app runs inside a thin wrapper native app.

• The wrapper native app uses the OS API’s to create an embedded HTML rendering engine which provides a bridge between the browser and device API’s.

• The communication between web app and native app normally happens over JavaScript via custom built API’s.

• ADVANTAGES:

• Flexibility of web apps combined with feature richness of native apps.

• Simplified deployment and immediate availability.

• Leverage existing knowledge.

• DISADVANTAGES:

• Poorer user experience as compared to native apps.

• Access to advanced device capabilities normally restricted.

TECHNICAL ARCHITECTURE:

• TECHNICAL ARCHITECTURE:

• Cross compilation using Virtual Machine.

• Single source codebase written in Ruby and UI constructed using HTML 5, CSS 3, JavaScript running on Ruby interpreter on the device.

• Support for SQLite enables the local storage of relational data, enabling offline capabilities for both hybrid and native HTML 5 applications.

• DESIGN PATTERNS:

• Model-View-Controller pattern for maintainability and best practices.

• Object Relational Mapper design for easy data manipulation.

• SUPPORTED PLATFORMS:

• WM /WEHH , WinCE5.0+, Android 2.1+, iOS 3.0+, BB 4.6+, WP7

HTML 5 FEATURES:

• HTML 5 FEATURES:

• App Caching, WebSockets, WebWorkers, Local & Session Storage, SQLite, Semantic Elements, Form Attributes

• IDE USED:

• RhoStudio – An Eclipse based IDE

• STRENGTHS:

• Design patterns used.

• Applications look and behave identically on all devices.

• WEAKNESSES:

• Updating HTML/JavaScript code needs a complete rebuild.

• Need to know Ruby well, which is not as popular as other programming languages.

• Doesn’t generate source code, only native package which can restrict any further tweaking of the app.

TECHNICAL ARCHITECTURE:

• TECHNICAL ARCHITECTURE:

• Web approach using hybrid model.

•