-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy path132Project.html
More file actions
110 lines (87 loc) · 3.93 KB
/
Copy path132Project.html
File metadata and controls
110 lines (87 loc) · 3.93 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
<!DOCTYPE html>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<link rel="stylesheet" href="DannyStyleSheet.css" type="text/css">
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE-edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title> 132 Project </title>
</head>
<body>
<ul>
<li>
<a href=index.html>Home</a>
</li>
<li>
<a href=ProjectList.html>Projects</a>
</li>
<li>
<a herf="#">Socials</a>
<ul class="dropdown">
<li><a href="https://www.twitch.tv/barista_ace">Twitch</a></li>
<li><a href="https://www.linkedin.com/in/dannyaceshafik">LinkedIn</a></li>
</ul>
</li>
<li>
<a href=aboutMe.html>About Me</a>
</li>
</ul>
<div class="paddingit">
<h1>
132 Project
</h1>
<div>
<h3>Role: UX Designer</h3>
<h3>Project Type: UX Project</h3>
This project was done in my Informatics 132 class at UCI. We were making a prototype of an application and had to go through a lot of iterations just to get to something we liked.
<br>
<br>
First, we came up with a problem statement <strong> How do we help with consistency in the workplace for professionals </strong>
<br>
<br>
we soon realized that our problem statement was too vague and we adjusted it to <strong> How do we help people with time blindness stay consistent with time management </strong>
<br>
<br>
Soon after we edited our problem statement we did a competitive analysis.
<br>
<br>
<img src="Productivity App Competitive Analysis.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
Then we made an affinity diagram to help us figure out which features and aspects of our application we’d like to have, what our target audience would be struggling with, and how to tailor the application to that audience
<br>
<br>
<img src="Productivity App Affinity Diagram.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
After which we created a persona of who our target audience would be. That way we could have a solid grasp on who we need to design for.
<br>
<br>
<img src="Productivity App Persona.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
Then we made storyboards on what situations our application would be effective/ helpful to our user.
<br>
<br>
<img src="Productivity App Storyboard 1.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
<img src="Productivity App Storyboard 2.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
We then made lofi prototypes of our application.
<br>
<br>
<img src="Productivity App Lo-Fi Prototype 1.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
<img src="Productivity App Lo-Fi Prototype 2.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
Then a mid fi prototypes
<br>
<br>
<img src="Productivity App Mid-Fi Prototype.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
Then a Hifi prototype.
<br>
<br>
<img src="Productivity App Hi-Fi Prototype.png" alt="A picture of a stickman, surrounded by monsters" />
<br>
And after all those steps our team decided that we got the application to a state that we could actively work on.
</div>
</body>
</html>