----- Original Message ----- > When you say "intent to implement" what is it you're planning on > implementing?
> * web activities between b2g-style webapps on Android Yes > * web activities called by sites loaded in the Firefox for Android browser? > * web activities provided by sites loaded in the Firefox for Android > browser? No. Not until some momentum on a spec is happening. > * webapps can call into native apps via web activities APIs (e.g. > sharing->native twitter)? Yes > * webapps exposing intents to native Android apps via activities? Ideally, yes > Intents do seem like a pretty fundamental part of an app ecosystem, but > there seems to be a big disconnect between the stated intent to > implementing them for Android and yet having no clear plan to > standardize them. I strongly feel we shouldn't ship this (to release > users on Android/desktop) until we have a stable spec. What's the point > of implementing this if we don't also have plans to standardize and ship it? Even though we only intend to implement activities/intents for webapps, we still plan to keep them off of Release (Beta and GA) until we feel the experience is working well enough. We don't have plans to implement activities/intents for general browser-based web sites. As you point out, we need some standardization first. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
