Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Chromeless Firefox Mobile for Android Development
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
C. Scott Ananian  
View profile  
 More options Sep 19 2012, 9:42 pm
Newsgroups: mozilla.dev.platforms.mobile
From: "C. Scott Ananian" <canan...@gmail.com>
Date: Wed, 19 Sep 2012 18:42:58 -0700 (PDT)
Local: Wed, Sep 19 2012 9:42 pm
Subject: Re: Chromeless Firefox Mobile for Android Development
I've been doing a lot of related work recently, and in fact just shipped an Firefox/Android based education app to an offline deployment in Ethiopia yesterday.

Here are the major bugs/missing features I've found:

* AppCache is really buggy.  Ogg audio doesn't play from appcache (bug 791017) and most video won't play either (bug 741351, bug 784329).  The AppCache.swapCache() method is broken (bug 769171).  On FF/Mobile, the cache also doesn't appear to update correctly when the manifest changes (still working on isolating a test case).

* There's no good way to install a webapp without connectivity (bug 790456).  I've resorted to copying profile directories around using adb, but it's evil.
* Webapp installation isn't scriptable by Android intents, either (bug 790457) so it's hard to automate installation (for classroom purposes, for example).

* The size of the offline cache and of local storage is fixed, and very small for Firefox/Android.  This will impose a strict limit on the size of your offline webapp and of the size of the data it can manipulate.  These limits should really be specified by the webapp's manifest.  (The user should be able to install a 50M webapp if they want to!) (bug 792651)

* No integration of add-ons and webapps (bug 790461).  This makes "phonegap"-like extended functionality for webapps needlessly difficult.  I've resorted to manually hacking the prefs.js for the installed webapp to re-enable extensions, and I've written an add-on-to-JNI bridge which allows your addon to access all of the Android SDK (see https://github.com/cscott/intent-addon for an example).  However, the Activity Context isn't properly exposed to Add-On authors (bug 790452).

* No splash screen support (bug 604728).  Your app will look pretty ugly while it is starting up.

* Versioning is problematic if you use AppCache -- AppCache only checks for new versions when the page is "loaded" or "reloaded", and there's no way to control that on an Android webapp.  Android Jelly Bean allows you to close apps easily (good) but it caches "closed" apps (oops!) so even if you close the app and relaunch it there's no guarantee you'll get reloaded.

That said, even with those issues webapps worked well enough for me to ship some code to Ethiopia this week, and the mozilla webapp stuff is IMO much better than PhoneGap on Android.  Video and WebGL work, for example!
  --scott


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.