00:14	Is that alright now?
00:16	# Okay.
00:19	Sorry?
00:23	Okay, everybody all set to start the meeting? Okay, we've got half an hour for this one um to uh discuss the um functional design. All ready to go? Okay. Um so hopefully you've all been working away, and I've put the minutes of the last meeting in the project folder. Um so I guess just to to recap on uh what we did last time. Um kind of uh got to know each other a little bit and uh got familiar with all the equipment and started to discuss um a bit about the project, you know, cost-wise how much how much money we had to s-
00:27	Could you plug me in?
00:30	#
00:30	$ Okay. Thanks.
00:36	Okay. %
01:40	Um just want to tell you that you have three new requirements, um which is the - The first one # is that um uh the company's decided that teletext is outdated uh because of how popular the internet is. Nobody uses teletext very much anymore, so we don't really need to consider that in the functionality of the - of the remote control. Um they've also suggested that we um we only use* the remote control to control the television, not the V_C_R_, D_V_D_ or anything else. I think the worry is that if the project becomes too complex then it'll affect um how long it takes us to get it into into production, the time to market. So um, we're just gonna keep it simple and it'll just control the T_V_. And the other thing was that the company want the corporate colour and slogan to be implemented in the new design.
01:56	'Kay.
02:21	Okay.
02:30	Um I'm not entirely sure what the corporate colour is. It might be yellow, because there seems to be a lot of yellow everywhere.
02:37	And the slogan, like the actual written slogan, or just to embody the idea of the slogan?
02:43	Well that's the thing, I'm I'm not sure um
02:46	# uh th- because on the the company website, uh what does it say -
02:51	'Bout putting the fashion in electronics.
02:52	Uh something -
02:53	Yeah, I mean do they - # Is that something they want actually written on it, 'cause it's quite long.
02:54	Mm yeah.
02:59	Um or yeah, just the idea, but I'm not sure. So that's something we can discuss as well. So those are the three things, just not to worry about teletext, uh only control the T_V_, and um and uh incorporate the uh colour and slogan of the company. Um so is everybody okay with any of that, or do you want me to recap at all? Right um, time for presentations then. Who would like to go first?
03:22	Nope, we're all set.
03:29	# I'll go first.
03:30	Sure.
03:30	Okay, cool.
03:36	Alright um, can I st- steal this from the back of your laptop? Uh -
03:39	Oh yeah, of course, yeah. G- go on ahead.
04:11	%
04:18	@ so this is the technical functions design.
04:21	Um # -
04:25	Right @ to do the um # the design I have I've had a look online, I've had a look at the homepage, which has given us um some insp- inspiration from previous products. Um I've had a look at the previous products to see what they offer and um I would like to ask you guys for um # your ideas about the design at the end of the meeting. Um unfortunately we're not allowed to talk outside the meeting room, so -
04:34	Mm-hmm.
04:47	$ Okay.
04:47	Right.
04:48	Um, having a look at the existing products, I found out that um it tends to come in sort of two extremes, there's either um a very complicated one that's got lots of buttons, lots of colours, very confusing, you don't know what you're doing. # Um in that case the the labelling tends to be very bad. Um there's an example I'll show you at the end, um @ sh- show you now.
05:08	Uh - #
05:14	@ here um the button there and there. This one's prog*. Sorry. That one's perg* and that one's prog*, and it doesn't really tell you what it does.
05:15	# Alright @.
05:34	Um, not sure if you had a a look at the other um control in that example. Um it's a very simple one. It's got only the basic functions mm but um # it's the same size as the the hard to use one. # Uh it looked a bit clunky. They're very big and not very much use for @ buttons. # Um, # and it's just very hard to access the advanced functions. There's there's nothing for instance for a slow motion button.
05:45	Oop.
06:02	Um, my own preferences, I prefer the the clunky one. Um it's very easy to use. Um but unfortunately it does lack the advanced functions which I I quite like having on the controls. # Um so I believe the the advanced functions should maybe be hidden in a drawer, or something like tha- @ from the bottom of it.
06:21	So, # now I'd like to ask for your preferences. Um not sure of how long we've got, uh -
06:26	Um. Well we can chat away for uh for five minutes or so I think at at most. Just a couple of minutes anyway.
06:31	Mm-hmm.
06:33	M- yeah, like a lot of a lot of what I've um read and prepared for this meeting fits in really closely with what with what Craig's just gone over. So in part I could I could give you some of my personal preferences but I could also th- add some to this which is just about sort of um sort of market research. But anyway, um we might come to that later.
06:50	Mm-hmm. Shall we sh- well we'll stick to kind of your area for now.
06:53	Which which is the clunky one, the one on left or on the right?..
06:54	# Um, the clunky one is the one on the right.
06:56	Okay.
06:57	Um clunky in what sense, like um h- heavier? Larger? #
06:57	Yeah.
07:00	Um I think it's supposed to be the same size, but um it's got much fewer buttons. It's, you know, it's very spread out and kind of - you know, I get the idea it'd be sort of about this size. # @ got very few buttons on it and -
07:05	I see, so it's more just basic. Right, okay.
07:06	Looks kind of - Yeah.
07:11	Yeah.
07:12	%
07:12	Yeah. Sure.
07:14	Well I think it's a valid point. I mean like the one on the left looks quite um quite complicated, and that P_R_T_ p- P_R_O_T_ thing is incredibly confusing. Um so I see I see why yo- you know you might prefer the simpler design, but yeah you don't want to lose out on, you know, what it does, so maybe you know you know you get a lot of remote controls where you kind of flip the thing open, I think that's a good idea. I think it's a good idea. #
07:31	Mm-hmm.
07:34	%
07:36	Mm-hmm.
07:36	Mm-hmm.
07:39	Mm-hmm.
07:40	Um, # do we have any functions that um we'd want on it? I mean so far I've got um on and off, um switch the channel up and down, and put the volume up and down. Um they're just the the very basics you could use for a T_V_.
07:45	Mm-hmm.
07:48	Uh-huh.
07:50	Uh-huh, and then actual numbers for channels as well, yeah.
07:53	Okay. Um, you say that's a h- a required one or a requested one? Would you like um the channels like the the numbers on thing, um -
07:57	Which was that?
08:01	Up - the numbers, or the up down?
08:02	God, I wou- I would say that's required, I mean there's no way anybody's gonna buy a remote control these days when if you can't actually individually select channels, I mean would anybody disagree with that?
08:03	#
08:09	Yeah.
08:11	Yeah.
08:12	Um, what else, uh - # So don't need to worry about teletext, don't need to worry about V_C_R_, uh any kind of like display controls at all do you think we need to worry about, you know like brightness and contrast?
08:17	#
08:23	We don't? No?
08:26	Yeah.
08:27	Well I think I think es- essentially what we're doing right now is we're categorising. We're saying well we want this to be a product that offers all the sort of more tricky features but we want them to be in another area? Is that right? Is that what we're we're doing? We're kind of like sorting them an- Or are we actually eliminating things we just don't want the product to have?
08:33	Mm.
08:39	Yeah.
08:40	Um, yeah.
08:42	Um -
08:46	I think - are you are you maybe kind of thinking what we absolutely have to have and what would be nice?
08:49	Uh, to start with um sort of a bit both, um we need to find out exactly what we have to have um and after that we can add things if they're possible.
08:54	Mm-hmm.
08:57	Okay, right. Well, do you wanna maybe just, at this point decide on what we absolutely must have as a p- as a function of this. Um, so so far, just to recap you've got volume and channel control and -
09:03	Yeah.
09:05	Yep.
09:08	There's um on and off, um volume and channel, and skip to certain channels with the numbers.
09:13	Right okay. Um -
09:19	Well, one one way I would look at this um would be that we a- approach the different controls in terms of um like control types, so that for the user it's very clear what they want to do where they go. Uh and also think maybe a little bit about sorta w- w- what would just wanna be acc- easily accessible. For example if we had audio controls, those could be something people set up very rarely. Maybe they're un- they're they're they're in a little area but covered up um, things like channel and volume um are used all the time, so we just have them right out on top, um very just very sort of self-explanatory. Um so maybe we need to think about having three or more groupings of controls, you know like one which are just the the habitual ones that should be right within your natural grip. And others that are uh also available and then others that are concealed. Something like that.
09:31	Mm-hmm yeah.
09:38	Oka-
09:44	Mm-hmm.
10:12	%
10:16	Okay. Uh well, just to to wrap up quickly on this this little section - Have I just lost - Oh no. Um, uh do you think maybe that's the only kind of uh essential requirements, and then maybe just things that would be nice if it could do would be things like audio set up and display set up and things like that, maybe like a mute button, that sort of thing. Any of - you anything to add to that at all? No.
10:38	Yeah.
10:40	No. I'll add it later, I guess @ the presentation.
10:42	Okay, right. Um okay, if we can move on to next presentation then please. Um
10:43	Mm-hmm. Yeah.
10:46	%
10:49	Sure.
10:51	# Do you want to (switch) places?
10:51	Do you wanna -
10:52	Can this can this pl- reach? Can this plug come across? No.
10:54	No. No.
10:55	Probably not, actually.
10:58	@
10:58	So why don't I just pick up and move then.
11:00	Yeah.
11:01	Here, I'll just [whistling]
11:05	Why don't I just -
11:15	%
11:18	Mm er, can you go up- behind me? Kinda - This is so - This - I'm all in a knot now.
11:19	Just just switch them.
11:23	$ @ bit complicated. It'd be nice if everything was wireless, wouldn't it?
11:28	$
11:29	Okay.
11:31	Right.
11:32	#
11:35	Um. So I can I can say already, I dunno whether this is for good or for bad but there'll be a lot of kind of uh redundancy in the in the the issues and the the uh $ the things. Yeah, yeah. Which is ma- not necessarily a bad thing, but may- what I've already started doing is cr- I created a slide in in my presentation here so um so that we kind of think well what's the cumulative effect of what we've taken from your ideas and and mine, because certainly I I have a hard time separating separating things completely. Obviously obviously what you've just told me what you've just told me impacts a lot on what um like market research mm that that I've been - So how do I how do I get this up? Okay.
11:47	Oh, like overlap between what you said? Oh well, for all you know that - that'll happen.
12:09	Mm hard to know what - where your role ends, yeah.
12:17	Okay.
12:19	Um function F_ eight.
12:20	Uh pr- yeah, press function and F_ eight, yeah.
12:22	Okay.
12:25	Alright. So -
12:31	F_ eight?
12:32	Function, the blue button. Next to the control on the left. Yeah. You have to push it together.
12:34	Oh, and F_ eight. Okay.
12:35	Mm.
12:37	Mm-hmm.
12:38	Yep.
12:44	Okay, I think that that's doing it now.
12:49	Nope. Try that again.
12:52	Uh, again?
12:53	Think maybe the the wire in the back might be loose.
12:53	Wait.
12:55	Okay.
12:56	Yeah, you wanna -
12:58	Um, # okay great.
12:58	Oh oh here we go. There you go.
12:59	Yep, there we go.
13:02	Okay. Just um - Before I bring this up what I'll just say is um what I've what I've done is tried to collect some information so that I can then relay this to to you guys so that it's - now becomes a collective thing. And then kind of lead us in the direction of deciding, 'kay what what are our options, what should we decide and do you know what I mean, so.
13:19	@
13:21	Increase that 'cause we can't see the -
13:21	Um -
13:23	Okay.
13:25	Okay.
13:26	That's much better.
13:27	Right.
13:30	Can you um -
13:33	There you go.
13:33	Right, okay.
13:34	Okay. Alright. That would be -
13:37	Okay. So um does that make sense? So what I basically got is I just looked into some information and sort of th- tried to think about how how we could review it and how we could - and what kind of decisions we could take away from it and then maybe by the end of just looking at some of these things we can think about what are our priorities. 'Cause certainly there's lots of different information to go through. So um I'm thinking here about uh primarily about customer needs, that we start with the customer, and w- you know, what they want and what are issues with with um existing products. Uh to think about trends and also about - try and connect that as you see with the company vision which is about fashion in electronics. Um and then, as I say uh w- we'd like to prioritise our design features from this and um -
14:21	$
14:22	Dunno. Okay. Um. So this is what I've found here, um a lot of this is new to me, so we'll just read through together. Um, users dislike the look and feel of current remote controls. So they find them ugly. Most people find them ugly. Um # the vast majority would spend more money for it to look fancy as well, we'll see later, the vast majority would spend more money for um slightly more intuitive control, such as voice recognition. Okay I'm gonna - we'll look at that in a second. Um most people use only a f- a very* slim portion of all the controls. So I guess what we're looking at here is people want this h- technology, they tend to use the most simple controls and overall they find remote controls to be something they don't - doesn't really appeal to them.
14:23	Bouncing on top. $
14:24	Yeah.
14:51	Mm-hmm.
15:12	So I think what we're doing is we're trying to take like - if for me this is sorta like three different different um inspirations, you know, one is that we want uh something that's high-tech but we want it to seem easy. And in spite of the primitive side of it and the very high-tech side, we want it to just be an appealing piece of equipment in people's hands. Um, # frustrations. They get lost a lot, s- as it came up in our last meeting. Um, takes time to learn how to use them. This is uh why I mention when Craig was uh showing us some ideas that we actually try and group controls, so d- it doesn't just look like a big panel, kinda like when you you look at, you know, a new computer keyboard, or something that is quite explanatory. If you want audio, if you want visual, then you have those. Um
15:12	Mm-hmm.
15:59	and I will admit I don't know what R_S_I_ stands for.
16:02	Repetitive strain injury.
16:04	Is installing a new remote control something that people -
16:07	Uh, no, that did not come up at all. Um so here here is another um sort of a a review here of the main things. I also found that most people would uh adults at least would pay more for voice recognition. Now apparently we do have access to all the tech- cutting edge technology in remote control. So I dunno if that's possible we might consider getting into it. Um.
16:33	# And and again here as we sort of move m- sort of thin- start thinking about how we wanna sell and market this, I think a recurring theme here is the company wants it to be - wants us to make something that's fashionable and sleek and trendy. Um people # uh additionally aren't aren't liking the appearance of their products, so we wanna think about as we take all the sort of the techie features how we can um put that into a unit which is which people like. You know, they like the aesthetics and the ergonomics.
16:46	Mm-hmm.
17:01	Okay. So want something that looks good and is easy to use, big priorities. Okay.
17:06	Yeah. Yeah, so you know just c- looking at what what Craig um Craig's i- uh ideas are s- sorta tell me that maybe what we wanna do is try and um separate the different things that we wanna include in this. So if we do say well we want there to be all the technology will we try and make that almost be like optional technology. You know, it's like like I find a lot of T_V_s these days, something really like about 'em is if you wanna just turn 'em on and off you can, but they have little panels where you click and there's just like tons of features you go through.
17:37	Mm.
17:40	So it - you wanna group all the different kind of types of functions together, you know. That's - I think it's a good idea.
17:42	# Yeah.
17:45	Yeah. That's s- that's sort of the um - But I - I'm - my hope here is that I'm putting out this information so that we can then say okay, well how do we collectively move on with it. Um I I haven't brought out one specific marketing idea, although my sense is that what we should try and think about is what are the current trends in materials and shapes and styles, and then use that. But not let that confine us technologically.
17:56	Mm-hmm.
17:57	Okay.
18:06	Mm-hmm.
18:13	Okay. Right.
18:13	So-
18:14	Alright? Any um comments on all of that? #
18:19	# Well, um one of the things that we have to decide on by the end of the meeting is who we're gonna be um - who's our our target audience, our target market. Um, so if we want something that that looks good and is easy to use, but has y- is fairly powerful product, whatever, who do we really want to aim that at? I mean # -
18:19	That's uh -
18:27	Yeah.
18:38	Okay.
18:41	Where's the money, maybe.
18:42	Yeah, who wou- who would have the money to spend. Well i- if if like twenty five Euro is our is our selling price then you can imagine, well I don't - I'm not really sure how much that will retail at. But you want - it's somebody who's not gonna just use the remote that comes with their telly, I suppose, they're gonna actually go out and buy one. So, who do you think we're aiming this at?
18:44	Yeah. And who watches T_V_.
18:49	Mm-hmm.
18:52	Mm.
18:57	Mm-hmm. Yeah.
19:02	Um, I think it'll be the mid range to the high end market, in terms of people. 'Cause twenty five Euros for a remote, how much is that lo- locally in pounds?
19:11	# It's about sixteen, seventeen pounds, I think.
19:13	Is that too - is that a lot of money to buy an extra remote or a replacement remote? Right. Um so maybe not the high end range, but maybe middle, middle up-ish*. Kind of. You know how much? I dunno I guess you pay, what, ten ten quid for a remote? Like a simple replacement, right. I mean if you lost your remote and the first thing you just wanna go out and get, would you - how much would you pay?
19:16	Yeah, okay.
19:17	Mm-hmm.
19:25	Okay.
19:28	Okay.
19:33	Yeah.
19:35	Yeah, yeah.
19:35	Yeah. This this kinda touches on your comments there, David. These are the age groups which we have information on and these are - this is a table of h- what people would pay more for a certain feature. Just gives us a rough idea of where the w- the will to spend money on T_V_ equipment is. Mostly focused around the twenty five age group.
19:40	Yeah.
19:44	#
19:46	Okay
19:51	Okay.
19:54	Yeah, so do you think we're we're aiming at a fairly young market then?
19:58	Yep.
19:58	Sort of young professional, kind of. Mm-hmm
20:00	# Yeah, okay.
20:01	Um -
20:01	Um do you think then uh voice recognition is something we should really seriously consider?
20:09	What what do you think, Craig?
20:11	Well, did you not say it was the the adults that were going for the the voice recognition? Sort of the the older group.
20:16	Uh, yeah, it's the -
20:18	Yep. It does it does fit with the market that we're sort of identifying, in terms of -
20:19	Uh f-
20:22	N- yeah.
20:24	I think we are gonna have to narrow it down, to say let's target these people and give them what they want and 'cause you know, there needs to be some kind of selling point to it. So um anybody - anything there to add - Just kind of young professionals, uh th- like # if we are going to include speech recognition, it's kind of between fifteen and thirty five seems to be like a really high response to that. So we could say that was our target.
20:27	Okay.
20:29	Yeah.
20:29	Sure.
20:31	Sure.
20:33	Yeah.
20:47	Mm-hmm.
20:49	I I think twenty five to thirty five is is is fair to add that in as a group as well because that's more than half your group of people who are willing to at least try and use your technology.
20:53	Mm-hmm. Yeah.
20:53	Yeah.
20:56	Yeah, yeah.
20:57	Mm-hmm. Okay, so fifteen to thirty five, look fairly young. You know, they have bit of expendable income to spend on this sort of thing.
21:01	Yeah.
21:01	Yeah.
21:04	Mm-hmm.
21:04	I think perhaps that age group is significant as well because those are people who use the computer, who are familiar with their - with computers in in their everyday work. I think people who are maybe about - I wouldn't say thirty five, but people who are about forty-ish* and above now would not be so dependent and reliant on a computer or a mobile phone or something like that. So these are people who are gadgety*, right? People who are u- growing up used to, you know in schools and in universities, when you go on to their working lives, people who would you know regular- Yeah. Yeah. Mm.
21:08	Mm-hmm.
21:13	Yeah.
21:13	Mm-hmm.
21:15	Mm-hmm.
21:18	Mm-hmm.
21:20	Mm-hmm.
21:21	But - yeah.
21:23	Yeah, sure. $ Mm-hmm.
21:23	Yeah.
21:26	So -
21:27	Yeah.
21:28	Yeah. So they'll not sh- not shy away from something quite high-tech. That that's that's a good point. Um okay, so um - so shall we make the decision uh to include speech recognition if we can.
21:32	Yeah. So they'll not sh- not shy away from something quite high-tech. That that's that's a good point. Um okay, so um - so shall we make the decision uh to include speech recognition if we can.
21:35	Yeah.
21:39	%
21:46	If we can.
21:47	I I think one thing we should try not to avoid is not to say we have to use speech recognition right now, because um, based on what you've go- y- everybody's saying, right, you want something simple. You want basic stuff and you want something that's easy to use. Speech recognition might not be the simplest thing for somebody to use.
21:48	Yeah.
21:53	Yeah.
21:53	Okay. Why is that?
22:04	Right.
22:04	Okay.
22:05	Could it be an on off thing? Like if you want it on - Yeah.
22:07	Um, but what I'm saying is that we're we're trying to lock ourselves into a s- particular kind of technology, rather than focusing on on exactly what are the features that we're gonna say, and then, you know, say speech recognition is good for this, speech recognition is not good for this. So maybe we should - I suggest that we think about speech recognition, anyway* it's a - it's something that can be used to fulfil a function, but at end of the day we don't look at the technology, but we look at the function first.
22:08	Where you can activate it and deactivate it?
22:13	Yeah.
22:13	Yeah.
22:17	Yeah. Sure.
22:17	Okay.
22:22	Sure. Yeah.
22:23	Okay.
22:25	Sure. $
22:29	Uh-huh.
22:31	Yeah.
22:32	Okay. Uh okay, well do you wanna um give us your presentation and then then we can - I don't know - um might have been a good idea to all deliver our presentations and then discuss, but this is this is how we're - Yeah, exactly, yeah. Oh it's something that's just occurred to me as well is if we make it um speech reco- if we incorporate speech recognition, that's appealing to people um maybe with a physical disability as well. Um.
22:33	Sure. Yep.
22:37	Okay, sure.
22:38	Yep.
22:41	Yeah, it's good - well it's good to get ideas out while they're fresh in mind. Um -
22:55	Not -
22:59	Yeah. And not losing. And also it helps in terms of people not losing this, you know they - they're saying oh it's - I lose it in the couch. @ like we're kind of what we're b- sort of getting in- into here is mating different uh design features together that they -
23:04	# Yeah.
23:08	Yeah.
23:15	Mm-hmm.
23:16	I reckon one problem with speech recognition is um I've actually seen one of them used and uh the technology that was in that one wasn't particularly amazing, so you end up yelling at the control for hours. Channel up.
23:24	$
23:24	Right. Oh really, you've seen one before.
23:25	Really?
23:26	Do you think maybe we need like further advances in that kind of area until it's worthwhile incorporating it though?
23:27	#
23:29	Um - #
23:32	I think it'd probably quite expensive to put in.
23:34	Sorry, do you mind passing me my notepad. Thanks.
23:34	Mm. Course not. There you go.
23:37	Cool, um. Okay. Um. Well this is just the working design um. Well this is just what - how I would go about it. Um I guess I try to define like what we're doing now, try to define what we're trying to get done. Um I think in a practical way, we kind of know what it is. We've used it, we're familiar with it, but we're - we can't n- we haven't narrowed down um exactly what the things we're trying to fulfil, like - Besides the basics, I think back - in the back of our minds we know what the basics are. Has to change channels, has to change volume, but in like specifics, right, which one of the basics are you trying to target. Um are there certain parts of the basics that are more important or less important than the basics? Um and I just - the idea is just to get everybody to um - I usually # have a have have a design that's there as a basic, so, you know, things that - to start everything going. But I guess everybody does have some idea, so I don't think um there's a need for that.
23:41	Right.
23:44	Mm-hmm.
23:54	Right.
24:15	Mm-hmm.
24:36	Um okay this finding things is a little bit confusing, so I'll go into the diagram first. It just explains how the process goes through, from a - from the basic technology point of view, the basic steps that you need um in the diagram and in this slide probably works better. Um okay, you need some power source. 'Kay, a battery or something, to keep it going. Um and that power source is important because it ties you down to um how long the device will last. Um it ties you down perhaps a bit later on in terms of the technologies um how far you can transmit the signal or the complexity of the functions that you want. Like for example, voice recognition, right. That might be constrained because that - you might need to power a microphone, you might need to power other things, so that's one perhaps constraint there. Um
24:45	Mm-hmm.
24:56	Mm-hmm.
25:04	Uh-huh.
25:13	Mm-hmm.
25:25	# Th- Okay, the basic thing is there's a user interface where people punch a button or talk into it or smile to it or blink their eyes, whatever. You know, and that um picks up an input from a user, um uh a logic - a series of logic has to decide what the user is telling the device, and the device has to r- you know, based on you push button A_, so I will do something with button A_. So maybe button A_ is the power button, okay. Um and then it needs to be able to send the signal out to the device itself which is the receiver here. Um and I think that's about it in terms of my design um. It's fairly general, um and I guess the purpose of this is also not to restrict you in in the way you're thinking, like um voice recognition, right, um, if it's something which is important then we just add more power rather than having a thing that we don't have enough power. So it's not really a constraint in that sense, but I mean these are functionally, you know, the base, what the technology has to do. Um so I guess the rest of it - I think we should maybe you you wanna go back to what the functions are? I think that's more relevant to a discussion?
25:34	Hmm.
25:50	Mm-hmm.
25:51	Mm-hmm.
26:07	Mm-hmm.
26:18	Okay.
26:19	Mm-hmm.
26:23	Mm-hmm. Okay.
26:25	Okay.
26:25	Mm-hmm.
26:32	'Kay.
26:32	Uh. Well, do you wan- do you wanna finish up your your whole presentation then? Are you are you all done?
26:34	Sure. Sure.
26:37	Yeah, w- I'm done. More or less. Yeah. Ps- Oh, it's just putting the rest of it into words, but it's essentially the same thing. Um you have a transmitter, an input device, logic chip, you know, stuff like that. Um -
26:43	Yep.
26:44	Mm.
26:47	Okay.
26:49	Okay. Right.
26:49	Right.
26:50	And like on the - means - b- Since we're on the topic of the technology, uh are there any like - what are our options? Alright, what's what i- in - Is this the only way that we go about it, or are there other thin-
26:52	I guess this would be -
26:55	Yep.
27:03	Um, these these aren't technology options in that sense. This is just um a basic principles and basic components that are needed. For example, if you needed um if you needed to add uh a voice recognition, right, then your user interface would be split, broken down into more components, right, which you have a microphone, the V_R_ and stuff like that. Uh
27:06	Right.
27:08	The basic principle of -
27:09	Okay.
27:10	'Kay.
27:11	Right.
27:12	Mm-hmm.
27:20	$ Okay.
27:21	Mm-hmm.
27:23	Oh. So this just show how we're kind of modularising the whole thing. Okay.
27:24	Okay.
27:27	Yep. Yep. So each component represents one function, but I think the basic functions are the logic, the transmitter, um and the receiver, okay, and the power are things that you won't have to care about. Um and those are things that based on what your user interface requires then we'll add more functionality to it. Um there might be one other consideration which would be that the the transmission between the remote control and the T_V_ for example. Okay, um are we gonna restrict ourselves to using the traditional technologies of infra-red* thing? Because that's something you need to actually be physically be pointing to. Right.
27:31	Mm-hmm.
27:35	Mm-hmm.
27:39	Mm-hmm.
27:39	Yeah.
27:43	Mm-hmm.
27:45	Okay.
27:53	Okay.
27:54	# Okay.
27:59	Okay.
28:03	Right.
28:03	Okay. Well well a worry that was was expressed in the new requirements was that if we made this too complex it would e- it would effect um how long how long it took us to get this to market, so I th- suspect it might be a good idea just to restrict our kind of our creative influence on this on the user interface and not worry so much about uh how we transmit it um because I mean it- it's tried and tested intra-red, so we could stay with tha-
28:23	Yep.
28:27	There might be one other problem with the transmission, um in particular right now, since we're talking about voice recognition. Um if somebody's gonna h- talk to the device, you ideally want them to hold it to them. I- it - you may not require that, but you know, um it's it's it's something very natural, I guess, you know, to hold it, to signal to the user, and push a button maybe to start s- talking about it. Then you need to send the signal out, so because if you're using infra-red, the line of sight um say the T_V_'s at that chair, and I'm standing in front of here and the transmitter is here, it blocks it. So in that sense, there's not really a restriction but it's something which you may have to think about later on in the process. Not so much further down.
28:35	Mm-hmm
28:37	# Oh, yeah.
28:37	Right.
28:39	Right.
28:42	Yeah, mm-hmm. %
28:47	Okay.
28:49	Mm.
28:52	Mm.
28:56	Yeah.
28:58	Okay.
29:01	Right.
29:04	Okay.
29:04	Okay.
29:05	And um just a clarification before we finish this. Uh does c- is our controller is it have the option of being um on a standard uh frequency as all of the other equipment, so that the one controller can control several pieces of equipment?
29:19	There's there's not much specific specific information, but I think that um one indication of infra-red mean that you're just targeting traditional devices. Because infra-red is something which everybody has.
29:22	W-
29:28	Yeah. W- Well well we've um - In the new requirement spec they said just to focus on the T_V_, so that's what we should do for now I think. Something I was wondering about was the power. Um, is it worth considering like having like a charging unit as opposed to just regular batteries? I mean is that something we really want to go into, do you think, or should we just consider running on regular batteries?
29:28	Okay.
29:33	%
29:33	Just to T_V_, okay.
29:36	Okay.
29:47	There's a- there's - Okay, from from a from a component point of view there's added complexity, and you add cost to it, um and then there's probably the fact that you need another physical component. You need a docking cradle, for example, for you to put it in to charge. Or you need to get the user to plug it in. Um and most users are very f- use- already used to the idea of buying batteries and putting it into the controller. But unless the controller's gonna consume a lot of batteries, like he's gonna run through like twenty batteries a month, then I don't think rechargeable is something we should - you know, we really need to care about. Um.
29:52	Uh-huh.
29:54	Uh-huh.
29:59	Mm-hmm. Mm-hmm.
30:00	Yeah.
30:02	Okay.
30:03	%
30:04	Okay, so -
30:09	Yeah.
30:16	Yeah.
30:19	Yeah.
30:19	Okay, so just stick to to regular -
30:22	Okay.
30:23	Um, right. So basically* the um - I'm just gonna just recap uh what I said at the start, was that um the the whole point of this meeting was to f- absolutely finalise who we're gonna aim this at, and what exactly the product's gonna do. So um just to recap on - Are we all happy about the idea of um aiming the product at um the fifteen to thirty five bracket? Um and also the funct- the the actual functions of what it's gonna do. Do you wanna recap on that, Craig?
30:34	%
30:41	Okay.
30:42	Okay.
30:54	Yeah, that's good.
31:03	Um. I think we just say that it was gonna be the the most basic stuff possible. Um on off, up and down channels, up and down volume and uh skip to a channel.
31:04	%
31:14	Okay, right.
31:14	Ta.
31:14	And is it going to include any of the uh the more advanced features, or are we gonna eliminate those?
31:20	Um I think we include mute, but apart from that um I think we just - we'll go for the simpleness.
31:27	Okay. R- is it is it is it s- is it not an option still that we include some things just as a sort of under - like sort of under a door or some -
31:27	Okay.
31:28	Okay, I think-
31:34	Yeah, it's as optional functions.
31:35	Yeah.
31:36	'Cause what what I'm - I'd be a bit worried about is if someone was h- had previously developed habits of expecting to control surround sound or this and that with their controller and then and then they, you know, w- they get ours and w- it's doesn't have that. I dunno if that'd be a problem.
31:54	Okay. #
31:56	Another thing that you were saying about categorising the controls? Um maybe I could suggest we we break them down into three simple categories. One would be audio controls, one would be video controls, and the other one would be a device. Um this may not map very well to advanced functionality especially, but I think that um from a manufacturer's point of view, from a person designing the device, but I think from a point of view of a person using the device, you know a T_V_ is something they see and something they hear, um it's something they do other things to like turn it on and turn it off. I mean like so what we could have is like three buckets, right, where we could throw things into, like if we want this feature, let's throw it into there, and then from there decide whether it's basic, or it's non-basic. I mean it might help with the visualisation. And it would actually help with the component build as well.
31:59	Mm-hmm.
32:04	Yeah. Okay.
32:06	Mm-hmm.
32:08	Okay.
32:17	Yeah.
32:25	Mm-hmm.
32:29	Yeah.
32:30	Right.
32:32	%
32:35	Yeah.
32:38	'Kay, okay. Like that.
32:40	Okay.
32:43	Mm-hmm. Mm okay, great.
32:45	Okay, right. Um, okay well I gotta kind of - got five minutes to wrap up now. Um next thing we're doing is having lunch. Whoohoo. Um and then we're gonna have thirty minutes of working on the next stage. Um so I'll be putting the minutes of this uh this meeting into the project documents folder. Um so uh I guess just to just to confirm that we know what we're doing in the next - well in the thirty minutes after lunch anyway, um for uh our Industrial Designer, you're gonna be thinking about the components concept. Um User Interface Designer gonna be thinking about our user interface, and marketing you're gonna be thinking about trend watching. Um and you'll all get specific instructions as well. So um I dunno, just just to to ask now if you've got anything else you've thought about while we've been talking. Um, do you wanna start with David. Anything else to say at all? No, okay. # Andrew?
33:05	Mm-hmm.
33:11	Mm-hmm.
33:14	#
33:36	#
33:42	Mm no, not really.
33:44	Um yeah, just - I just wanted to ask then before we wrap up, shall we agree for sake of um sort of clarity and when we when we r- resume that we'll u- use this idea David's proposed, where we think of these three sort of buckets and anything anything we discuss about them is sort of, okay, we're talking about this. Shall we do that, then? Okay, great.
33:57	Yeah, yeah I think that's definitely a good idea.
34:01	Mm.
34:01	Uh-huh. Yeah.
34:04	Um just about the three buckets, um what would go in the the device functions one?
34:08	Um things like on off. Because they don't have anything to do with what you see. I me- mean in terms of picture and the entertainment value, you know, um so um - And channel. Because the on off also goes, you know, like on off like power, not on off sound. Not on off video. Although you don't turn off the video on your T_V_, but um you might wanna you know turn off the sound, say you wanna pick up the phone, there's a mute button, right, so you you have you have a choice of putting it on to um others or a device. Device is basically anything which we can't categorise, right. We put it out.
34:12	Yeah.
34:18	Okay.
34:20	And and channel.
34:20	Um -
34:21	Right.
34:26	Yeah.
34:31	Okay.
34:35	Okay.
34:44	Okay, so you're gonna have um audio which is gonna be like you know your bass settings and actual volume - hi- Okay.
34:49	Mm-hmm.
34:50	Yeah, anything to do with what you hear, right. You you put that into audio. And then video is anything that you can see. Um.
34:52	Mm-hmm.
34:53	Okay, and then visual -
34:53	Mm-hmm.
34:57	Mm-hmm.
34:57	Okay, so brightness, contrast, things like that, and then just actual device things, like what channel you're watching, turning on an off, stuff like that. Okay, um -
34:59	Yep.
35:00	Colour, yeah.
35:02	Yep.
35:03	Sure.
35:04	Sure.
35:04	Yep.
35:05	Okay.
35:08	And then k- I suppose quite likely what would happen is in the d- device category there might be some which are just like the habitual standard and then others which are maybe a bit more - Yeah. Sure, okay. Okay.
35:16	Like random which we have no other place to put, but we need it somewhere there. Um even even if it doesn't map very clearly what happens is that people at least have some in their mind. It's easy to use, I think that's one thing that um - and I guess from the component point of view it's easy to build as well 'cause things are like fixed. $
35:16	Mm-hmm.
35:18	Yeah.
35:20	Okay.
35:30	Okay.
35:33	Okay.
35:33	# Okay. Um so yeah, I guess just things to think about are you know like the fact it's gotta look good, because of who we're we're, you know, targeting this at. Um something maybe kind of quirky in design maybe. Make it kind of ergonomic kind of to hold, you know, things like that. Um, # so I guess I guess that's it. That's the meeting over. Whoohoo.
35:36	%
35:45	Mm-hmm.
35:47	Mm-hmm.
35:53	Great.
36:02	Then we get to go find out what was picked up for lunch for us. $
36:04	$

---