Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

PhoneGap too slow for Android?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    PhoneGap too slow for Android?

    Hi,

    I've been testing a relatively simple app based on the world cup demo, while it works its painfully slow on my 3 Android devices including a Samsung Galaxy Note. I've followed the documentation and I don't think I've done anything unusual. Has anyone else had similar experiences with PhoneGap for Android? I wanted to publish it on Goggle Play but considering its poor performance I'd be too embarrassed to put my name to it (disappointing).

    Below is the QR code for the app and the web app link. Its a search tool for the Australian Aircraft Register with Flickr (pinched from the world cup demo) and Google Maps.

    http://111.67.20.102/airreg/webapp.a5w

    AirRegQR.png

    #2
    Re: PhoneGap too slow for Android?

    I just ran your app on my Nexus 7 (2013) and I'd say it's workable, but kind of "stutters". Are you using a server with this app? Is your connection WiFi or cellular? Do you see a difference in performance between the two? I feel that some apps just won't be useable with a celluar connection. If you're connecting and pulling down images it may be too much.

    I have an app in development under iOS and Android (no server) that is very smooth (normal) under iOS and Nexus 7. However, reports back from testing say that it does not run well on any Android phone tested. That it does not run at all or there is odd behaviour.

    Because there are a thousand flavours of Android and because each manufacturer does their own thing to Android with their own browser versions I'm afraid this may be what we get for a while. Some say Apple is too closed. I disagree because you get an amazing "experience". Android is far too open. There needs to be some coherence in order to create a better overall experience for the user. The Google Play store is filled with apps that simply do not work or need a rooted device to work. It's silly.

    Comment


      #3
      Re: PhoneGap too slow for Android?

      FWIW I just ran the app from my Samsung S4 in Thailand which has been throttled back to 384kbps due to exceeding my data limit, and it ran absolutely fine! Bringing up the image was instant (maybe you are caching it now?). The main issue is the fixed box at the footer advertising your application services which makes using the app in landscape difficult. Suggest getting rid of it in landscape mode on a mobile device, or locking to portrait and also ditching the keyboard when a selection has been made (I assume this can easily be done in Alpha like it can in iOs).

      Are you hosting with Zebra or doing it yourself?

      Comment


        #4
        Re: PhoneGap too slow for Android?

        Tested on my HTC desire 601 via WIFI; very slow, tapping on the text box results in maybe 3 to 4 seconds before a cursor shows up. The pictures do load very fast though.
        Frank

        Tell me and I'll forget; show me and I may remember; involve me and I'll understand

        Comment


          #5
          Re: PhoneGap too slow for Android?

          Very slow on an S4.

          Can't tell if a button has been pressed or not..

          Not sure if it's local or the server.

          Got an add about hosting. Is that you or your hosting ISP?
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment


            #6
            Re: PhoneGap too slow for Android?

            Very slow on my Samsung S3 (SGH-1747M) over high speed Wifi.
            Brad Weaver, President
            ComputerAid International
            Ottawa ON Canada
            Versailles KY USA
            www.compuaid.com

            Comment


              #7
              Re: PhoneGap too slow for Android?

              Peter - One thing I would recommend is putting your map control in its own child UX and load it dynamically. It is slowing your app down considerably. If you open your web site in Firefox (running in debug mode and select the Net tab) you will see that it takes 16-17 seconds to load all of the necessary Google map resources when your cache has been cleared. You won't get any better overall time if you eventually click the Map button, but at least it will load much faster initially and you will not get penalized with any Google map resource loading if you don't need to see a map.

              Comment


                #8
                Re: PhoneGap too slow for Android?

                I'm busy converting all of my UX components to parent-child UX "sets". Things
                were incredibly slow especially when I had multiple charts and related data-series.

                This results in much more work on navigation because both the parent and child UX
                components need alterations to menus, swiping, and general navigation to make
                the "set" seem like it is one singular UX.

                It is what it is. Speed is a requirement.

                I thought tall blondes and a Ferrari were also requirements but fate did not get the memo.

                Comment


                  #9
                  Re: PhoneGap too slow for Android?

                  Hi All,

                  Thanks for all the feedback. I rebuilt the app panel by panel checking the performance with phone gap numerous times along the way. I noticed (as DaveF suggested) the Map control was killing the performance. I tried to use the map as an embedded component but it was still slow so I dropped the feature entirely. Also one of the list controls bound to my server was sucking up too much data and slowing it down, I dropped that feature too (the browse function) as it was pretty useless anyway.

                  Anyway it a dumbed down version of what I started with but it now performs pretty well, still a few bugs to sort out but I might have something worth publishing on Google Pay and maybe the App store one day.

                  Below is the current version

                  Thanks again

                  Cheers

                  Peter

                  AirRegQR.png

                  Comment


                    #10
                    Re: PhoneGap too slow for Android?

                    Interesting,

                    I don't know what you do with the map but you could experiment with a hidden feature of the UX & create static HTML of a UX with a map control. csh.png
                    Frank

                    Tell me and I'll forget; show me and I may remember; involve me and I'll understand

                    Comment


                      #11
                      Re: PhoneGap too slow for Android?

                      Originally posted by Clipper87 View Post
                      Interesting,

                      I don't know what you do with the map but you could experiment with a hidden feature of the UX & create static HTML of a UX with a map control. [ATTACH=CONFIG]38862[/ATTACH]

                      Interesting.

                      One might be able to go a step further and combine that with offline storage.
                      Just thinking out loud here. I have lists that have associated maps but the
                      lists are not highly dynamic. Therefore, one might:
                      1. Create a list and associated table with a character field to hold resultant HTML
                      2. Set the list for offline storage (local database on the device)
                      3. Populate the HTML field when the address is first entered or after the fact with a processing loop
                      4. Allow the offline list to populate the first time (slower)
                      5. Pull the now-local HTML and assign it to the "static html" property when you need it (fast)


                      Just a thought.

                      Comment


                        #12
                        Re: PhoneGap too slow for Android?

                        It is a feature not yet documented & part of the phonegap genie. The new videofinder is actually a static html page created from a UX with a list see this video http://www.youtube.com/watch?v=-l2bwb0OCYc
                        Frank

                        Tell me and I'll forget; show me and I may remember; involve me and I'll understand

                        Comment

                        Working...
                        X