00:11	$
00:13	$
00:18	%
00:22	%
00:24	Okay.
00:26	Okay everyone's ready.
00:27	Hello.
00:29	So we are here for uh for uh functional design.
00:33	@
00:37	Okay? So we are here for the functional design meeting mm # so first I will show the agenda so
00:49	we will uh I will take notes during this meeting so
00:54	I will try to summarise it and put that summary in the shared folder if you want to look at it afterwards
00:54	#
01:03	so then uh each of you will uh lead a presentation on the task that has been required last time so user requirement specification, technical function design and working design.
01:18	Then I will uh present you some new project requirements I received from uh the management board.
01:28	Then we will take uh the decision on on the remote control uh needed functions
01:36	and then I will assign you the task for the next part of the meeting. Of the - of the process. So uh who want to start the the presentation of what they did?
01:57	Mm.
01:58	F- do you want to start?
02:00	Make a start yeah. So. % Cable, camera. Should be in my - in their folder no? Up.
02:02	You can start.
02:04	#
02:07	You have uh PowerPoint?
02:13	Ah yeah maybe there. Okay. Who are you? $
02:18	Um at three I think.
02:21	No? # Mm.
02:21	#
02:27	Ouch.
02:29	#
02:29	And -
02:32	Okay. $
02:33	We have a technical problem uh.
02:37	Do we think w- s- in the - in the wrong folder maybe?
02:41	# It is possible.
02:42	You put it on -
02:43	No.
02:44	It was somewhere in something like this. I don't* remember the name actually must be something like messenger AMI or something.
02:49	What do you have in short cut?
02:51	Go up.
02:52	Participant two.
02:53	Yeah go up.
02:55	Yeah.
02:56	Again.
02:58	No. Go back.
03:00	You have no -
03:02	Uh maybe messenger AMI.
03:05	Messenger.
03:06	Over.
03:08	Okay.
03:10	No. There is nothing.
03:15	There's no -
03:16	Let's go and check. I'll go and check.
03:17	We have a technical problem.
03:19	Yeah. Otherwise, could you just describe
03:23	by hand? With the the whiteboard?
03:23	Okay.
03:26	Yeah.
03:26	If you remember yeah but that's -
03:28	Yeah. So uh. Basically # what we want here is a remote control right. # So um the question well first of all what to control. So # most people want to have a a remote for their hi-fi and T_V_ and stuff like that. And - but other people want th- also remotes for # controlling uh and toys like robotic pets and little robots and stuff and other people also want to have remotes for controlling um whole house.
03:34	Yeah.
03:43	Mm-hmm.
03:52	Mm-hmm.
03:59	Mm-hmm.
04:00	Yeah.
04:00	Yeah, so there's a project I think called X_ house or something like that that does that, uh you can integrate your remote with uh computers stuff. So # there is one - that is one thing. The other is the
04:09	Mm-hmm.
04:15	the finder feature yeah by whistling or whatever. Uh if you have the finder feature then you can also have
04:19	Okay.
04:23	uh at the same time as - and general voice commands if you want yeah.
04:27	Mm-hmm.
04:28	# So I think it should be a package in that case. Uh so the user interface will consist of two parts. # One is the voice command part and on- one is the actual buttons part. # Uh and th- the buttons part would be uh a set of buttons for choosing devices, a set of buttons for special navigation in space,
04:45	Mm-hmm.
04:49	Mm-hmm.
04:50	a set of buttons for # linear access of medium and a set of buttons for random access.
05:00	Okay.
05:00	Yeah?
05:00	What do you mean by linear access then?
05:02	Like a video tape goes forward, backwards, uh fast and stuff yeah.
05:04	Ah.
05:08	Um.
05:08	Okay so special navigation, linear access, random access and there's a fourth one no?
05:14	Mm?
05:16	So the better now for special navigation?
05:18	Yeah. For special navigation for example you might have a T_V_ in the menu and you going to change yeah? Uh.
05:22	Okay. Then linear access then random access.
05:25	Mm. Yeah and also parameter changing. # So if there are common parameters maybe we should put special buttons for that um or maybe we could have everything uh generic but uh there are a lot of uh remotes on the market right now and # basically this is most of the - almost everybody has this stuff.
05:28	Ah yeah parameter okay.
05:33	Okay.
05:43	Okay.
05:48	Okay and and voice command did you uh -
05:51	Voice command w- we could specify anything. We could assign any button - a command to any button, if we have enough processing power, I guess so. # Yeah.
05:54	Okay.
05:56	Okay.
06:01	Okay.
06:02	Yeah.
06:02	So that's uh that close your investigations?
06:06	Yeah. Uh yeah I think so. Not so far.
06:07	Okay.
06:09	Okay. Maybe we can have a look at the user requirements with -
06:13	Yeah. % Um I dunno if you can open the - uh m- is not here.
06:18	I dunno if I can open it. Maybe you can s-
06:22	It's -
06:23	Uh in -
06:26	yeah okay. No.
06:26	Messenger no?
06:28	In document ^@^.
06:32	Mm computer* yeah.
06:35	In which folder?
06:36	Where did you put it?
06:38	Here. Here.
06:40	# Short-cut to AMI shared folder?
06:41	@ mm.
06:42	But it's not -
06:44	Um.
06:47	Maybe you can send it to me by email.
06:51	Just to participant one.
06:56	Mm-hmm. Yeah, I can do that.
06:56	At AMI.
06:59	I will try to show it to everyone, that would be more comfortable.
07:04	Okay. Um.
07:09	You send it?
07:12	# It's participant one?
07:15	Yeah.
07:16	Uh this is this email.
07:23	I'm designing the user interface. $
07:44	Okay. You can uh.
07:48	Okay.
07:55	So maybe I can switch slides when you - whenever you ask, that will be more convenient. So okay, functional requirements.
07:58	Yeah.
08:03	Okay so- you can - you can go.
08:09	Okay so % in our usability lab we observed the remote control use among one hundred subjects and the subjects also filled a questionnaire* okay?
08:17	Mm.
08:22	Yeah.
08:24	And here I have the results so you can see that um seventy five per cent of users find most remote controls ugly so we have to find something to make them more
08:40	# more nice, more kind. Eighty per cents of users would spend more money when the remote control would look fancy. # Eighty hundred per cent of users would spend more money when the remote control would look - oh - to - it's not good. $ So okay. So it's not in theory - but I I can I can say yeah. #
08:55	$
08:55	$
08:59	We can just keep doing that?
09:02	Yeah.
09:02	Fifty f- uh seventy five per cent of users say they s- zap a lot. So mm # we have to have a remote control uh very um # out for that. $ Uh the buttons have - are to be um uh uh like you say resist- resisting to to shocks. $ Um and fifty per cents of users say they only use uh # ten per cents of but- of the buttons in the - in the remote control. So all the buttons we we have to put are - have to to have um a use a real use and not only or -
09:22	Okay.
09:31	#
09:33	Okay.
09:46	Okay.
09:47	Okay, so fewer buttons maybe would be good?
09:49	Yeah. F- not many buttons, and uh and uh uh u- useable buttons $.
09:57	Okay.
09:58	But what kind of remote controls did you look at?
10:01	Sorry?
10:02	What kind of task was it? It was a T_V_?
10:05	Yeah. Uh # most for most is T_V_.
10:07	Yeah.
10:09	Yeah but in fact we - it it seems that we are going to make a T_V_ remote control according to new requirements I received from the management bo- I will present them in the following. Okay.
10:15	Huh.
10:18	Uh-huh.
10:21	Ah! Good.
10:22	$ 'Kay you can go so.
10:27	So there are other frustrations expressed by users, so they said uh they lost uh often the remote control in in the room so they want to have a way to # to
10:38	Yeah.
10:44	To find it. Yeah.
10:44	to find it. Um and um lot of the time they - it takes too much time to learn how to use a new remote control. So they want something s- really* very simple and uh easy to use.
10:54	Yeah.
10:57	Mm-hmm.
10:59	Okay.
11:03	And uh remote controls are bad for
11:08	^R_S_I_^ $ um -
11:08	What is her other* side?
11:13	I dunno.
11:13	Other side yeah, yo- wa- your wrist.
11:16	#
11:17	It i- can become painful you can have tendonditis*.
11:20	Oh yeah? I did not knew that.
11:20	Yeah.
11:22	If you also @ up on a computer in a strange position.
11:25	Okay so you - we have to make it uh more ergonomic yeah.
11:27	Ergonomic. But uh $. Have to say ha ha. $
11:30	Yeah.
11:32	$ It's your job $ Oh. #
11:35	$
11:38	#
11:40	Uh.
11:41	Uh sorry $ got a message from Microsoft. $
11:46	$
11:46	$ Okay um before that I I have some some # some thing # uh to say before um -
11:55	Yeah.
11:58	Yeah yeah.
12:00	#
12:02	We know that uh the user* use uh a lot their um remote control um to to change channel. # Um and um to to change uh volume selection of the - and uh and not uh a lot for setting - for setting the the channels and uh thing- things like that. So it's better to put uh uh uh something very easy to set and uh and -
12:12	Yeah.
12:19	Okay.
12:26	Yeah.
12:29	Mm-hmm.
12:31	Mm-hmm.
12:31	Okay.
12:39	Yeah.
12:40	This function should be very uh accessible. Yeah, okay. This is the main function okay.
12:42	Very accessible yes.
12:45	That's right.
12:47	% So then we asked some questions to them and um we asked this question if they prefer an L_C_D_ screen or on their remultific- function remotes control and if they mm pay more for speech recognition in remote control and you can go # we have here the results of
12:51	Yeah.
12:54	Yeah.
13:04	Yeah.
13:10	The first question.
13:11	of the questions. So you know that um
13:18	#
13:18	# for the younger it's very important
13:22	To have L_C_D_ and voice.
13:22	to have the s- yes and speech recognition. And uh and the others is not so important but uh we know that uh uh people between fifteen and twenty five are people who watch a lot T_V_ and uh who who wh- can use a lot this uh. So maybe we we can have a speech recognition in. Yeah.
13:44	Okay.
13:47	Yeah maybe this this is important. Moreover th- maybe those uh like those teenager customer could advice their parents to buy this equipment and so we can - we have to take care of that point of view I think or so.
13:59	Mm.
14:04	Mm. Okay and if there is th- the conclusion now. So as we say before, I think uh um a remote control lightening in the dark it's it's a good thing. Uh not to many mud- buttons like we we said before, e- easy to use uh a way to find it easily in the room and uh uh resistant to to shock and to to -
14:06	Yeah.
14:18	Okay.
14:21	Yeah.
14:35	Mm-hmm.
14:37	Okay.
14:39	# An- I s- no, yeah. # I dunno if you see something else important or -
14:40	# Okay these are the user requi-
14:46	#
14:49	#
14:49	I'm just thinking of some thing. Um -
14:51	Mm.
14:51	Yeah.
14:55	We want to have a - no, I don't know if this is a good idea. We want to have a a general remote control for everything.
15:01	No no no. We - w- it seems that we no want to have a T_V_ remote control. From the management board I receive an email. Cos it would be costly
15:07	Okay.
15:07	Mm.
15:10	Yeah.
15:14	uh and and also it it would take more time to develop to have a a general generic remote control.
15:17	Yeah. Yeah yeah.
15:20	Yeah.
15:21	Mm - I - it's not true I think.
15:25	The the second claim that you put.
15:25	No no. #
15:28	That it would be too long to develop.
15:29	Yeah. I think that should be the same.
15:29	%
15:32	Oh yeah. Because I received that email from management board and they seems to tell that that if we want to be on the market as early as possible we should uh focus on T_V_ more where it seems that the market is more important.
15:51	So maybe it's a good decision. I dunno. What's your opinion?
15:54	I have uh I've no idea I mean I should know a bit more about how fast we can uh design it. I don't think -
15:56	%
16:01	#
16:01	$
16:01	$
16:02	Uh yeah.
16:03	Finish tonight. $ But basically yeah maybe I can continue with my presentation, it would be al- you - you - but I think we have some technical problem or so. So I'm just going to describe briefly what we do in the remote control. If fact -
16:05	Yeah. Okay. Yeah.
16:05	$
16:10	Okay.
16:11	Yeah.
16:11	Yeah.
16:18	Maybe you can go to the whiteboard if you have some drawings to do I don't know.
16:22	Yeah but -
16:22	Mm.
16:24	Do I have - oh yeah. Now I have enough cables.
16:25	$
16:26	Like a - you feel a bit like a dog with this stuff.
16:31	$
16:31	# Okay so I'm just going to describe - in fact for for a remote control this is quite easy. We just have - sorry, I'm going #
16:38	#
16:39	$
16:43	#
16:43	Okay. Are you okay? $
16:45	Like that. I'm just going to describe. Basically we have a a battery a power supply here. After that we just have um user interface. Let's say that
16:56	um
16:59	something like that, which could be um a L_C_D_ let's say or um an array of push button, something like that.
17:13	Push button or a L_C_D_. After that we we feed that into um
17:19	uh an electronic chip. So I say U_C_ and I feed that to uh L_E_D_ which is uh infrared - um which is a an infrared um component. And so what we - for for myself this - for for us this is quite easy.
17:40	U_C_ is the central unit?
17:43	Yeah. Y- it's a - it's - this just a chip which does all the um numerical
17:44	Okay yeah.
17:51	Computation.
17:52	numerical computation according to your display. And so for us uh this is quite easy. We just need to take - to define what we want to do when the user interface um wants something and after that we just do the coding to s- and send that to to to the - not the - to the television. So for us this is quite easy.
17:53	Okay.
18:16	Okay.
18:18	Okay so this is quite easy. There is not that much constraints.
18:20	Yeah. Um we just have to define the processing power that we need uh especially if we want to do some uh speech recognition, in that case that mean that we are going to use more for simple -
18:32	# This will - think this will take more time to develop also. Yeah. #
18:35	Yeah of course of course. And um but for a standard one this is really easy. It's a question of one month and so on s-
18:43	Soon.
18:44	To have a - you s- you speak about with voi- voice control?
18:48	No no no no, I say - yeah - standard uh standard remote control takes maybe uh one month to to do that.
18:49	Standard button one.
18:56	Yeah. So the only time problem is the sp- voice recognition*. Yeah. Yeah.
18:59	%
19:00	Yeah. Definitely.
19:03	So do you have any idea of how long it would take to have voice recognition now?
19:08	$ Ten years.
19:08	I would say $. I would say uh about eight months to have the first results.
19:10	$ $
19:10	$
19:15	$
19:19	Okay so i- it's a bit long yeah.
19:21	Yeah. I can -
19:27	Um.
19:34	One month for the standard one with button. Even if we have a L_C_D_ display?
19:36	Yeah.
19:39	Yeah even. I mean that this is really standard devices now.
19:44	Um eight.
19:47	For uh speech recognition.
19:53	Okay yeah.
19:57	Okay so we can take this into account. So who think it would be good to go for uh like speech recognition?
20:06	But we don't have time to market.
20:07	And also - how much uh I think
20:08	# Yeah it will.
20:12	I think we should contact management.
20:13	during the kickoff meeting you say that we we shouldn't - we shouldn't go up to twelve point five Euro per unit so how many units should we sell to have a -
20:14	%
20:21	Euros. Yeah, yeah.
20:31	Well. Uh -
20:32	Well each unit is is sell uh twenty five Euros.
20:35	Yeah but how many - yeah.
20:39	How muc- how much do you get - how much do you - if you buy one million units h- no, one hundred thousand units.
20:43	%
20:46	Eh chips. We're gonna need chips right.
20:48	Yeah.
20:49	Yeah. How much will it cost for one hundred thousand?
20:51	# Usually this is less tha- at two dollars per chip.
20:56	Okay.
20:57	Because we are -
20:57	So you have any* idea* for a powerful one that has uh good enough for do speech recognition.
21:03	Yeah, we can -
21:04	Yeah? Okay.
21:06	So. No it doesn't.
21:07	It seems that that we want to sell like four million units from the first meeting.
21:11	Mm-hmm.
21:15	Okay.
21:17	Four million. @
21:18	Okay. Maybe we can uh we can look at the new requirement I receive from the management board and discus- discuss all function we want to have.
21:28	Mm.
21:30	Um
21:33	I just had a question uh do you want to continue with your presenta-? Is it -
21:35	%
21:37	Yeah I I will continue. Well ask your question if you want.
21:39	#
21:41	Um you say that I don't remember by heart but thirty per cent
21:47	Mm?
21:48	of the tested people say that's it's quite difficult to to to use the remote control.
21:57	Yeah.
21:58	Do they say that this is difficult but for the same reason or do they have other reason?
22:05	Oh. Would j-
22:06	To to - maybe to keep in mind maybe to access to that menu you should do something like that.
22:11	Uh # yeah w- I I think they they say that it's uh difficult to learn how to use it but i- when you know how to use it, it's it's okay. But -
22:18	Mm-hmm.
22:20	Mm-hmm. And -
22:20	Okay. It's not intuitive first.
22:23	Yeah.
22:24	But yeah maybe and what about if we design a remote control which can be configure as you want? You say that I want, I have six button -
22:33	Mh-hmm. A a lot of people are uh - if you have the L_C_D_ screen if you can do it completely the way you want because the buttons also look the way you want them but it will be hard to configure I mean imagine i- uh - so it's really something for the expert user. So -
22:36	Yeah.
22:37	Yeah.
22:40	Yeah.
22:41	But, but also it seems that -
22:45	Yeah.
22:45	Yeah.
22:49	Okay.
22:51	I mean there are markets and markets. I think the young people are th- uh are uh - Christine here said uh you have a - # uh it is yeah. # So for our young people uh it will be cool, they can be able to use it. Th- maybe their parents will not but they will configure it. I guess. I don't* know if there is study about that.
22:54	%
22:58	Yeah.
22:59	Yeah.
23:09	Yeah. Maybe it would be more complex to configure it to be simple $ than creating a simple product.
23:10	Mm-hmm.
23:11	Mm.
23:12	Yeah. Yeah.
23:14	Yeah.
23:14	Mm.
23:14	Mm.
23:16	Yeah.
23:16	And there are - another thing is that if we make something that's simple and easy to use that's bas- to use immediately that means that it will be exactly the same as everything else. All right?
23:24	Yeah. Yeah.
23:26	Otherwise, if it's different then of course everybody has - somebody has to learn to use it first.
23:30	Yeah.
23:31	Yeah. But also we we see that that most people find it - find remote controls too complex because they have too many buttons and they mainly use only channels and volume buttons. So we may just uh make a very easy to use remote control with mainly those buttons and maybe also um
23:43	Mm.
23:43	Mm-hmm.
23:53	Yeah.
23:57	some lightning stuff too
24:00	because most people find also hard to to find the remote control.
24:06	Mm-hmm.
24:07	Losed- lose it etcetera.
24:10	These - these are - these two points are the main frustrations so maybe if we design something very simple and easy to uh find when lost it will uh add uh a serious competitive advantage
24:27	Mm.
24:27	without making something too complex and too long to develop.
24:31	Mm-hmm.
24:32	So but le- let us see first the new requirement. So we don't have to - so this this uh is uh is um in the this is in the same direction as we were speaking so we don't have to make a very complex remote controls to access teletext and stuff like that -
24:54	But teletext is just one button.
24:57	Yeah but then you have to - you have to define the buttons to surf amongst pages and stuff.
25:01	You you just write the - write the numbers.
25:05	Yeah.
25:06	So will you add with the channel keys, right?
25:06	So well -
25:10	Yeah. So anyway we don't have to include this feature because it's it's not used any more by users, they prefer to s-
25:10	So.
25:12	#
25:20	I am. I'm sure that uh it don't like but uh I don't see just one button.
25:25	Yeah. I dunno. If i- one button is still one more button. If - if - if we want to make it very simple we have to reduce number of buttons compared to th- to our competitors.
25:26	So.
25:38	Mm-hmm.
25:40	Well anyway I have this point. We can discuss. Also um - so as as I told before uh it would be better if it's only for the T_V_ um
25:57	because we want to be quick on on the market.
26:01	And then also we have to make very uh uh clear that this uh
26:09	this remote control is is part of of our products and show our corporate uh logo and and colours on the - on the design as well so that uh they identify it as one of our product.
26:26	So this is the the key point.
26:29	%
26:30	So before uh finishing we can uh define uh what would be the characteristic of the - o- th- of the control - of the remote control and which button do we need which function do we want etcetera.
26:47	Capital.
26:48	Mm.
26:49	$
26:51	So
26:53	do you um so so from from the the Marketing Expert I think
27:02	a key aspect is the easy to use aspect, it should be very simple and most button are never used only ten per cent of the button are are used often so I think we have to do something very simple and I think we all agree on that point, no?
27:07	Mm.
27:19	Mm-hmm.
27:20	Mm.
27:20	Well if it is going to be just a T_V_ remote control it is going to be very simple.
27:23	Yeah okay. So yeah the key point here is simple.
27:30	Maybe. # So few buttons, channel,
27:35	volume control
27:37	and what el- what function do you see
27:40	Well if it's going to be as simple as possible then just have the remote control, there is no other function* that I can see
27:41	in addition to that?
27:46	really.
27:46	Yeah. Maybe switch T_V_ on and off $
27:49	$ Uh no you want to keep television* on so that the advertising can - revenue can come back to us. Or something.
27:50	$
27:51	#
27:55	$ Yeah. Yeah. Volume, maybe a mute button, and then on off button.
27:57	%
28:03	Mm.
28:06	And that's all?
28:07	Uh I know that som- you say that many people are doing plenty of - a lot of zapping.
28:13	Mm.
28:13	Mm-hmm.
28:14	I know tha- I discovered that when I did a quick look, uh they do now som- they do something which is quite nice now, you have a button, you you press it, and this is uh the previous channel which has come back.
28:14	#
28:22	It's a memory, yeah.
28:26	Okay. Yeah this is cool. Maybe we can include that also. Previous* previous channel button. So we have like channel button, the previous channel button, the volume button, plus a mute button, and uh just the the traditional on off button.
28:37	Mm-hmm.
28:40	Mm-hmm.
28:45	Mm-hmm. #
28:45	And uh and of course the channel changing buttons*.
28:49	Yeah. I I talk about that, yeah?
28:50	How should they how should we implement that? Because uh could be numerical only or could be also incremental.
28:57	Yeah. Incremental definitely because zapping you you switch them.
28:58	#
29:02	Mm-hmm.
29:02	Let's say that we can do something like that. This is uh incremental*, but once you press it for a long time, you go five by five.
29:14	To go fa- to go faster.
29:14	We go faster?
29:18	Mm.
29:18	Mm. It's an interesting idea, that if you press it for a long time it does something else, in general. So if you you have your ten buttons for the - for the numeric- the numerical buttons and you have - instead of having just one memory
29:33	Yeah.
29:33	%
29:33	you have if you press them for a long time -
29:37	No. Doesn't work # does it.
29:40	Maybe we should have also a digit button -
29:44	Maybe we should have a complete keyboard and just type console commands. $ Change channel to eight.
29:46	$
29:47	$
29:50	Yeah.
29:52	$ Maybe we have also to have digits or only incremental. I dunno bec- because if you have the -
29:52	No. #
30:01	Well if it's useful like if if you want to change between three channels for example then you h- you cannot - you cannot cannot work with just memory being incremental.
30:05	Uh.
30:09	Yeah. Because you have your previous channel button if you have incremental only it's not uh it isn't worth it because the previous channel is eith- either minus one or plus one. $ So I think we need also digits. Maybe we we can make very obvious the channel and volume button* button and smaller button down there with the the digits.
30:15	Yeah.
30:20	Yeah. Yeah. $
30:25	Okay.
30:36	Yeah when you zap usually you will have to press the same button all the time [sound imitating pressing buttons] and -
30:39	Yeah.
30:41	# Or we can do something like that. We can design the remote control to have access. You know some remote control have uh protection and so you you y-
30:43	Yeah.
30:46	%
30:50	Mm-hmm.
30:54	Yeah.
30:54	You -
30:54	Hey I just thought this thing - there is a - I mean you know there is are some @ with a wheel like this. Instead of having the up down buttons for uh you can have the wheel. # Yeah.
31:01	Yeah.
31:02	Yeah, a kind of joystick.
31:04	Yeah. Maybe we can have a wheel for incremental. Okay. So have a wheel for incremental, have the digits uh on the lower side that can be closed so as you say protected,
31:04	#
31:07	Yeah.
31:14	Mm-hmm.
31:16	Mm-hmm.
31:18	# and uh yeah I think this is the basi-
31:20	On the lower side I think it - you have to turn it. No? If we do that.
31:21	And do we - do we have a -
31:25	Or a - or a ball, yeah, not a a wheel but a ball, and you say uh to -
31:29	No, a wheel is better. I would say the wheel is better. What is the expert of uh -
31:30	Yeah.
31:32	Because of that [sound imitating mechanical noise]
31:35	Yeah.
31:35	Because it's uh it's it's not like a volume which is smooth yeah? The channels* change one by one. So you have to the user has to like to should feel the the the discrete sense a bit.
31:40	Yeah.
31:44	Yeah, the - yeah.
31:45	Okay. Yeah. That's a good idea.
31:47	Yeah.
31:51	Well also we have to decide uh so it should be lightening in the dark I think because most people lost their remote control.
31:58	'S quite - it's quite easy we do that w- with back light on the - on the wheel.
32:00	Okay.
32:01	#
32:02	Yeah. Even if i- L_E_D_ uh or a- if if it's the L_C_D_ feature uh whatever, yeah.
32:05	A blue - a blue L_E_D_ and we sell that um.
32:07	Yeah, and do we put an L_C_D_ display? Because it was important for young customers if you remember.
32:08	#
32:08	Yeah.
32:14	# I think it's only put on if cou- have multi function. If you do not multi function then there is no p- point in having L_C_D_. Just increase the cost. # The user does not have an advantage really.
32:18	Yeah.
32:23	Okay.
32:25	So no L_C_D_?
32:26	Mm-hmm.
32:26	Hmm.
32:27	And so no speech as well because it w- it would delay too much the development process.
32:32	Okay.
32:32	Well if it's going to delay yeah but uh # it will be cool. It would. Because a user could say C_N_N_ for example and it would go C_N_N_. Mm.
32:38	Mm-hmm.
32:39	Yeah. That would be cool. But eight months is really long and -
32:42	Yeah.
32:46	Maybe we can just uh -
32:48	$ Ten years $
32:51	$
32:51	$
32:52	Okay. So um I I will uh - I will - so I- we will move to next meeting so in - after the lunch break uh here are the individual uh action uh you are required to do but you will be uh recalled to the actions by uh email I think but you can take notes if you - if you want but well the instruction will be sent. So
33:06	Mm-hmm.
33:25	thank you for uh your suggestion and I I will make a summary of that meeting that I will put in the shared folder you can't see $ and uh and then you will um you will be able to to see what has been uh has been said on on this meeting and and what has been decided. Uh maybe for next meeting uh send me your presentation before by email so that we can see them uh altogether. That would be easier.
33:26	Okay.
33:33	Okay. Okay.
33:34	$
33:58	Yeah. What is the folder that you put yours in? And did it it did work?
33:58	Mm.
34:02	# No.
34:03	No it did not work. She send it to me by email.
34:03	No no. I dunno, I dunno it.
34:04	Ah yeah. Mm.
34:06	Okay.
34:07	So maybe this is better, to send it by email. Okay? So yeah I I'm - it's in the first uh email so I'm participant one at AMI uh where is that, it's here.
34:10	Okay what is your email?
34:17	At participant one. Okay.
34:22	Participant one at AMI.
34:27	# Okay.
34:29	So see you after lunch break.
34:32	'Kay thank you.
34:32	Well during lunch break actually. $
34:47	So next time we should have a fight.
34:49	$
34:50	How about uh @ management or something.
34:54	Who happens to be your friend.
35:00	%
35:07	@

---