Firefox Arrives On Android
Barence writes "Mozilla has launched a 'pre-alpha' version of Firefox for Android smartphones. The mobile version of Firefox, codenamed Fennec, has until now been restricted to Maemo Linux handsets. But following a surge in developer effort, Mozilla has unveiled a build for handsets running Android 2.0 or above. Mozilla is making no guarantees about the browser's stability. 'It will likely not eat your phone, but bugs might cause your phone to stop responding, requiring a reboot,' writes Mozilla developer Vladimir Vukicevic on his blog. 'Memory usage of this build isn't great — in many ways it's a debug build, and we haven't really done a lot of optimization yet. This could cause some problems with large pages, especially on low memory devices like the Droid.'"
Unless you want to help debug and/or develop, I doubt anyone expects or even wants you to.
If you report bugs on alpha code the developers will thank you. If you report bugs on pre-alpha code, the developers will collectively roll their eyes and suggest that maybe you should wait a month or two before installing another pre-alpha.
Oh wait, firefox, yeah.. I guess it's always pre-alpha ;)
How we know is more important than what we know.
I like Firefox mobile on my n900. It works pretty well, gives me features not available in the default browser. I have not had memory leak problems with it. However, it does get sluggish if you turn on flash and visit pages with a bunch of flash ads. I should put adblock on it...
Pre-alpha is just PR talk. Just like how game-developers claim their new screenshots is pre-alpha build. "Oh. it doesn't look so good now. but it's just pre-alpha. We promise, in 3 months when it's released it will be AWESOME". (ref. bungie halo series)
Some of us don't like our data being proxied and processed off our phones. I know it's a fine line, but my Android browser has good JS support. Why would I want to throw that away for a little bit of speed?
If a man isn't willing to take some risk for his opinions, either his opinions are no good or he's no good
Probably not.
"I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
But I made the fatal mistake of putting it into landscape to get a better keyboard, and it brought my phone (Desire) to a crawl. I assume it was trying to rebuild the page layout, something bad happened and displayed a black page.
It Shows promise, it is not usable (obviously) but the UI design seems better than the inbuilt browser. With tabs off screen to the left, and navigation buttons off screen to the right.
Would of been nice to see pinch zoom working, and I am assume that it will (or a custom build that will).
From what I have seen, when it heads into a more stable phase, I would probably swap right away.
Automation - The Car Company Tycoon Game
Because you might want to help make it better by submitting feedback and tracking bugs as it heads into alpha/beta stage and reporting them?
Because tinkering is cool, and it doesn't replace your webkit browser?
It's not really a valid point, you're both criticizing this as if it were a release.. It's alpha for a reason. Like the GP says, they don't expect nor want people with your expectations to try this build.
As far as why you'd want it at all, well, competition is always a good thing..
I can smell the momentum in the air with Android. I was one of the first people (suckers/early adopters) to buy a G1 handset from T-Mobile. At the time I had a 2G iPhone. Used the G1 for a week, went back to my unlocked, jailbroken iPhone because it had a bunch of great apps that worked well, better form factor, better touchscreen, and much more usable.
Fast forward 16 months, during which time the G1 has sat there and gathered dust. I've finally gotten fed up with my 3G iPhone, the closed ecosystem, the limited email application which is the dealbreaker for me (lack of IMAP IDLE still - msgpush.com is not an option for me, and switching email services to support the technologies Steve Jobs approves of is ridiculous). The other day I decided to blow the dust off my G1, update to the latest software (which on a G1 means running CyanogenMod since the official updates are still stuck at Android 1.6 for G1s, and CyanogenMod is a 1.6/2.0 hybrid - and despite rumors to the contrary, CyanogenMod is rock-solid stable on the G1) and see how much things have improved over the last 18 months.
The openness of the Android platform is what really is blowing me away. Running CyanogenMod, installing themes, downloading up-to-the-minute app releases and bug fixes from open source projects and vendors without having to go through Market is absolutely liberating after 2 and change years of iPhone usage, and having to clamor for every feature addition and update. On Android, if you want a new feature, you can usually find it or you can add it yourself - K9mail is the best living example of this itch-scratching driving innovation.
Anyway, more specifically on the topic - I don't know if Fennec/Mobile Firefox will be a winner or not in the short run. Most likely it will take a while to get there - remember how long Mozilla took to get to a usable desktop browser? But ultimately, more browser competition on Android will be a very good thing, and AdBlock would be sweet. The fact that we have these choices on Android drives innovation and competition, and is the reason that the platform is currently improving faster than the iPhone platform. And makes it a much more fun place to be as a geek than iPhone-land right now.
How does this technology work? Since the android gui is written in a java dialect, and firefox is written in C/C++, how does a C++ program run on a java VM? As one big native plugin?
anyway,having a runnin POC might attact other developers, that cannot be bad for fennec.
I just installed it on my rooted, custom ROMmed and overclocked Motorola Droid.... and it worked! I played with it for about 10 minutes. It didn't crash my phone, reboot my phone or damage my phone in any way.
It's absolutely alpha quality software at this point, so don't expect much from it. But it has lots of potential and I'm absolutely confident this will turn into a great browser on Android.
so your question is 'why would i download a pre-alpha release and play around with it on my phone' because it MIGHT NOT WORK
...mine is why are you on slashdot if that sounds like something you wouldn't do? i was really excited about the release and installed it immediately for my Moto Droid and then i come into the one place on the web where i thought that others would share my enthusiasm and here you two are pissing all over it for being, you know, an alpha release.
It does, and they are. There are a few tweaks that add-on authors should make to their add-ons to support the mobile versions (mainly UI-related), but those are trivial for most cases. I say this as someone who has ported more add-ons to Firefox for Mobile than anyone else (as far as I know).
Why then would I want to replace my webkit browser with this? I understand this is an Alpha and that bug might be fixed, but again, why would I want to use this over my webkit based browser?
Because some of us view OSS as more than just free software. Some of us want to help debug/test it and add to the community. Some are out for more than just a free-ride (although there's nothing wrong with a free-ride when it's offered.)
There are lies, damned lies, and statistics.
I see you're one of those people who knows a few testing buzzwords, and thus consider yourself an expert in the field.
Just so you know, "UAT" refers to user-acceptance testing, not "usability testing" like you've mistakenly claimed. Usability testing checks whether or not the program is convenient to use, whether or not it's accessible to people with handicaps, whether or not it works well with various input and output devices, and so forth.
User-acceptance testing ("UAT") refers to testing that the client or user performs in order to ensure that the system meets their minimum requirements in terms of functionality, usability, stability, reliability, performance, and so on.
Oh, and your breakdown of the tests applied to each release level are pure bunk. They don't even correspond to Firefox's development practices at all. Please refrain from spewing mountains of bullshit the next time you post. Thank you!
Good god man, my FF never goes over 100mb, even with lots of tabs open. It averages at 70mb and i'm sure you can configure it to be even more minimal.
It's possible your build is bad. Are you using something stable and tested by your distro?
http://soylentnews.org/~tibman
I have a g1. You really need to use a task manager and uninstall anything that possibly runs at boot/in the background. They are just waaaay too ram limited. Also check out cyanogen mod as well as the 10mb RAM hack and turning on compcache and swap. My phone flies compared to stock android 1.6 and I have stuff on every desktop. Just keep getting rid of stuff till it gets smooth again....
zosxavius photography
BTW, the prices are in Euro but Slashdot can't show the symbol when I type it ... this is quite embarrassing for a geek web site.
It's not Slashdot's fault that UTF-8 doesn't support the euro symbol.