Comments for DougT

Comment on Fennec and Native Android UIs by work in progress – turning on reftests in the new native UI for firefox on android | 3.1415926535897932384626433…

Mon, 28 Nov 2011 16:17:43 +0000

[...] latest builds of Mobile Firefox are switching to using a Java based UI, which means the tests that depend on a traditional window environment and backend XUL will most [...]

Comment on Fennec and Native Android UIs by Ben Bucksch

Ben Bucksch — Sun, 06 Nov 2011 01:12:18 +0000

Awesome. I can’t wait to install it on my phone.

As a Mozilla developer, I’d like to use Firefox on my phone, for ideology and for tabs, but I can’t, it’s too slow and takes too much RAM. Thanks for doing this. It makes sense, the UI on Android should be minimal, so the UI work is limited.

As for extensions, if Addons SDK API is designed well enough, these addons should work in the native UI.

Comment on Fennec and Native Android UIs by Rob

Rob — Fri, 04 Nov 2011 23:28:32 +0000

I completely agree that “people aren’t sticking around”. I have been using Firefox as my default browser on all of my Mac machines (though I’ve recently had a few issues with FX7 that has me considering a switch to Chrome), yet I cannot bring myself to wait around for Fennec to load on my HTC EVO 4G. I’ve had Fennec installed several times only to ditch it. I can literally feel my blood pressure rise each time I see that “Loading” screen. LOL. At any rate, I’m using the stock browser baked into the CyanogenMod7 ROM I’ve installed and it suits my purposes. If Firefox gets its act together around a mobile version I may have to give it another look and try. Best of luck.

Comment on Fennec and Native Android UIs by AV

AV — Tue, 18 Oct 2011 18:49:35 +0000

Electrolysis will remain or isn’t related?

Comment on Fennec and Native Android UIs by dougt

dougt — Fri, 14 Oct 2011 16:36:05 +0000

on the fastest phone we have, we startup in 2 seconds. the default browser starts up an order of mag faster. If the world only had these kind of phones, I tend to agree with you. However, it is not. There is a long tail of lower end phones. ARMv6 phones are still being sold replacing feature phones. I’d love to ignore this problem…. hardware will fix this for us!!!

But our competition isn’t thinking that way nor do they have to load a library as big as libXUL before they show their UI. Our competition kicks our ass on very low end phones. Why can’t we compete?

We have such a great feature set. We are the browser for the people. But people aren’t sticking around.

Comment on Fennec and Native Android UIs by Firefox 8 beta brings Twitter search, tab controls | REDSTAB VIDEOS

Firefox 8 beta brings Twitter search, tab controls | REDSTAB VIDEOS — Mon, 03 Oct 2011 01:53:39 +0000

[...] especially when compared to the built-in browser from Google. To that end, Mozilla is investigating mobile Firefox with a native Android interface rather than the one built using Mozilla’s XUL technology. Such an approach speeds browser [...]

Comment on Fennec and Native Android UIs by FuTuRe BeAt….. - FuTuReBeAt.NeT......

FuTuRe BeAt….. - FuTuReBeAt.NeT...... — Sun, 02 Oct 2011 20:18:43 +0000

[...] XUL user interface language as the basis for Android Firefox. Experiments with the browser using Android’s native user interface language have been [...]

Comment on Fennec and Native Android UIs by Mozilla Releases Firefox 8 Beta, Includes Twitter Search

Mozilla Releases Firefox 8 Beta, Includes Twitter Search — Sat, 01 Oct 2011 15:23:50 +0000

[...] XUL user interface language as the basis for Android Firefox. Experiments with the browser using Android’s native user interface language have been [...]

Comment on Fennec and Native Android UIs by Mozilla Releases Firefox 8 Beta, Includes Twitter Search

Mozilla Releases Firefox 8 Beta, Includes Twitter Search — Sat, 01 Oct 2011 03:58:25 +0000

[...] interface denunciation as a basement for Android Firefox. Experiments with a browser regulating Android’s local user interface language have been [...]

Comment on Fennec and Native Android UIs by dougt

dougt — Sat, 01 Oct 2011 03:47:43 +0000

XUL isn’t the slow thing. It is waiting all of the support libraries to be loaded and ready to bring up a UI. Android already has the support libraries ready to go when you start an Android application if you write the application using the Android’s Native widgets.