Showing posts with label android. Show all posts
Showing posts with label android. Show all posts

Friday, March 3, 2017

Using Cordova Network API in gwt phonegap


The Network API provides access to the network connectivity information of the device, including wifi and cellular connection status.

Configuration


For using this API, you need to add Network Information plugin to your project.

cordova plugin add cordova-plugin-network-information
The network API can be accessed in gwt phonegap project as described below.

final PhoneGap phoneGap = GWT.create(PhoneGap.class);
Connection connection = phoneGap.getConnection();


The Network API is a very simple API and provides only 1 property/method and 2 events.


Usage


connection.type


Description


This provides the type of active network connection available. The possible connection types are :
  • Connection.UNKNOWN
  • Connection.ETHERNET
  • Connection.WIFI
  • Connection.CELL_2G
  • Connection.CELL_3G
  • Connection.CELL_4G
  • Connection.CELL
  • Connection.NONE

If the device doesn’t have a active network connection, then the connection type returned is NONE.

If the device has a active Wifi connection and a active 3G/2G/4G connection, then the connection type returned will be Wifi. The devices are designed to use the most efficient network when multiple active networks are available. Since the wifi is more efficient(more reliable, stable and cost effective), the devices normally use wifi even if other cellular connection types are available. If wifi is not available, then the device will check for the next efficient cellular connection type which normally will be in the sequence 4G,3G ,2G and CELL.

Sometimes, it is just not enough to known whether the device has active network connection or not. The application needs to know what is the connection type. You may have a user preference where user decides if the app can work on Cellular network or not. In this case, you need to check the connection type to match the user preference and allow the app to work in offline or not allow the user to launch if the connection type doesn’t match the user preference.

Code

String connectionType = connection.getType();


Supported Platforms


  • iOS
  • Android
  • Windows : When running on a emulator, the connection type is ETHERNET.


offline


Description


This event is fired when the device connected to the network is disconnected.


Code


The code for registering the offline event is below.
phoneGap.getEvent().getOffLineHandler().addOfflineHandler(new OffLineHandler() {
               
                @Override
                public void onOffLine(OffLineEvent event) {
               //Add your code here.
                }
            });


online


Description


This event is fired when the device is connected to the network.


Code


The code for registering the online event is below.
phoneGap.getEvent().getOnlineHandler().addOnlineHandler(new OnlineHandler() {
           
            @Override
            public void onOnlineEvent(OnlineEvent event) {
            //Add your code here.
            }
        });


Demo


The below example demonstrates usage of the Network API.

public class ConnectionDemo implements EntryPoint {
     private Logger log = Logger.getLogger(getClass().getName());
     private ScrollPanel scrollPanel = null;
     private LinkedList<String> list = null;
     private CellList<String> cellList = null;
     private Connection connection = null;
    
    /**
     * This is the entry point method.
     */
    public void onModuleLoad() {
         GWT.setUncaughtExceptionHandler(new GWT.UncaughtExceptionHandler() {

              @Override
              public void onUncaughtException(Throwable e) {
                Window.alert("uncaught: " + e.getLocalizedMessage());
                Window.alert(e.getMessage());
                log.log(Level.SEVERE, "uncaught exception", e);
              }
            });

            final PhoneGap phoneGap = GWT.create(PhoneGap.class);
            phoneGap.addHandler(new PhoneGapAvailableHandler() {
              @Override
              public void onPhoneGapAvailable(PhoneGapAvailableEvent event) {
                    createUI(phoneGap);
              }
            });

            phoneGap.addHandler(new PhoneGapTimeoutHandler() {
              @Override
              public void onPhoneGapTimeout(PhoneGapTimeoutEvent event) {
                Window.alert("can not load phonegap");

              }
            });
            phoneGap.initializePhoneGap();
    }
    private void createUI(final PhoneGap phoneGap) {
        try {
            scrollPanel =  new ScrollPanel();
            list = new LinkedList<String>();
            BasicCell<String> cell = new BasicCell<String>() {

                @Override
                public String getDisplayString(String model) {
                    return model;
                }
            };
             cellList = new CellList<String>(cell);
            scrollPanel.add(cellList);
             connection = phoneGap.getConnection();
            addInfo("Connection Type : ");
            phoneGap.getEvent().getOnlineHandler().addOnlineHandler(new OnlineHandler() {
               
                @Override
                public void onOnlineEvent(OnlineEvent event) {
                    addInfo("online and connection Type : ");
                }
            });
            phoneGap.getEvent().getOffLineHandler().addOfflineHandler(new OffLineHandler() {
               
                @Override
                public void onOffLine(OffLineEvent event) {
                    addInfo("Offline and connection Type : ");
                }
            });
            RootPanel.get("ConnectionDemo").add(scrollPanel);
        } catch (Exception e) {
            e.printStackTrace();
        }
    }
   
    private void addInfo(String type) {
        list.add(type+connection.getType());
        cellList.render(list);
        scrollPanel.refresh();
    }
}


Test


For testing, I will run this app in both iPhone 6 and Nexus 6P devices. The test steps are below.
  1. The app is launched when the device is connected to wifi and there is no cellular connectivity.
  2. Then the wifi is disabled and since there is no cellular connectivity, the device is in offline mode.
  3. The wifi is enabled.
  4. The wifi is again disabled.
  5. The cellular connectivity is enabled.
  6. The cellular connectivity is disabled.


Android Device


image

iOS Device



image

The code is available on the github.

Monday, February 27, 2017

Using Cordova Device API in gwt phonegap

 
Cordova Device API provides access to the device hardware and software information like what is the OS the device is running, its OS version and Serial id etc..

Configuration


This is a global object and is accessible any time after the deviceready event is triggered.

For using this API, you need to add the Cordova Device Plugin to the project.
cordova plugin add cordova-plugin-device
After your app is launched, include the below code to use any Apache Cordova API’s in the project.
final PhoneGap phoneGap = GWT.create(PhoneGap.class);
The Device API can be used only after the deviceready event is fired. So once your app is launched check for PhoneGapAvailableEvent. This event is fired once the Cordova library is successfully loaded and is ready for use.
    phoneGap.addHandler(new PhoneGapAvailableHandler() {
              @Override
              public void onPhoneGapAvailable(PhoneGapAvailableEvent event) {
                   // start your application code here.              }
            });
The Device API can be accessed through the Device object. The Device Object can be accessed as below

Device device = phoneGap.getDevice();

Usage


platform


Description


This property returns the operating system the device is running.
iOS devices return iOS while the Android devices return Android.

Code

String platform = device.getPlatform();

Supported Platforms


  • Android
  • iOS
  • Windows

version


Description


This property returns the device Operating system version number.

Code

String version = device.getVersion();

Supported Platforms


  • Android
  • iOS
  • Windows

cordova


Description


This property provides information of the platform specific cordova version running on the device. The cordova version and platform specific cordova  versions may be different. The cordova version displayed when you use cordova –v is the Cordova tooling and CLI version installed on your development machine.The cordova version may be 6.1, but the android platform cordova version may be 5.1 and ios platform cordova version may be 4.1. This platform specific Cordova version is the version of the cordova.js file in each platform. To get the platform specific version information from Cordova CLI, use the below command.
cordova platform list

image_thumb1


Code

String cordovaVersion = device.getPhoneGapVersion();

Supported Platforms


  • Android
  • iOS
  • Windows

model


Description


This property provides the information about the device model or product. This value is set by the manufacturer and may vary across the versions of the same product and these may not be well known names.
Ex: iPhone 6 is iPhone7,2.
On Android, this returns the product name instead of the device model.
The list of android devices product names mapping to common names is available at the below location.
https://support.google.com/googleplay/answer/1727131
And a similar list for iOS devices is available at the below url.
http://www.everyi.com/by-identifier/ipod-iphone-ipad-specs-by-model-identifier.html

Code

String model = device.getModel();

Supported Platforms


  • Android
  • iOS
  • Windows

manufacturer


Description


This property returns the name of the manufacturer of the device.
Ex: For iPhone, it would be Apple and for Samsung Galaxy Note, it would be samsung etc.

Code

String manufacturer = device.getManufacturer();

Supported Platforms


  • Android
  • iOS
  • Windows

uuid


Description


This property returns the device UUID(Universally Unique Identifier). The process of generating this UUID is different for different OS and is determined by the manufacturer.

On Android, uuid is a 64 bit integer created on first boot which is returned as string.

On iOS,uuid is created when a app from a vendor is installed. It will be same for all the apps from the same vendor. But if all the apps from the same vendor are reinstalled, then uuid will be recreated and will be different from the earlier one.

Code

String uuid = device.getUuid()

Supported Platforms


  • Android
  • iOS
  • Windows

serial


Description


This property returns the hardware serial number of the device, if available. Works only on physical devices since the emulators doesn’t have serial number.

Code

String serial = device.getSerial()

Supported Platforms


  • Android only.

isVirtual


Description


This property indicates whether the app is running on an emulator or an actual physical device.


Code

boolean isVirtual = device.isVirtual();

Supported Platforms


  • Android
  • iOS
  • Windows

Demo


The below example demonstrates the usage of the Device functions described above.

FlowPanel container = new FlowPanel();
Form widgetList = new Form();
widgetList.setHeader(new Label("Device"));
Device device = phoneGap.getDevice();
widgetList.add(new FormEntry("Platform", createTextBox(device
        .getPlatform())));
widgetList.add(new FormEntry("OS Version", createTextBox(device
        .getVersion())));
widgetList.add(new FormEntry("Cordova Version",
        createTextBox(device.getPhoneGapVersion())));
widgetList.add(new FormEntry("Model", createTextBox(device
        .getModel())));
widgetList.add(new FormEntry("Manufacturer", createTextBox(device
        .getManufacturer())));
widgetList.add(new FormEntry("Name",
        createTextBox(device.getName())));
widgetList.add(new FormEntry("Serial", createTextBox(device
        .getSerial())));
widgetList.add(new FormEntry("UUID",
        createTextBox(device.getUuid())));
widgetList.add(new FormEntry("Is Virtual", createTextBox(String
        .valueOf(device.isVirtual()))));
container.add(widgetList);
RootPanel.get("DeviceDemo").add(container);

The result of the program when it is run on different devices is as below.

Android emulator


g1_thumb1

On the Android emulator, since the manufacturer and the serial are displayed as unknown since this is a virtual device. As you can observe the device is indicated as a virtual device. Since the name of the device property is depreciated, the name value is not displayed.

Android Genymotion emulator


g2_thumb1

On a Genymotion Android emulator, the manufacturer is indicated as ‘Genymotion’ and there is no serial number as this is a virtual device and the serial number is derived from the hardware.
And similar to the other Android emulator, the device is indicated as a virtual device.
The model of the device selected in the Genymotion configuration is indicated as the model.
And the name of the device is depreciated and so no information is displayed against that.

Samsung device


Screenshot_2016-04-28-19-13-33_thumb

When the same program is run on an actual Samsung device, you see slightly different results.
The virtual status is returned as false, indicating that the device is an actual physical device.
The serial number is available since this is a real physical device.
The manufacturer name is displayed as ‘samsung’, since this is a samsung device.
The model of this device is displayed and to understand its common name, a reference to https://support.google.com/googleplay/answer/1727131 indicates that the market name of the device is ‘Galaxy Note3’.
Similar to emulator, the name is not displayed since it is depreciated.

iPhone


When the program is run on the iPhone

image_thumb4

The app is running on iPhone 6 device, so the isVirtual device flag is indicated as false.
And since name is not depreciated and serial is not supported on iOS, those values are set to blank and unknown respectively.
If we look up http://www.everyi.com/by-identifier/ipod-iphone-ipad-specs-by-model-identifier.html for iPhone7,2, we find out it is one of the iPhone 6 models.


iPad


When the app is run on iPad,


image_thumb3

The app is running on iPad device, so the isVirtual device flag is indicated as false.
And since name is not depreciated and serial is not supported on iOS, those values are set to blank and unknown respectively.
If we look up http://www.everyi.com/by-identifier/ipod-iphone-ipad-specs-by-model-identifier.html for iPad3,4, we find out it is iPad 4th Gen wifi model.


iPhone Simulator


When the program is run on the iPhone simulator:

image_thumb6

Since this is running on an emulator, the virtual flag is indicated as false and the name and serial are not supported on iOS and since this is a emulator, the model is indicated differently.

         The code displaying the usage of this API is available on github.








































Friday, August 28, 2015

Installing NodeJs on Windows

 
NodeJs is an asynchronous event driven JavaScript framework designed to build scalable network applications. NodeJs is used to distribute Cordova and all the plugins related to Apache Cordova. 

Download the latest version of nodejs from nodejs website.

https://nodejs.org/

clip_image002

Once the download is completed, double click on the installer to start the installation process.

clip_image004

Click on ‘Next’ to start the Nodejs installation.

clip_image006

Accept the End-User License Agreement and click on ‘Next’ to continue the installation process.

clip_image008

clip_image010

Select the location at which you want to install the Nodejs.

clip_image012

Click on ‘Next’ to continue installation.

clip_image014

Click on Ínstall’ button to start installing nodejs.

clip_image016

clip_image018

Click on ‘Finish’ to complete the nodejs installation.

clip_image020

To verify the installation, open command prompt and run the below commands.
npm –v
node –v

These commands should display the nodejs version and npm versions. They may vary from the below screen based on the version of the nodejs installed.

clip_image021

We have installed nodejs on the windows machine and we will be using this to work with Cordova in the upcoming tutorials.


Tuesday, July 15, 2014

Setting up development environment for GWT

Introduction

This is part of series intended to develop cross platform mobile applications in Java. In this blog post we will see what GWT is and set up the development environment for GWT.

GWT is an open source development toolkit for developing complex browser based Ajax applications. Using GWT you can develop Rich Internet Applications(RIA) in Java which is then compiled into JavaScript and is cross browser compliant.

Some of the advantages of developing web applications in GWT are:

Since GWT apps can be developed in Java, you can enjoy all the advantages of developing in Java like auto-complete,Debugging, refactoring, code reuse, polymorphism, over riding, over loading. And Java has large set of tools for development like Eclipse, NetBeans,JUnit and Maven etc which you can use for developing Rich Internet Applications(RIA).

Maintaining large JavaScript projects is not easier when compared to Java projects. But you need JavaScript to run Rich Internet Applications in browser. GWT combines both the advantages. You develop the applications in Java and then they are compiled into JavaScript, so you are having best of both.
GWT is almost similar to AWT and Swing packages in Java and so has a low learning curve for Java Developers.
Supporting several browsers in the market is a difficult tasks. Each browser creates it own set of problems. GWT solves this problem by creating optimized JavaScript code for each browser specifically addressing the issues with that browser. So you can support almost all the major browsers including Android , iPad and iPhone based browsers without worrying about quirks for each browser.

Developing UI's in Java is difficult task compared to other aspects of Java programming. GWT solves it by providing several UI widgets and also you can extend the existing widgets and create your own custom widgets if you wish to.

Some of the limitations of GWT are:

Since the java code is compiled into JavaScript which runs on the browsers, the JavaScript needs to be enabled on the browsers. The applications will not work if the JavaScript is not enabled on the browser.
If you have specialist UI designers who can create HTML pages, this will not work. You may have to implement what ever Designer created again in GWT.

Web Pages created by GWT cannot be indexed by search engines since these applications are generated dynamically.

I think except the second drawback in the list, others don't matter much. It is difficult to provide a rich internet application just in HTML. You will need JavaScript to create rich internet applications. Some apps provide a limited version of apps which work if JavaScript is disabled but majority of apps require JavaScript , so you are not the one there. And there is no reason why large number of users will disable JavaScript on their browsers.

And there is a work around for indexing by search engines. The index page can be created in html, and the remaining pages can be created in GWT. GWT provides an option to define index page in html format. So the index page can still be indexed by search engines and the other pages are mostly dynamically created data, so they don't need to come up in the search unless you they are some kind of content management systems(CMS).

Like the case with all the frameworks, GWT doesn't solve all the issues, but it surely makes the java developers more productive developing the web applications, provides cross browser support and works perfectly for complex enterprise web applications.

GWT Development Environment Setup

We will start setting up the development environment for GWT applications.

Java

Since you will developing the applications in Java before they are compiled into JavaScript, you need to set up Java development environment.
Once Java environment is set up, let us configure the environment for GWT.

GWT SDK:

Download the latest version of GWT SDK from the GWT project site.
http://www.gwtproject.org/download.html

gwt_1

Go to the above link and click on ‘Download GWT SDK’ highlighted in the above screen. Then unzip the downloaded GWT SDK to your preferred location on your hard disk and it will look similar to the below screen shot.

  101

You might want to add this path to use the commands available in gwt.

Right click on ‘Computer’ on your desktop and select ‘Properties’ which displays the below screen. Click on ‘Advanced System settings’.

a5

Click on ‘Environment Variables’ in the below screen.

a6

Clicking on Environment Variables will display the below Window. Select ‘Path’ from the list of available variables and add the path to which you extracted GWT SDK.

a7

z1 
Then click on ‘OK’ to close the ‘Edit User Variable’ screen and ‘OK’ in ‘Environment Variables’ and ‘System Properties’ window to save the modifications.

 

Eclipse


You need to install the eclipse plug-in for GWT to develop GWT applications on eclipse easily. To install GWT eclipse plug-in , launch eclipse , go to Help –> Eclipse Marketplace

111

Search for GWT in the eclipse market place.

122

Find out ‘Google Plugin for Eclipse’ and the version number should match the version of the eclipse you are using. If you are using Eclipse Kepler(eclipse 4.3), you need to look for ‘Google Plugin for Eclipse 4.3) and click on ‘Install’.

124

Accept the license and click on ‘Next’ to continue installation.

127

It takes some time to download and install the plug-in.

129

While installing you will get a security warning. Just click on ‘Ok’ to continue the installation.

130

Restart the eclipse after the installation of plug-in is completed. After restarting the eclipse, you will see the GWT plug-in added to the eclipse tool bar.

131-1

NetBeans

If NetBeans is your preferred IDE, there is an GWT plug-in available for NetBeans as well.
Launch NetBeans, and in NetBeans ‘Start Page’ click on ‘Install Plugins’.




n1

Alternatively you can navigate to Plugins view by selecting Tools – > Plugins from the NetBeans menu.


n20

In the Plugins Windows, navigate to ‘Available Plugins’ tab.

n2

In the Search textbox, enter gwt and hit Enter. This will return the gwt related plugins for NetBeans.

n3

The GWT plug-in for NetBeans in GWT4NB which is the only GWT plug-in available in the list. So select it to install and click on Install button at the bottom of the Plugins screen.

n5

Click on ‘Next >’ button to start the installation of the GWT NetBeans plug-in.

n6

Select the check box against the license agreement and click on Install to agree to the license agreement and to start the installation process.

n7

GWT NetBeans plug-in is being installed..

n8

When the below message is displayed, just click on Continue to continue the installation process.

n10

Restart the IDE once the installation is completed by selecting against the ‘Restart IDE Now’ and clicking on ‘Finish’.

n11

Once the IDE is restarted, from the NetBeans Menu bar , select File –> New Project. You will see the below New Project window which has a GWT option under the Categories indicating that the GWT Plugin for NetBeans is installed successfully.

n21

Browser Plugins


And we need to install extensions to the browser you are planning to use for running the GWT app in development mode. We will see later what the development mode is, but for now let us install the plugins for the browser to complete our set up of the development environment. If you launch the app in Dev mode without installing the plug-in, the browser will display a message similar to below.

In Internet Explorer:

144-1

On Chrome:

147-1

When you click on Download, On Chrome, you will be redirected to the Chrome extensions page from where you can install the GWT Developer plug-in.

146

Click on ‘FREE’ button to install the plug-in on Chrome browser.

On IE, clicking on ‘Download’ button will download a ‘GWTDevPluginSetup.exe’ set up and launching it will install the GWT developer plug-in for IE.

Restart the browsers after the GWT developer plug-in is installed.

Unfortunately the latest versions of Mozilla Firefox doesn't support the GWT Developer Plugin. So you can’t work in Development mode on latest version of Firefox, but GWT already provides a super dev mode which doesn’t require installing any plug-in during development. So you can use Firefox in super dev mode during development mode.

Conclusion

We completed setting up the required development environment for developing applications in GWT. We can start creating GWT applications !!

Monday, January 13, 2014

Using Ripple to emulate Apache Cordova / Phonegap applications.

Apache Ripple


After somegap I had to use Ripple emulator when I was trying to upgrade GWTPhonegap to support Apache Cordova 3.3. Apache Ripple is a browser agnostic mobile emulator. This will enable rapid development of Hybrid mobile applications using frameworks like Apache Cordova and Blackberry webworks. Ripple was initially developed by Blackberry and then donated to Apache open source community. Similar to Apache Cordova, Apache Ripple is a free and Open sourced under the Apache License, Version 2.0

Installation


The latest version of Ripple is distributed using nodejs and so you need to install nodejs first. The instructions to install nodejs are available here.

After installing nodejs, open the command prompt/terminal and run the below command to install ripple emulator.

npm install -g ripple-emulator




And since you will be emulating Apache Cordova applications, you need to install Cordova and create a Apache Cordova application.The instructions to install Apache Cordova are available here.

Running Ripple


Once you create a Apache Cordova project, make changes to the code, add the platform, prepare the project running the below command.

cordova prepare

The above command needs to be run every time you make changes to your project.



Run the below command from the root of your project to start the Ripple emulator.

ripple emulate




Once you run the above command, ripple will launch the default browser on the system. Your application will be emulated in the browser launched.




Some times you may see the below error page after Ripple launches the browser.



Just click on 'Wait' button or refresh to resolve the error.

Device


The devices section highlighted below provides options to emulate the application on different devices.



There is a option to select the device which we need to emulate. There are several Blackberry, Android and iOS devices available which can be emulated.

Also there is an option to simulate the vertical and horizontal orientation also.Just click on the vertical or horizontal  icon against Orientation label to simulate Vertical or Horizontal orientation.


Platform


The platform section provides options to choose the platform and version to be used for emulation.

The platform drop-down provides options to select a platform among WebWorks, Phonegap to emulate.


You can also select the version you want to emulate.Apache Cordova provides versions 1, 2 & 3. I believe all the versions between 1 and  2 can select 1 and so on.

Information


The information section provides information about the environment that is being emulated.The description of  the information displayed is below.


Version: version of the application
Platform: The framework that is being emulated.
Device: The device that is being emulated.
OS: Operating system of emulated device.
Manufacturer: Manufacturer of the device that is being emulated.
Screen: The screen resolution of the emulated device.
Density: The pixel density in the app you are emulating.
CSS Pixel Ratio: The device pixel ratio is the ratio between logical pixels and physical pixels.This indicates the pixel ratio of the emulated device.
CSS Pixels:The CSS pixels that is being emulated.
User Agent: Indicates the user agent in device that is being emulated.


Accelerometer


The accelerometer allows us to emulate the device motion changes using accelerometer  framework. You might as well emulate shaking the device to test the device motion changes. You can use the device icon in this section to emulate the device motion actions.




Settings



The 'Settings' has options to switch the themes between 'Light' or 'Dark' and you can turn the tool tips on or off.

Desktop browsers have a limitation which restricts the Ajax code from making cross domain requests. This is a security restriction on all the browsers. Chrome provides an flag to bypass that restriction. 


The Cross Domain Proxy is one of most useful features of the Ripple emulator. Ripple proxies the request made from then application, makes a request for the data from its own server and then proxies the result back to the application.





Device & Network Settings

This section provides you an option to emulate the network and gloabalization API of the Cordova framework.

You can select the connection type you want to select from all the connection types like ETHERNET, Wi-Fi, 2G, 3G, 4G and also you can indicate if there is a network lag or not.

There are also some functions from globalization API which can be emulated. You can provide the locale name, whether the day light savings are enabled or not and also the first day of the week. The values provided here will be used by your application when these functions are called.


Geo Location


The geolocation allows you to emulate the location related API in your application. You can enter the values to mock in the geolocation section and they will be used by your application.


Config


The Ripple emulator reads the configuration file and displays the result in this section . If there are any errors or issues they will be displayed here.


Events

The Events section provides several events(device ready, back button,pause, resume, search button, menu button, offline, online) which are supported by Apache Cordova. While these events are not actually simulated, they are just registered. Say if you select back button, the event will be registered to the Cordova API, but it doesn't simulate the actual hardware event.



Camera


Ripple supports some of the functions related to Camera API also. It allows you to select a image from your system and then use it for mocking the functionality later.




Unsupported options


As you can see by now, Ripple doesn't support all the options provided by Apache Cordova. When Ripple encounters a call that it doesn't support, it shows up a pop up similar to below.



In this case you can enter the JSON object to the callback that you want to execute.

Conclusion


Ripple is an excellent development tool to emulate the Apache Cordova applications on desktops. You will be able to switch between different OS's like Android, i-OS and Blackberry. And you will able to get a first hand feel of how your application looks on different devices and also in horizontal and Vertical orientations. There may be some limitations in Ripple, but I believe it is a must use tool for developers developing cross platform mobile applications using Apache Cordova. And once you are done with developing, you need make sure you will test the application on real device before pushing the applications to App Stores.