OEMs will always have the power to modify and lock down our code - that doesn’t 
mean we should’t try to provide a better default. 

I don’t think that answer to this problem is a technical one though, more like:
- making more information available to consumer so that can make more informed 
decisions when buying a phone
- doing better at trying to support our users (or more to support our community 
to support Firefox OS users)


On 15 Apr 2014, at 9:08 pm, Tim Chien <[email protected]> wrote:

> I don't think OEMs will leave this feature on on many phones -- many
> of the phones contain SIM locks and other customization bits, and they
> have the business incentive (or, requirement from their partners) to
> prevent people from removing them in day one.
> 
> How are we going to do with those phones?
> 
> On Tue, Apr 15, 2014 at 6:42 PM, Ben Francis <[email protected]> wrote:
>> On Tue, Apr 15, 2014 at 6:58 AM, Fabrice Desré <[email protected]> wrote:
>>> 
>>> One piece is to provide an *easy* way to change the update channel.
>> 
>> 
>> This definitely seems like the right solution for Gecko updates, and for
>> updates to Gaia apps which absolutely have to be certified. One use case is
>> providing an alternative release channel for security updates for devices
>> considered end of life by their manufacturers. But another use case is
>> providing a pre-release update channel for users to try out pre-release
>> versions of Firefox OS like they can with the Nightly, Aurora and Beta
>> Firefox release channels in order to contribute to the project by testing.
>> We should at a minimum be able to do this for the upcoming reference device.
>> 
>>> Another annoyance is that we still can't update gaia apps without doing
>>> a full update. That's pretty ridiculous to not be able to upgrade
>>> productivity and media apps for instance. That is blocked on some APIs
>>> being only available to certified apps.
>> 
>> 
>> We've discussed this before and I would really like to see as many as
>> possible of the Gaia apps move into the Firefox Marketplace so that they can
>> be updated independently of the OS like any other app.
>> 
>> Perhaps a good place to start would be to list the APIs that are forcing
>> each Gaia app to be a "certified" app, and look at which of those APIs we
>> could feasibly start to transition to being available to privileged apps, or
>> the web.
>> 
>> Ben
>> 
>> _______________________________________________
>> dev-b2g mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-b2g
>> 
> 
> 
> 
> -- 
> Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox
> OS, Mozilla Corp. (Taiwan)
> _______________________________________________
> dev-b2g mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-b2g

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to