Mozilla.com/Mobile in Mind/Challenges: Difference between revisions

Mozilla.com/Mobile in Mind/Challenges (view source)

Revision as of 22:19, 14 July 2011

918 bytes added , 14 July 2011

no edit summary

Jasongrlicky

156

edits

@@ Line 1: / Line 1: @@
-For the 2011 Q3 "Mobile in Mind" project, the first step is to identify a list of aspects of the site which will not translate directly to mobile. This will serve as an outline for the design process, where we address each of these challenges one by one to develop reusable design patterns. We should be able to then apply these patterns to mozilla.com on the pages listed here, and get a site design that can be more easily made mobile-friendly.
+For the 2011 Q3 "Mobile in Mind" project, the first step is to identify a list of aspects of the site which will not translate directly to mobile. This can serve as an outline for the design process, where we address each of these challenges one by one to develop reusable design patterns. We should then be able to apply these patterns to mozilla.com to get a site design that can be more easily made mobile-friendly.
 =Mobile in Mind Challenge List=
@@ Line 8: / Line 8: @@
 ===Examples===
 ====Site-Wide:====
 * Main menu drop-downs operate on hover
 ====Specific Pages:====
+* Top Features box rollover - http://mozilla.com/firefox/features
+* Personas hover-on-preview interaction - http://mozilla.com/firefox/customize
+* http://mozilla.com/firefox/technology - Example rollovers
 * Tour page features rollovers - http://mozilla.com/firefox/central
-* Top features box rollover - http://mozilla.com/firefox/features
-* Personas hover interaction - http://mozilla.com/firefox/customize
 ==Large Amounts of Content Won't Fit==
@@ Line 26: / Line 25: @@
 ====Specific Pages:====
 * http://mozilla.com/firefox/fx - Possibly too much copy on headlines
-* http://mozilla.com/firefox/features - Too much content per section, even if we were to create an expandable UI -
+* http://mozilla.com/firefox/features - Too much content per section, even if we were to create an expandable UI
+* http://mozilla.com/firefox/technology - Really a lot of content, especially including examples.
+* http://www.mozilla.com/en-US/firefox/central/ - 8 Steps is a lot of content for a small screen
 ==Content Must be Linearizable==
 Since the small amount of screen real estate on phones necessitates a linear browsing experience, the information hierarchy must be clear enough that making the content on a page linearized does will not confuse the user.
+===Examples===
+====Specific Pages:====
+* http://mozilla.com/firefox/technology - Sidebar is of ambiguous importance
+* http://mozilla.com/firefox/central/ - Pop-ups can be difficult on Mobile, especially with a lot of content in them.
 ==Horizontal Space is at a Premium==
@@ Line 39: / Line 45: @@
 ====Specific Pages:====
 * http://mozilla.com/firefox/fx - The content of the spinning wheel popup is horizontally oriented, and the panda graphic takes up a lot of horizontal space.
+* http://mozilla.com/firefox/customize - The Add-ons gallery categories employ a tab metaphor that requires a lot of horizontal space.
+* http://www.mozilla.com/en-US/firefox/video/ - Horizontal navigation for videos may be awkward.
+* http://www.mozilla.com/en-US/firefox/central/
+** We won't be able to fit the large image on small screens and keep the same level of detail.
+** Absolute positioning of tooltips will be tricky at small screen widths.
 ==Complex JavaScript Animations Will Not Perform Well==