Mobile/firefoxhome/08-08-2011: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 40: Line 40:
* [http://developer.apple.com/ue/ User Experience]
* [http://developer.apple.com/ue/ User Experience]
* [http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/Intro/Intro.html Human Interface Guideline]
* [http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/Intro/Intro.html Human Interface Guideline]
== Security  ==
Points for consideration
*'''User History Data'''
**Storing this data for users will likely result in Mozilla eventually receiving official inquiries on particular user data for criminal investigations.
**If this model is selected appropriate staffing, budgeting and processes will need to be in place to handle these requests
**Alternatives: There aren't obvious alternatives at the moment since the intended use of the application is to provide quality information to the user based upon search history. Therefore, the server side needs access to the plain text data.


== Other ==
== Other ==

Revision as of 20:36, 8 August 2011

« previous week | index | next week

Dial-in

  • 650-903-0800 or 650-215-1282 x92 Conf# 265 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 265 (US)
  • IRC channel #fxhome
  • Room: MTV 3Z - Zombocom
  • Vidyo: tbd

Agenda

  • What is remaining for next milestone
    • BrowserID update
    • iOS App update

Engineering Update

Front end

  • New grid layout

Server

Add-on

iOS App

  • What is missing?

UX and User Research

Design

  • App icon design
  • Visual design for add-on UI

Research

QA

Security

Points for consideration

  • User History Data
    • Storing this data for users will likely result in Mozilla eventually receiving official inquiries on particular user data for criminal investigations.
    • If this model is selected appropriate staffing, budgeting and processes will need to be in place to handle these requests
    • Alternatives: There aren't obvious alternatives at the moment since the intended use of the application is to provide quality information to the user based upon search history. Therefore, the server side needs access to the plain text data.

Other