Is it okay ?
Thanks.
Alri
Yeah , and that's fine. Okay. So , basically , the method that we usually use in the user interface design is that we need to look at what people like and what people don't like about existing products. So , in our case , existing remote controls. And then , what the good ideas are , and what the bad ideas are , and why they're bad and good , which isn't always as obvious. We seem to have intuitions about why things are good or things are bad , but when you look , technically , at how it works , sometimes that's not the case. Then we need to decide what functionalities we really want to keep , 'cause that'll feed into both Ed's work and Christine's work. Um and then what the remote control should look like , obviously , once we've got a good idea of what the functionalities are. So , in terms of the functionalities that we need , you obviously need to be able to turn the T_V_ on and off. You need to change channels , both by directly going to a specific channel or by channel surfing. You need to be able to control the volume and then control any menus on the T_V_ to regulate contrast or whatever. So , the problems that people have expressed is that there's too many buttons on remote controls , in general. The buttons  it's not clear what they're supposed to do. Um often , you need to know specific button sequences  to get certain functionalities done , um which you don't necessarily always remember , especially if it's a functionality that you don't use very often. And that the buttons are too small. So , here we've got two examples where here on the left-hand side , you can see a remote control that has lots and lots of buttons.