in reply to Phonegap with ajax and Perl backend

" I have a website created with Perl (and MySQL) and Ajax and would like to convert it to an app that can be downloaded on an Android phone or Iphone"

I have not used phonegap, are you sure it can do this? I doubt it very much. Most of these things I've seen create a UI (HTML/CSS/JS) within a wrapper and expose things like GPS, accelerometers etc via HTML5. Think about what you're trying to do. The "server" does not get downloaded onto the phone. Also, WFIW, I've reversed a couple of "apps" created using similar systems distributed by my employer. I was wondering why a 4 page "app" (one pointless splash screen, one legally unenforceable 'licence' page, a help page and one stupid graph) was over 40MB in size. Bloatware combined with binary runtimes for various targets, all bundled up in a .apk file. If you have this running on a web server, why bother having an app at all? Why not just have a web interface with a nice UI?

  • Comment on Re: Phonegap with ajax and Perl backend

Replies are listed 'Best First'.
Re^2: Phonegap with ajax and Perl backend
by Anonymous Monk on May 11, 2017 at 15:38 UTC

    The app stands a higher chance of being used if it can be found on the phone like a native app (Iphone or Android) phones. I came across someone's blog where he wrote about serving his Javascript game via web and via an app that can be downloaded on Android phones. He said the usage of his game is higher in the app format.

      "I came across someone's blog where he wrote about serving his Javascript game via web and via an app that can be downloaded on Android phones."

      So a blog you found is the authoritative answer on the subject? Both (the fact you found a blog/the claim of an app getting more users than a website) simply sounds like a matter of marketing. Regardless of how you deliver it, you're attempting to deliver a service. I'd focus my efforts there.

        No, it wasn't due to the blog. I had already started on the PhoneGap thing before I chanced upon it. The app that I will be making is the sort that people would not normally google for and use via a phone's browser.

      A Javascript game - or application - is already running in the device. Converting it to an actual Android App is not a structural change. (Don't know about conversion to an iOS app.)

      Converting a server-based application to an Android app, however, is a serious structural change. And you may still end up with an app that communicates with a server. (And probably even more difficult to do for iOS.)

      A more realistic approach would likely be converting just the web-based UI to an Android (or iOS) app.

      Also, I've heard that there are apps that, supposedly, just pass an URL to the web browser. I haven't tried. So far, the only Android app I've "created" was the result of following a tutorial and adding/modifying some features. Curiosity satisfied, I've not had a reason to do more.

      I'd much rather use Perl. Then, if I need to use it on my tablet, put a web interface on it. If some one else needs to use it from their tablet or smart phone, they will, despite the lack of an app.