|
Size: 1493
Comment:
|
Size: 3008
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| * [[https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/OSXHIGuidelines/AbouttheTouchBar.html#//apple_ref/doc/uid/20000957-CH104-SW1]] Touch bar guidelines... many bad, but interesting to see an all new product specified to this detail level... * [[https://www.filamentgroup.com/lab/bulletproof_icon_fonts.html]] |
|
| Line 4: | Line 6: |
| * [[http://qz.com/823204/graphic-design-legend-milton-glaser-dispels-a-universal-misunderstanding-of-design-and-art/?utm_source=dlvr.it&utm_medium=twitter]] | |
| Line 6: | Line 9: |
| * [[http://instrktiv.com/en/technical-writing-ux/]] manuals... good point since I hate FAQs, help, etc. but they do exist... | |
| Line 7: | Line 11: |
| * [[http://www.washingtontimes.com/news/2014/feb/9/soldiers-say-intel-tool-is-too-difficult/]] crappy systems kill. There are tech issues (slow) but unfriendly and hard to figure out? That's UX. | * https://cloudfour.com/thinks/ios-doesnt-support-progressive-web-apps-so-what/ PWAs still worth it, but I say the reason is that anything well considered is good, no PWA specifically. Just consider mobile first, last and mostly. Then everything is more efficient, etc. |
| Line 9: | Line 13: |
| * [[http://www.washingtontimes.com/news/2014/feb/9/soldiers-say-intel-tool-is-too-difficult/]] crappy systems kill. There are tech issues (slow) but unfriendly and hard to figure out? That's UX. (KEEP NEAR THE NEXT ENTRY) * http://www.ntsb.gov/investigations/AccidentReports/Reports/RAB1603.pdf speaking of IoT, we're using web 1.0 practices and keep trying to kill people; how there's no checks, no guardrails. E.g. why not design this to avoid accelerating so fast it hurts people, ever, regardless of commands issued at the moment. This is totally UX, as the intersection of software and reality/people is what the issue is always, but pure s/w devs don't consider reality nearly enough. |
|
| Line 10: | Line 16: |
| * https://www.bloomberg.com/technology undisruptable, or self-disrupting... cannot decide. But pick one. |
Describe November 2016 here.
https://developer.apple.com/library/content/documentation/UserExperience/Conceptual/OSXHIGuidelines/AbouttheTouchBar.html#//apple_ref/doc/uid/20000957-CH104-SW1 Touch bar guidelines... many bad, but interesting to see an all new product specified to this detail level...
https://www.filamentgroup.com/lab/bulletproof_icon_fonts.html
http://www.brainyquote.com/quotes/quotes/j/johnlasset490502.html IF I can find a full source for it
http://99percentinvisible.org/episode/on-average/ read all this. Suggested by lisa as relates to a11y. I think of the USAF/USN elimination of the non-norms. May fit as a reference on that page of that deck even.
https://m.signalvnoise.com/the-art-of-designing-with-heart-f5dc4df21697?gi=b2cbb05f4947#---0-183.bd3fcdl2y Read it. Maybe.
http://instrktiv.com/en/technical-writing-ux/ manuals... good point since I hate FAQs, help, etc. but they do exist...
https://twitter.com/stephanierieger/status/776114105656545280 on misapplying research. People treating computers like people doesn't mean you need to anthropomorphize them.
https://cloudfour.com/thinks/ios-doesnt-support-progressive-web-apps-so-what/ PWAs still worth it, but I say the reason is that anything well considered is good, no PWA specifically. Just consider mobile first, last and mostly. Then everything is more efficient, etc.
https://www.youtube.com/watch?v=_aygWy0dP3k&list= "My 20min talk-real-fast introduction to the Physical Web. I try to focus on WHAT you can build rather than the WHY" Scott Jenson
http://www.washingtontimes.com/news/2014/feb/9/soldiers-say-intel-tool-is-too-difficult/ crappy systems kill. There are tech issues (slow) but unfriendly and hard to figure out? That's UX. (KEEP NEAR THE NEXT ENTRY)
http://www.ntsb.gov/investigations/AccidentReports/Reports/RAB1603.pdf speaking of IoT, we're using web 1.0 practices and keep trying to kill people; how there's no checks, no guardrails. E.g. why not design this to avoid accelerating so fast it hurts people, ever, regardless of commands issued at the moment. This is totally UX, as the intersection of software and reality/people is what the issue is always, but pure s/w devs don't consider reality nearly enough.
On how R&D pays off http://www.wvgenweb.org/ohio/ww1-kindelberger.htm - I don't like failing fast to the public, and all this speedy lean, MVP stuff really. I say invest in R&D and fail /secretly/. Launch only great products. - Find quote about rabbits!
https://www.bloomberg.com/technology undisruptable, or self-disrupting... cannot decide. But pick one.
For a complete index of the monthly newsletters, see http://4ourth.com/wiki/Newsletter
To sign up for 4ourth Mobile Online Training, visit http://4ourth.com/Training/