Familja Java dhe J2ME

Single source codebase written HTML 5, CSS 3, JavaScript running on a mobile browser embedded in a native app wrapper.

Device capabilities accessed through device-independent JavaScript API.

SUPPORTED PLATFORMS:

iOS, Android, Blackberry, WP7, Symbian, Palm, Samsung Bada

IDE USED:

MAC OS X & XCODE for iPhone & iPad.

Google Android SDK, Eclipse ADT Plugin, Ant as well as Eclipse IDE for Android.

STRENGTHS:

• STRENGTHS:

• Native wrapper source code is provided so it can be customized further.

• Simple ‘drop-in libraries’ concept makes it easier to develop.

• Lowers barriers of adoption for web developers.

• WEAKNESSES:

• Lack of support for native UI components, design patterns & development tools.

• The capabilities offered by the framework is limited to what a “WebView” can do.

• Different projects for different platforms

• Different JavaScript files on each platform for PhoneGap itself and plugins

• No native UI support

• Java, Objective-C or C# requirement to create new plugins

• No built-in support for push notifications

TECHNICAL ARCHITECTURE:

• TECHNICAL ARCHITECTURE:

• Cross compilation technique – Pre-compilation, front-end compilation, platform & package compilation.

• Single source codebase written in JavaScript, compiled into native code and packaged for different target platforms.

• Does not use browser engine to render user interface on mobile devices.

• Instead the UI elements are converted to true native UI elements when deployed to the phone.

• SUPPORTED PLATFORMS:

• iOS, Android, Windows & Blackberry

• IDE USED:

• Studio, an Eclipse-based IDE

STRENGTHS:

• STRENGTHS:

• Native code output very quick and fluid on the phone.

• Easy setup and startup for developers.

• Excellent documentation & examples.

• Strong community forum to find out answers.

• Intuitive app management environment.

• Support for desktop and tablet development

• WEAKNESSES:

• Potentially restrictive API’s

• Tries to solve too many problems in one shot supporting phones, tablets & desktops.

TECHNICAL ARCHITECTURE:

• TECHNICAL ARCHITECTURE:

• Cross compilation using Virtual Machine.

• Single source codebase written in C/C++ or HTML/JavaScript or a combination of both.

• C++ source code  platform-independent intermediate code  application package

• SUPPORTED PLATFORMS:

• iOS, Android, Windows Mobile, Moblin/MeeGo, Symbian & Blackberry

• IDE USED:

• MoSync IDE based on Eclipse.

STRENGTHS:

• STRENGTHS:

• Only one project structure for all the platforms.

• The same JavaScript file.

• Extend JavaScript functionality using C++ or Java and Objective-C

• Native UI support

• Built-in support for push notifications

• Target group: Both web developers looking to enter the mobile space, as well as the ordinary PC/Mac desktop developer with knowledge of C/C++.

• WEAKNESSES:

• No support for accelerometer or camera in most phones.

• Contains XML parsing libraries but lacking support for JSON or other data formats.

• Doesn’t provide support for MVC; requires little extra effort to create views for data.

Phone

• Phone

• Eclipse ( http://www.eclipse.org/downloads/ )

• Android Plugin (ADT)

• Android SDK ( http://developer.android.com/sdk/index.html )

• Install everything except Additional SDK Platforms, unless you want to

• Windows Users: may need to install Motorola Driver directly ( http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers )

Once installed open the SDK Manager

• Once installed open the SDK Manager

• Install the desired packages

• Create an Android Virtual Device (AVD)