canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
Mobile/Readabilityv2: Difference between revisions
→CURRENT STATUS & ACTION ITEMS 7/16
| Line 4: | Line 4: | ||
==CURRENT STATUS & ACTION ITEMS 7/16== | ==CURRENT STATUS & ACTION ITEMS 7/16== | ||
Where are we? | ===Where are we?=== | ||
Short answer: design phase | Short answer: design phase<br> | ||
√ Clear mission <== as good as or better than ios. Chrome also a good barometer for benchmarks | √ Clear mission <== as good as or better than ios. Chrome also a good barometer for benchmarks<br> | ||
√ Clear approach <== implementation decisions will be based on providing a superior user experience | √ Clear approach <== implementation decisions will be based on providing a superior user experience<br> | ||
√ High value bug fixes in flight for short term but focus is truly on providing a holistic solution | √ High value bug fixes in flight for short term but focus is truly on providing a holistic solution<br> | ||
===What do we need to do next?=== | |||
[madhava,ibarlow] comparison of 5 sites in order to visually depict preferred heuristics; from there we can extrapolate features<br> | |||
[madhava] engage UR <== he will let me know when I need to invite them<br> | |||
[ibarlow] look into purchasing fonts<br> | |||
[elancaster] collect feedback/reviews with comments specific to readability/font inflation for FN14<br> | |||
[sjohnson] look into readability.js and add to wiki<br> | |||
[mfinkle] spec reader mode details for scott to review<br> | |||
==Schedule== | ==Schedule== | ||