Hybrid vs Native Android App Comparison

A while back I did a File Size and Startup Time Comparison of Android Apps using App Inventor versus the Android SDK. Android SDK was the winner.

Now I have done a comparison of Hybrid (using PhoneGap compiled on PhoneGap Build) vs Native (using the Android SDK).

Below are are my results for a very simple app using the Galaxy Note 2 as the test device. If you are concerned about speed, native is the winner in my book.

Android SDK

  • File size before install: ~162 KB
  • File size after install: 652 KB
  • Startup time: Less than half a second
  • Notes: Tapping the Clear Textbox button had what seemed like instant responses.


 PhoneGap

  • File size before install: 349 KB
  • File size after install: 1 MB
  • Startup time: About 2.5 seconds
  • Notes: Tapping the Clear Textbox button had a somewhat laggy response, but not too extreme.


Comments

Post a Comment

Popular posts from this blog

Adobe® Flex® Combobox: Selecting an Item Without Using SelectedIndex

In Adobe Flex, in order to select an item in a ComboBox, you use the .selectedIndex property. However, there might be times that you want to specify the item to be selected based on something other than it's position in the list. I have found two potential solutions: ComboBox2 from Ben Forta, Flex evangelist, is a ComboBox component which allows you to specify a "selectedValue" property.   VAComboBox  from Codieron, LTD. (BSD license) Copyright Notice: Adobe, and Flex are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Read more

Parameters Sent by TinyWebDB in App Inventor for Android

TinyWebDB is a component in App Inventor for Android that lets your app communicate with a web page in order to set or retrieve values, rather than storing them on the phone itself. I wanted to know what the TinyWebDB component sends to the web page when it tries to set or retrieve values, so I used Kodingen this morning to write a PHP script that takes the form fields and values sent to the page and writes them to a file. Here is what I found: TinyWebDB.StoreValue sends these parameters: tag value TinyWebDB. GetValue sends this parameter: tag So if you write your own PHP page for TinyWebDB to connect to, you can know if TinyWebDB is trying to store a value if the "value" key exists in the $_POST array. If the "value" key doesn't exist in the $_POST array then you know that TinyWebDB is only trying to retrieve the value for the given tag. As an alternative to using the method outlined by Google , you could use TinyWebDB with your own script written in an
Read more