Changes for page Graphical User Interface

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -31,19 +31,19 @@
31	31
32	32	== Landing Page ==
33	33	There is first a connection page. When opening the app, the user is required to pick their role, as shown in the picture below. Then, they log in with their credentials (log in page not shown).
34		-[[image:homepage.png||width="1000" height="560"]]
	34	+[[image:homepage.png||width="800" height="448"]]
35	35
36	36	== Patient Page ==
37	37	This page has for objective to display every potential interaction that the PwD could make use of when communicating with Pepper. In case the PwD wants to directly start an activity with Pepper, they can also see them from the app. This also allows for checking which activities are currently implemented on Pepper for the specific PwD.
38	38	We defined the first row as potential activities for the PwD to do, and the second row as potential use cases where the PwD may need Pepper's help.
39		-[[image:patientux.png||width="1000" height="560"]]
	39	+[[image:patientux.png||width="800" height="448"]]
40	40
41	41	== Patient's relative Page ==
42	42	This page has for objective to display every potential interaction that the patient's relative could make use of regarding Pepper.
43		-[[image:patientrelativeux.png||width="1000" height="560"]]
	43	+[[image:patientrelativeux.png||width="800" height="448"]]
44	44
45	45	== Healthcare professional Page ==
46	46	This page has for objective to display every potential interaction that the patient's relatives could make use of regarding Pepper. Most interactions of the HCP are about editing the patient's information or preferences.
47		-[[image:hcpux.png||width="1000" height="560"]]
	47	+[[image:hcpux.png||width="800" height="448"]]
48	48
49	49	[1]: Molich, R., & Nielsen, J. (1990). Improving a human-computer dialogue. Communications of the ACM, 33(3), 338-348.