Performance Problems Found in Mobile Web App Development

These aren't perfect statistics, but the basic idea of how my experience went when testing mobile web development on 5 mobile devices went something like this:


iPhone 5 (using Safari on iOS 6.1.4)
  • Linear gradient on the buttons worked.
  • Rendering 1,000 buttons took about .75 seconds.
  • Scrolling the div containing the buttons was very good. Nothing was hidden unless I scrolled really fast. Rendering was quick to catch up though.
  • Hiding one button after rendering the thousand buttons was instant.
  • Showing an image with a background image was instant after the images were cached.
iPod Touch 4 (using Safari on iOS 6.1.3)
  • Linear gradient on the buttons worked.
  • Rendering 1,000 buttons took about 1.5 seconds.
  • Scrolling the div containing the buttons was pretty good. Nothing was hidden unless I scrolled kind of fast. Rendering was slower to catch up than the iPhone 5.
  • Hiding one button after rendering the thousand buttons was instant.
  • Showing an image with a background image was instant after the images were cached.
  • The background could not load a png image that was 1536x2048 at 71.98 dpi. The filesize was 707 KB. When I made the image smaller (536x715 at 143KB), then it would load.
iPad 1st Generation (using Safari on iOS  5.1.1)
  • Linear gradient on the buttons worked.
  • Rendering 1,000 buttons took about 1 second.
  • Scrolling the div containing the buttons was pretty good. Most the content was hidden when I scrolled kind of fast, but rendering kept up okay but. Overall it was still worse than the iPod Touch 4 but better than the Galaxy Note 2.
  • Hiding one button after rendering the thousand buttons was instant.
  • Showing an image with a background image was instant after the images were cached.
Galaxy Note 2 (using default browser on Android 4.1.2)
  • Linear gradient on the buttons worked.
  • Rendering 1,000 buttons took about 2.5 seconds.
  • Scrolling the div containing the buttons was not very good. Chunks of the view were hidden just by scrolling moderately fast. Rendering was okay in catching up.)
  • Hiding one button after rendering the thousand buttons took about 2 seconds.
  • Showing an image with a background image was instant after the images were cached.
Galaxy S Fascinate (using default browser on Android 2.2.2)
  • Linear gradient on the buttons did not work.
  • Rendering 1,000 buttons took about 2 seconds.
  • The div containing the buttons would not scroll.
  • Hiding one button after rendering the thousand buttons took about 1 second.
  • Showing an image with a background image was instant after the images were cached.

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