On February 16, 2015 at 3:51:34 PM, Paul Theriault ([email protected])
wrote:
> On Thu, Feb 12, 2015 at 8:58 PM, Benjamin Francis wrote:
> > I would suggest we should aim to migrate the vast majority of apps
> > (including Gaia apps) to being web apps, but there are likely to be some
> > Firefox Apps which are basically Firefox OS chrome (like the system app) or
> > Firefox OS addons (like the dialer) and require chrome level type
> > privileges.
> >
>
> I did some analysis of the permissions used in Gaia to see how feasible
> this is. See[1] for data.
>
> This confirms some of the high priority APIs that we might want to expose:
> - deviceStorage:*
Maybe the Quota Management API? I've not evaluated it, but worth having a look:
https://dvcs.w3.org/hg/quota/raw-file/tip/Overview.html
> - contacts
There have been various attempts to do contacts - but they got caught up on the
whole web intents thing. I think we should redo contacts, and do it right. In
particular, something that allows something as simple as:
<input type="contact">
Alternatively, we could be smarter about, for instance, <input type="tel"> or
the like, and allow the user to select values from their contacts. There may be
other reusable things in HTML.
> - SystemXHR (hard to imagine this being exposed to the web)
CORS enables SystemXHR-like capabilities on the Web. That's already a solved
problem.
> - Camera: expose Camera API? Or add features to getUserMedia (latter seems
> more likely, but are their hardware risks/limitations)
Agree. How is basic support for things like?:
<input type="file" accept="image/*;capture=camera">
I see it's not supported on Firefox Desktop, for instance. Is it supported on
mobile or FxOS?
I'm told that WebRTC now allows for high-quality media.
> - Mobile Connection API is another popular one, but this is very dangerous.
Have you taken a look at:
http://w3c.github.io/netinfo/
What's dangerous about it?
> Maybe we could look at exposing more of the read-only attributes through
> the mobile-network permission but it has similar privacy implications to
> geolocation, only more difficult to explain to the user.
Then we can move to only enabling them through TLS, for instance. What use case
are we trying to address exactly? Are any of the use cases not covered here:
http://w3c-webmob.github.io/netinfo-usecases/
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
