Linked by Thom Holwerda on Thu 3rd Oct 2013 22:25 UTC
Mozilla & Gecko clones

Whether or not the Open fits your needs, one thing is clear: Mozilla needs more capable hardware to demonstrate Firefox OS' potential. The Open is good for someone whose alternative would be a basic flip phone, but the camera quality, connectivity, display and performance don't do full justice to the software.

A promising start, but clearly better hardware is needed. I'm really hoping Firefox OS gets a fair shot.

Thread beginning with comment 573853
To view parent comment, click here.
To read all comments associated with this story, please click here.
Lennie
Member since:
2007-09-22

The latest Android versions depend on faster hardware, you can't run the latest Android versions on cheap hardware. That is why you still see phones with Android 2.x on the market.

FirefoxOS doesn't depend on beefy hardware. It supposedly runs decent on cheaper phones for markets and people that don't want to spend as much money but still want a smartphone.

There are 6 billion people around the world with phones, only 1.1 billion of that are smartphones.

Reply Parent Score: 4

unclefester Member since:
2007-01-13

Plenty of phones that run Android 4.x are available for around $100 unlocked. eg Samsung Galaxy Mini 2 and Huawei Y300. Within 6-12 months all Android phones will run Android 4.x.

Edited 2013-10-04 09:05 UTC

Reply Parent Score: 3

Lennie Member since:
2007-09-22

Cheapest FirefoxOS phone is US $3 a month on contract. I don't know if Android has reached that point yet.

Anyway it's good that hardware improves, the more hardware improves and prices drop the better the webapps and webbrowsers run on Android phones and the more people can afford them.

Remember this is a Mozilla project, the web and webapps is the only thing they care about.

Webapps running on Android need 2 frameworks running on the phone at the same time: Android and webruntime. FirefoxOS only needs 1 to run webapps.

Many of the APIs Mozilla made for FirefoxOS have been proposed to the W3C and adopted:

https://wiki.mozilla.org/WebAPI

Even if FirefoxOS goes away, Android browser, Chrome, mobile IE, Firefox for Android, whatever else runs on mobile devices can adopt these APIs and webdevelopers can use them.

Their goal is for an open (web) option to exist. And with still almost 4 billion people with only a feature phone they don't have access to a proper webbrowser on their phone.

But Mozilla has done other things as well.

For example Mozilla and others at the W3c have been working on adding a (micro)payment system to the web.

You have to remember many of these feature phone users are using a pre-paid system, they don't have a bankaccount (thus no creditcard). (8% of the people in the US don't have a bankaccount either ! http://blogs-images.forbes.com/halahtouryalai/files/2012/09/underba... 28% of the people don't do all their finances through banks).

So other models are needed. One model is to tie the payment to the network operator. So you paid for your voice and data plan in advance in a shop and then part of that money can be used for paying other things when buying webapps or other goods on the web.

https://hacks.mozilla.org/category/payments/
https://payswarm.com/

When evaluating Mozilla projects, there is always a bigger picture involved.

This is about how the web is for everyone. Many people currently do not have similar easy access to information as you do.

Edited 2013-10-04 09:48 UTC

Reply Parent Score: 3

Lennie Member since:
2007-09-22

An other datapoint.

In the other comment I mentioned:

"Webapps running on Android need 2 frameworks running on the phone at the same time: Android and webruntime. FirefoxOS only needs 1 to run webapps."

Did you know more memory in your smartphone means less battery life ? (and running 2 frameworks means using more memory obviously)

Let's recap how a basic computer (thus also smartphone) draws power:
- CPU
- networking
- memory
- storage
- screen

When your phone is idle it goes to a sleep mode.

What is sleep mode ? I think it's basically suspend to RAM, right ?

So the CPU is idle, storage is idle and screen is blanked. On the networking side, your phone is sending and/or receiving keep alives from the cell tower.

But memory is still going: refresh, refresh, refresh, refresh.

If it wouldn't do that, the content would be lost.

So if your smartphone has less memory onboard, it will use less energy.

Maybe things have improved:

http://www.techspot.com/news/51750-smarter-design-cuts-existing-sra...

Edited 2013-10-04 10:19 UTC

Reply Parent Score: 3