Firefox OS/Geolocation: Difference between revisions

m
remove extra "="
mNo edit summary
m (remove extra "=")
Line 5: Line 5:
The underlying implementation can be different for different hardware providers. As a developer, you should be transparent to the underlying implementation, and write apps using the APIs which specifies whether you want enableHighAccuracy or not. eg: if you are writing a navigation app, which needs accuracy upto a few meters, then enableHighAccuracy=TRUE. If you are writing a weather app which just needs w coarse location, then your app can consume less power by enableHighAccuracy=FALSE.  
The underlying implementation can be different for different hardware providers. As a developer, you should be transparent to the underlying implementation, and write apps using the APIs which specifies whether you want enableHighAccuracy or not. eg: if you are writing a navigation app, which needs accuracy upto a few meters, then enableHighAccuracy=TRUE. If you are writing a weather app which just needs w coarse location, then your app can consume less power by enableHighAccuracy=FALSE.  
   
   
==Commercial Implementations=
=Commercial Implementations=
Mozilla does not produce Firefox OS images for commercial devices-- we provide source code to chip manufacturers and OEMs.  These parties customize various parts and create binary images for devices.  The final Firefox OS image is mostly representative of what we have in the public source repositories.  This is an important distinction because the configuration of some parts (like linux config, device setup, etc) is not in Mozilla's hands.
Mozilla does not produce Firefox OS images for commercial devices-- we provide source code to chip manufacturers and OEMs.  These parties customize various parts and create binary images for devices.  The final Firefox OS image is mostly representative of what we have in the public source repositories.  This is an important distinction because the configuration of some parts (like linux config, device setup, etc) is not in Mozilla's hands.


canmove, Confirmed users
312

edits