Android smart phone hybrid application

• Environment setup
  • Setting up the project
  • WebSphere Commerce prerequisites
  • Installing APK files
  • Third-party application dependencies
• System architecture
  • Android operating system architecture
  • WebSphere Commerce Android hybrid application architecture
  • StoreWebViewController
  • JavaScript bridge
• Native features in the hybrid application
  • Mobile application flows
• Application and directory structure
  • Overview of the package structure
  • Android Manifest file
  • Permissions
  • Source files
  • Application Resource files
  • WebSphere Commerce files

• Android devices must install the Barcode Scanner application by ZXing Team from Google Play for the barcode scanning page to function correctly.
• Android devices must install the Voice Search application by Google Inc. from Google Play for the voice search page to function correctly.

Control web content returned from the server

The User Agent in the HTTP head specifies the hybrid application.

WebSphere Commerce allocates the special device ID. The hybrid application ID is -21.

Page headers and footers are removed from the response.

Animation

Animation effects mimic native applications with transitions between back and forward page navigation.

Gesture

Gestures enable shoppers to flip through catalog pages in the storefront.

1. The JSP file calls the JavaScript function.
2. The JavaScript calls the Android function.
3. The hybrid application implements the Android function.
4. The Android function invokes the native capabilities.

• mobile20\AndroidHybrid\javascript\DeviceEnhancement.js
• mobile20\AndroidHybrid\include\styles\style1\CachedHeaderDisplay.jsp
• mobile20\Snippets\StoreLocator\ViewMap.jspf
• mobile20\ShoppingArea\CheckoutSection\OrderShippingBillingDetails.jsp
• mobile20\Snippets\StoreLocator\GPSSupport.jspf
• mobile20\UserArea\AccountSection\RegistrationSubsection\UserRegistrationUpdateForm.jsp
• mobile20\include\JSTLEnvironmentSetup.jspf

• Madisons-AndroidHybridMobile\src\com\ibm\commerce\android\hybrid\mobile\web\JavaScriptInterface.java

• Hybrid shell (Header, tabs, search, menu button) throughout the application.
• Barcode scanner on the barcode scanning page.

  The barcode scanner can scan 2D QR coded URLs (for example, product page URLs) of the same WebSphere Commerce server specified in the hybrid application configuration. Scanning any URLs of a different server results in navigating to the URL using the default Android Web browser, instead of displaying the content within the hybrid application.

• Voice search on the product search page.
• Address book integration for importing contacts into the account address book.
• Store locator and Google Maps integration on the store locator.

src

Contains Java source files.

gen

A Java source directory for files generated by the Android platform.

res

Contains all external resources used by the application.

General

Minimum SDK level.

Application

Register activities.

Permissions

Access that must be granted for the application to run.

The permissions must be accepted by the user before the application can be installed.

Instrumentation

Profiling information used during development and testing.

android.permission.INTERNET

Requests access to use the Internet from within the application.

android.permission.CLEAR_APP_CACHE

Requests permission to clear the application cache.

android.permission.WRITE_EXTERNAL_STORAGE

Requests permission to write to the external SD card.

android.permission.CAMERA

Requests permission to launch the camera application (for barcode scanner).

android.permission.READ_CONTACTS

Requests permission to read the contact information on the phone book.

android.permission.ACCESS_COARSE_LOCATION

Requests permission to use the location manager to detect location based on network.

android.permission.ACCESS_FINE_LOCATION

Requests permission to use location manager to detect location based on GPS.

android.permission.ACCESS_MOCK_LOCATION

Requests permission to use mock location providers for testing

android.permission.ACCESS_LOCATION_EXTRA_COMMANDS

Requests permission to access extra location provider commands.

<uses-library android:name="com.google.android.maps"/>

<string name="map_api_key"></string>

res/drawable

Contains client-side images and pictures used by the application.

res/layout

Contains the user interface layout files used to render each screen of the application. The layout files are stored in XML format. See Android Developers: User Interface for more information.

res/values

Contains XML files that are mainly name-value pairs. These XML files declare arrays, styles, colors, and strings that are used by the application. Files such as strings.xml and arrays.xml are translated into other languages and enable the application to use language-specific strings at runtime.

The system_settings.xml must be customized to contain the minimal set of default properties:

storeName

The store identifier.

hostName

The host name of the WebSphere Commerce Web Server.

storeId

The store ID (STOREENT.STOREENT_ID) of the store.

storeIdentifier

The string used for SEO-enabled URLs. If this field is empty and the catalogId is not empty, the catalogId is used to look up the initial catalog.

catalogId

The catalog ID associated with the preceding store identifier SEO string If the SEO string is empty, this optional catalog ID can be configured to load the initial catalog.

map_api_key

The Google Maps API key.

Note: One key cannot be shared across multiple Android development environments.

res/xml

Contains XML files that are used to define preferences for the application.

res/anim

Contains predefined animations used by the application.