canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
Mobile/Readabilityv2: Difference between revisions
→Where are we?
(→Notes) |
|||
| Line 4: | Line 4: | ||
==CURRENT STATUS & ACTION ITEMS== | ==CURRENT STATUS & ACTION ITEMS== | ||
===Where are we?=== | ===Where are we? As of 07/26=== | ||
Short answer: design | Short answer: investigation and design <br> | ||
√ Clear mission <== as good as or better than ios. Chrome also a good barometer for benchmarks<br> | √ 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<br> | √ 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<br> | √ High value bug fixes in flight for short term but focus is truly on providing a holistic solution<br> | ||
√ We have scrubbed through deferred bugs and have prioritized them; some of our overall platform and app logic investigations may trump the need for some of them, though, at this point, investigating fixes for the bugs are worthwhile<br> | |||
===What do we need to do next?=== | ===What do we need to do next?=== | ||