-
Notifications
You must be signed in to change notification settings - Fork 0
/
testinterface.html
373 lines (267 loc) · 20.1 KB
/
testinterface.html
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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
<!DOCTYPE html>
<html lang="en">
<head>
<link rel="shortcut icon" href="images/favicon.ico" type="image/x-icon">
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Nitesh Kumar's Portfolio</title>
<!-- Bootstrap -->
<link href="bootstrap/css/bootstrap.min.css" rel="stylesheet">
<link rel="stylesheet" href="fancybox/source/jquery.fancybox.css" type="text/css" media="screen" />
<link href="css/base.css" rel="stylesheet">
<link href="css/fonts.css" rel="stylesheet">
<link href="css/font-awesome.css" rel="stylesheet">
</head>
<body>
<div class="header">
<div class="container">
<div class="row">
<div class="col-md-12">
<div class="name"><a href="index.html">Nitesh Kumar</a></div>
<ul class="nav">
<a href="mailto:[email protected]"><li>Email</li></a>
<a href="https://medium.com/@thatnitesh" target="blank"><li>Blog</li></a>
<a href="about"><li>About</li></a>
<a href="index"><li>Work</li></a>
</ul>
</div>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-md-8">
<div class="project-name">Improving usability of a test taking interface</div>
<div class="project-desc">
Jukebox is a place to discover great music - from old classics to latest chartbusters. It is the intranet music player of IIT Roorkee. We decided to make it incredibly simple and easy to discover new music, see what is trending or find a track, album or artist.
</div>
</div>
</div>
</div>
<div class="ff-jb">
<img class="banner" src="images/banners/jb-banner.png">
</div>
<div class="story">
<div class="container">
<div class="row">
<div class="heading col-md-8 col-md-offset-2">Introduction</div>
<p class="text col-md-8 col-md-offset-2">
HackerEarth provides an interface where the developers can take programming tests created by companies. Their programming skills are assessed based on how they perform in these tests. If they score well, they are shortlisted and are invited for further interview process by the companies.
</p>
<p class="text col-md-8 col-md-offset-2">
This interface is very crucial because:
</p>
<ol class="text col-md-8 col-md-offset-2">
<li>It directly affected people’s prospects of getting a job.</li>
<li>It was an interface for taking tests. Most users had never seen it before. That means that there can be absolutely no learning curve.</li>
</ol>
<div class="heading col-md-8 col-md-offset-2">Problems with the existing interface</div>
<p class="text col-md-8 col-md-offset-2">
Sadly, based on the user feedback, it was clear that the existing was not very user-friendly. Users were having a hard time completing the most basic tasks, like submitting an answer after completion.
</p>
<p class="text col-md-8 col-md-offset-2">
Most frequent feedback we got from the users was
</p>
<ul class="text col-md-8 col-md-offset-2">
<li>“The interface is clunky.”</li>
<li>“I forgot to submit my answers.”</li>
<li>“I wanted to submit my answer but I by mistake I ended the test.”</li>
<li>“I don’t know which questions I have already attempted. It’s difficult come back to unattempted questions.”</li>
</ul>
<div class="col-md-4 story-small-box">
<a class="fancybox-button" rel="fancybox-button" href="images/testinterface/old1.png"><img class="story-img" src="images/testinterface/old1.png"></a>
</div>
<div class="col-md-4 story-small-box">
<a class="fancybox-button" rel="fancybox-button" href="images/testinterface/old2.png"><img class="story-img" src="images/testinterface/old2.png"></a>
</div>
<div class="col-md-4 story-small-box">
<a class="fancybox-button" rel="fancybox-button" href="images/testinterface/old3.png"><img class="story-img" src="images/testinterface/old3.png"></a>
</div>
<div class="col-md-12 caption">Some snapshots of the old interface</div>
<div class="heading col-md-8 col-md-offset-2">Design plan</div>
<p class="text col-md-8 col-md-offset-2">
We decided to figure out problems in the existing interface based on user feedback and complaints, and design solutions to mitigate these errors without making any stark changes.
</p>
<p class="text col-md-8 col-md-offset-2">
We wanted to solve the usability problems with moving as less pieces as possible. We couldn’t make any drastic changes in the layout or make any big changes that would increase the learning curve.
</p>
<p class="text col-md-8 col-md-offset-2">
We set out to improve the overall usability , readability and mitigate user errors with this redesign.
</p>
<div class="heading col-md-8 col-md-offset-2">Redesigning Multiple Choice Quesitons</div>
<p class="text col-md-8 col-md-offset-2">
We started from multiple choice questions. This question type was most prone to user errors. It wasn’t clear to users that they had to click the “submit” button after selecting an option.
</p>
<p class="text col-md-8 col-md-offset-2">
Earlier, users had to click exactly on the radio button to select an option and the options were not properly spaced out.
</p>
<div class="col-md-12">
<a class="fancybox-button" rel="fancybox-button" href="images/testinterface/old1.png"><img class="story-img" src="images/testinterface/old1.png"></a>
</div>
<p class="text col-md-8 col-md-offset-2">
I designed options as blocks. The option-text was enclosed in these boxes and they felt more tactile. Also, proper feedback was designed on hover. This feedback tells the user that the whole block can be selected.
</p>
<p class="text col-md-8 col-md-offset-2">
Once you select a block, a message floats right next to the submit button and attracts user’s attention to the “submit” button. Even if the user decides to change his answer, he will remember that he has to submit his answer after selecting it.
</p>
<div class="col-md-12">
<a class="fancybox-button" rel="fancybox-button" href="images/testinterface/mcq.mov"><video class="story-img" width="90%" height="auto" align="middle" source="" src="images/testinterface/mcq.mov" type="video/mov" autoplay="" loop=""></video></a>
</div>
<div class="heading col-md-8 col-md-offset-2">Coming back to unattempted questions</div>
<p class="text col-md-8 col-md-offset-2">
Earlier, question’s attempted/unattempted state was demonstrated by a dot right next to question number in questions listing. If the dot is grey, it means the question is unattempted. If it’s blue, it means you have already attempted it.
</p>
<div class="col-md-4 col-md-offset-4">
<a class="fancybox-button" rel="fancybox-button" href="images/testinterface/old-attempt.png"><img class="story-img" src="images/testinterface/old-attempt.png"></a>
</div>
<p class="text col-md-8 col-md-offset-2">
Candidates taking a test have a habit of leaving some questions for later. They want to attempt other questions and come back to it at a later stage. When there is not much time left for the test to end, the user wouldn’t want to be looking for these dots in front of these questions — if it’s blue or grey. That is exactly what was happening. They were having to search for unattempted questions.
</p>
<div class="heading col-md-8 col-md-offset-2">The solution</div>
<p class="text col-md-8 col-md-offset-2">
I designed a solution which makes it easier to come back to unattempted questions. Whenever you submit your answer for a question, a vertical blue line runs through the question in the list.
</p>
<p class="text col-md-8 col-md-offset-2">
The interesting thing is this blue line continues if you attempt the next question and breaks when you skip a question.
</p>
<div class="col-md-4 col-md-offset-4">
<a class="fancybox-button" rel="fancybox-button" href="images/testinterface/new-attempt.png"><img class="story-img" src="images/testinterface/new-attempt.png"></a>
</div>
<p class="text col-md-8 col-md-offset-2">
Now imagine, you have 10 minutes left in the test and you want to get back to the unattempted questions. You just have to look where the blue line is breaks. Wherever it breaks, it means that you have not yet attempted that question.
</p>
<div class="heading col-md-8 col-md-offset-2">Trending Songs</div>
<p class="text col-md-8 col-md-offset-2">
This screen, also the homepage of Jukebox shows the top 50 trending songs at all times. And since, it shows trending and not all time top songs, the score of each song (number of clicks) is halved every two days. So, in order for a song to trend for a long time, it has to played over and over otherwise it will move down the list.
</p>
<div class="col-md-12 img-wrap">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jb1.png"><img class="story-img" src="images/jukebox/jb1.png"></a>
</div>
<div class="heading col-md-8 col-md-offset-2">Artists</div>
<p class="text col-md-8 col-md-offset-2">
The artist view in earlier design was just a list of artists in alphabatical order and when you would select a particular artist you would be taken to that artist's page.
</p>
<div class="img-wrap col-md-12">
<div class="col-md-6">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jb-artist-list.jpg"><img class="story-img" src="images/jukebox/jb-artist-list.jpg"></a>
</div>
<div class="col-md-6">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jb-artist-page.jpg"><img class="story-img" src="images/jukebox/jb-artist-page.jpg"></a>
</div>
<div class="clear"></div>
</div>
<p class="para-gap text col-md-8 col-md-offset-2">
As the design evolved, we clubbed the two views together as it would save the user the trouble of going back and forth between the two views and make it easier to navigate through artists.
</p>
<div class="col-md-12">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jb2.png"><img class="story-img" src="images/jukebox/jb2.png"></a>
</div>
<div class="heading col-md-8 col-md-offset-2">Albums</div>
<p class="text col-md-8 col-md-offset-2">
The layout of albums in Albums view was kept asthetically the same as that of albums listed in the artist page but with a larger album art because why change something unnecessarily and it would make a lot of code reusable.
</p>
<p class="text col-md-8 col-md-offset-2">
We used the same navigation technique with albums as with artists. The alphabatical list of various albums is present on the left and when an album is selected it open on the right.
</p>
<div class="col-md-12">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jb3.png"><img class="story-img" src="images/jukebox/jb3.png"></a>
</div>
<div class="heading col-md-8 col-md-offset-2">Song And Album Interactions</div>
<p class="text col-md-8 col-md-offset-2">
While designing the new interaction pattern, I started with a single track - what all actions could I do on a single track on Jukebox. Once interations for a single track were setup, they could be easily applied to albums and artists.
</p>
<div class="col-md-10 col-md-offset-1">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jbw3.jpg"><img class="story-img" src="images/jukebox/jbw3.jpg"></a>
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jbw4.jpg"><img class="story-img" src="images/jukebox/jbw4.jpg"></a>
</div>
<div class="heading col-md-8 col-md-offset-2">Losing The Header</div>
<p class="text col-md-8 col-md-offset-2">
We got rid of the conventional header at the top. We were using high resolution cover images for artist pages and huge albums arts. As we already had the player fixed at the bottom, having a header at the top made everything appear dwarfed.
</p>
<p class="text col-md-8 col-md-offset-2">
If we had a header, it would primariliy serve as the space for the logo, the searchbar and user options.
</p>
<div class="col-md-10 col-md-offset-1">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/header.jpg"><img class="story-img" src="images/jukebox/header.jpg"></a>
</div>
<div class="heading col-md-8 col-md-offset-2">Search</div>
<p class="text col-md-8 col-md-offset-2">
So, we made a huge tradeoff by losing a conventional, big, simple looking fixed seachbar at the top when we decided to lose the header. Now, the search bar was nowhere to be seen except for a small search icon on the bottom player.
</p>
<div class="col-md-12">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/bottom-bar.png"><img class="story-img" src="images/jukebox/bottom-bar.png"></a>
</div>
<p class="para-gap text col-md-8 col-md-offset-2">
But once you clicked the search icon you got this entire screen for search on which you had to just start typing and it would look for songs, albums and artists. It had to be fast and the user must get the desired result on the quick results window itself.
</p>
<p class="text col-md-8 col-md-offset-2">
As we didn't really have any other input fields on the entire app except for search, we thought,"why not start searching for results whenever the user starts typing"! It would be as simple as thinking. As soon as you think of a song, just start typing it and jukebox will search it for you. No need to reach for search field. And you go back to the previous view by pressing Esc so that you don't have to move from your keyboard.
</p>
<div class="col-md-12">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jbsearch2.mov"><video class="story-img" width="90%" height="auto" align="middle" source="" src="images/jukebox/jbsearch2.mov" type="video/mov" autoplay="" loop=""></video></a>
</div>
<div class="heading col-md-8 col-md-offset-2">What Made The Cut</div>
<p class="text col-md-8 col-md-offset-2">
After numerous iterations and taking out as much as we could, this is what made the final cut.
</p>
<div class="col-md-12">
<a class="fancybox-button" rel="fancybox-button" href="images/jukebox/jb-cut.png"><img class="story-img no-border" src="images/jukebox/jb-cut.png"></a>
</div>
<div class="heading col-md-8 col-md-offset-2">What I Learned</div>
<div class="mini-heading col-md-8 col-md-offset-2">Process is just process</div>
<p class="text col-md-8 col-md-offset-2">
One process doesn't fit every project. The best process is the the one that suits you and your team. The best tools are the ones you are fastest with. The thing that matters is to hold the vision and to know how to build it.
</p>
<div class="mini-heading col-md-8 col-md-offset-2">Say no to most things</div>
<p class="text col-md-8 col-md-offset-2">
Yes, one of the most important things I learned. As you start to get something in shape and it starts to come together, it's very easy to get excited and lose your vision and hence the core value of the product. It's very imporant to make sure that whatever it is that you're building is not trying to do too much. When you started building it, you had that one problem in mind that it would solve. Keep that in vision.
</p>
<div class="mini-heading col-md-8 col-md-offset-2">Using the product</div>
<p class="text col-md-8 col-md-offset-2">
We wanted to build a product that we ourselves would love to use. And while building a product it's very eary to miss some invisible UX issues. They need to be discovered by using the the product.
</p>
<div class="mini-heading col-md-8 col-md-offset-2">Design a lot of stuff and throw a lot of it away</div>
<p class="text col-md-8 col-md-offset-2">
When I started designing jukebox, one day I would throw together something in photoshop and the next day I would think, "This is just stupid! What was I thinking!" and I would throw it way. I would try something else the next day. It's really important to sleep on it. It helps you envision what you want to build and more importantly what you don't want to build.
</p>
</div>
<div class="row">
<div class="col-md-8 col-md-offset-2">
<div class="project-nav">
<a href="index" class="home-link">HOME</a>
<a href="he-pricing" class="proj-nav-btn next"><span class="next-text">NEXT</span><i class="fa fa-long-arrow-right"></i></a>
<a href="channeli" class="proj-nav-btn prev"><i class="fa fa-long-arrow-left"></i><span class="prev-text">PREVIOUS</span></a>
</div>
</div>
</div>
</div>
<div class="container">
<div class="row">
<div class="col-md-12 footer">
<div class = "social">
<a href="https://twitter.com/thatnitesh" target="blank">Twitter</a>
<span class="social-sep">-</span>
<a href="https://medium.com/@thatnitesh" target="blank">Medium</a>
<span class="social-sep">-</span>
<a href="https://www.instagram.com/thatnitesh/" target="blank">Instagram</a>
<span class="social-sep">-</span>
<a href="https://in.linkedin.com/in/nitesh-kumar-86631925" target="blank">LinkedIn</a>
<span class="social-sep">-</span>
<a href="mailto:[email protected]" target="blank">Email</a>
<br><br>
© 2017
</div>
</div>
</div>
</div>
</div>
<!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
<!-- Include all compiled plugins (below), or include individual files as needed -->
<script src="bottstrap/js/bootstrap.min.js"></script>
<script type="text/javascript" src="fancybox/lib/jquery-1.10.1.min.js "></script>
<script type="text/javascript" src="fancybox/source/jquery.fancybox.pack.js"></script>
<script type="text/javascript" src="fancybox/lib/fancybox-load.js"></script>
</body>
</html>