>
> > Even if that does not end up being the best approach for the Camera API,
> > such a UI element might be useful elsewhere (e.g., as an option for SMS
> > apps that don't want a full-screen SMS approval dialog).
>
> When does SMS app have to show a full-screen SMS approval dialog?
> Regular content have to use intents-like system and other content will
> just be able to use the API, AFAIK.
>

You can theoretically use Intents to send something silently in the
background, or you can use Intents to open a full-screen SMS dialog that is
pre-populated where the user just hits "Send".  Which do you mean?  I think
the former is a bad idea, and the latter does not satisfy many apps that
send text messages.  (Handcent SMS, for example.)


> I doubt that many applications would require a specific UI. On Android,
> for example, most applications are very ok with using intents to pick a
> camera instead of re-building a camera picker.
>

That is untrue.  Many apps use the direct API call for taking photos.


> This said, apps that require a custom UI would have to just use the
> Camera API. An intent-like system would solve most use cases but not all.
>

I have no objections to also supporting an Intent system where you open the
full-screen Camera app, which returns a stream of data.  The question is
what to do for all the apps that this does not satisfy (which is a very
large number of apps).
_______________________________________________
dev-security mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security

Reply via email to