This document discusses how user experience (UX) extends beyond the user interface (UI) and involves many other aspects of software development and delivery. It begins by defining UX and explaining its broader scope compared to user interface or usability. The document then covers how UX is impacted by activities throughout the software development lifecycle (SDLC) and various levels of the technology stack, including APIs, databases, infrastructure, and dependencies. Key themes that affect UX like performance, reliability, security and bugs are discussed. The importance of UX and challenges of UX work are presented. Finally, the document proposes approaches like planning for UX, user testing, advocating for quality practices, and emphasizing UX as a team

1. UX Beyond the UI
Joe Regan
UX Developer/Designer

4. User Interfaces
https://commons.wikimedia.org/wiki/File:Aldea_Digital_2013_01.jpg

5. Graphic Design

6. Usability

7. UX practices and activities
https://www.flickr.com/photos/gdsteam/20649386153

8. “I invented the term [User Experience] because I thought
Human Interface and usability were too narrow: I wanted to
cover all aspects of the person's experience with a system,
including industrial design, graphics, the interface, the
physical interaction, and the manual.”
Don Norman
(my emphasis)
http://adaptivepath.org/ideas/e000862/

9. What we’ll cover
•UI and UX activities in the SDLC & application stack
•Stack in-depth
•Themes
•Why it matters
•Challenges
•Approaches

10. UI and UX in the
SDLC and
Application Stack

13. Highly
detailed tech
stack diagram

14. Certainly these
have an effect
on UX

15. System components
that aren’t the UI
and their effect on UX

16. Application code
that’s not the UI

17. APIs and Services

18. Server-side
https://commons.wikimedia.org/wiki/File:Server-multiple.svg
Back end processes
Databases
Associated systems

19. Your network
and
infrastructure
https://en.wikipedia.org/wiki/Network_topology#/media/File:NetworkTopology-FullyConnected.png

20. Software your code
depends on
and its effect on UX

21. Frameworks and
components

22. Third-party
APIs or
platforms
Source:TechTarget Network

23. Platform and
version support

24. “iOS first”

25. Themes we’re seeing

26. Performance

27. 47% expect a web page to load in 2
seconds or less
40% will abandon a web page if it
takes more than 3 seconds to load
Sources: Akamai, Econsultancy, Think with Google

28. http://www.fastcodesign.com/3061519/evidence/the-ux-secret-that-will-ruin-apps-for-you

29. Behavior in low-
or no connectivity
situations

30. Availability

31. Reliability
https://pixabay.com/en/macro-focus-cogwheel-gear-engine-1452987/

32. Security

33. Nissan Leaf - unsecured API
http://www.programmableweb.com/news/poor-api-security-leaves-nissan-leaf-vehicles-vulnerable-to-hackers/2016/02/25

34. Accuracy

35. Steam server caching
https://eclecticlight.co/2015/12/27/unexpected-christmas-presents-how-steam-served-the-wrong-user-data/

36. Delivery

37. Bugs! https://commons.wikimedia.org/wiki/File:H96566k.jpg

38. http://www.nytimes.com/2016/01/14/fashion/nest-thermostat-glitch-battery-dies-software-freeze.html?_r=0

39. Why this matters

40. We are constantly
interacting with software

41. It wasn’t always this way
https://commons.wikimedia.org/wiki/File:NASAComputerRoom7090.NARA.jpg

42. How many different interactions with software is that?
The average person
looks at his or her phone
46 times every day.
Deloitte 2015

43. Failures are
more noticeable
Sources: TechCrunch, iMore, Reddit

44. Challenges

45. EMPATHY
Not your usual UX presentation
slide

46. And now I have to worry about UX too?

47. Are you committed to
quality?

48. Quality can lead to
better user
experiences

49. Quality practices
Unit testing
Code reviews
Test automation
agile processes
Continuous Integration
Continuous Delivery

50. Craft

51. If your users care that your system will work
tomorrow and the next day and six months from
now and that it can be updated effectively and
efficiently without stuff breaking all the time, then
they care about good software design.
Josh Schultz (@veryfancy)
http://veryfancy.net/blog/users-care-about-software-design/

52. I think in reality developers, even
experienced ones, tend to do a very poor
job of defending our practices in terms that
make sense to anyone else.
Chris Ammerman
http://www.whilenotdeadlearn.com/blog/2016/2/28/why-should-they-care

53. These practices lead to higher
quality software
This can lead to better user
experiences

54. Approaches to
improving UX

55. I’m not trying to get
everyone to do my
job for me
(honest!)
http://www.wikiart.org/en/norman-rockwell/tom-sawyer-whitewashing-the-fence

56. Plan and test for it

57. User Testing
Analytics

58. Involve the
team in the
UX process

59. Advocate for quality
practices in other disciplines

60. UX isn’t just UI, wireframes and user research

61. Development quality in all
aspects is key to user experience

62. UX is a team effort
DC Comics “The New Frontier” by Darwyn Cooke

63. We have to make sure we
are building the right things
and building them well

64. EMPATHY
Here’s a better
slide

65. https://twitter.com/KentBeck/status/566255102067871744

66. Build for others
as you would
have built for you

67. Thank you
Joe Regan
Red Arrow Labs
jregan@redarrowlabs.com
@jregan