Confirmed users
2,959
edits
(Created page with "== Comments == "This document covers the product requirements for the Android WebRT, code name "Soup", for the June, 2012 milestone." (jsmith) Curious, why is June 2012 picked ...") |
|||
| Line 1: | Line 1: | ||
== Comments == | == Questions and Comments == | ||
"This document covers the product requirements for the Android WebRT, code name "Soup", for the June, 2012 milestone." | "This document covers the product requirements for the Android WebRT, code name "Soup", for the June, 2012 milestone." | ||
| Line 9: | Line 9: | ||
"Tier 1 App Support" | "Tier 1 App Support" | ||
(jsmith) Could you define what you mean by "support?" | (jsmith) Could you define what you mean by "support?" Does this mean that Soup needs to be able to run the app with its major points of functionality with no issues? In other words, could you be more specific about the quality requirements? | ||
"Improve User Experience Issues" | |||
(jsmith) Could you identify specific pain points in our user experience currently that we want to aim for? | |||
"Publish "Mozilla Marketplace" in Android Market" | |||
(jsmith) Will this be a beta or GA? | |||
Open Issues/Risks | |||
(jsmith) Might want to add "tracking and ensuring fixes of evangelism issues," specifically in regards to top apps (tier 1s especially). | |||
User Scenario/Stories | |||
(jsmith) Suggestion - In wording user stories, instead of using "Alice" as a default name to a user, point out the stakeholders interested. For example, | |||