This document discusses various aspects of coupling and interaction design in mobile applications. It addresses good and bad examples of coupling on Android and iOS, such as how apps are switched between. It also discusses using accurate text to represent backend processes, and using faster progress bars to reduce cognitive load on users. Visualizations are suggested to improve progress bars.

1. Android
Cloud
InteractionDesign

2. Materialise

6. Design for the Sense of Order

7. Design for the Sense of Order

8. Coupling

9. Good Coupling is S4

10. Bad Coupling on iOS 7
Bad Coupling on iOS 7

11. Bad Coupling on iOS 7Bad Coupling on iOS 7

12. Coupling
Make it smarter

13. Bad App Switching on Android
Showing ”current” app

14. Bad App Switching on Android
Showing ”current” app

15. Good App Switching on iOS
Showing ”next” app directly

16. Good App Switching on iOS
Showing ”next” app directly

17. Coupling
Reduce Cognitive Load

19. Now you know that there is a fifth star

20. Google Nexus Event Sept. 2015

21. What’s wrong with this?

22. Old/ New

23. New/ Old?!

24. Just those?

25. Coupling
Represent what's happening in the backend.

26. Loading.

27. Loading.
Not good all the time.

28. Authenticating with server..
This is better.

29. Retrieving your data..
This is better.

30. Signing you in..
This is better.

31. Coupling
We are crazy. Even for Progress Bars.

32. Visualizations, Faster Progress Bars. http://www.chrisharrison.net/index.php/Research/ProgressBars2

33. Visualizations, Faster Progress Bars. http://www.chrisharrison.net/index.php/Research/ProgressBars2

34. Visualizations, Faster Progress Bars. http://www.chrisharrison.net/index.php/Research/ProgressBars2

35. Visualizations, Faster Progress Bars. http://www.chrisharrison.net/index.php/Research/ProgressBars2
-
+

37. Affordances