Yeah. It's alright. Um  Alright , I've done some research for functional requirements. Um  yes. The working method um  there were hundred uh uh w h one hundred people , uh how do you say uh , f watched using remote controls in the usability lab and they also uh filled out a questionnaire uh with a few questions. Uh , I've lined them up here. Uh , ask whether um common remote control looks good or not , about willingness to spend money on remote control , about zapping behaviour , and uh and stuff like that. I uh have found some interesting things. We do we do got a market. Um ,  three out of four people claim m uh to find remote controls ugly. So if we make a trendy design , we sure have seventy fi seventy five percent of the market , which you can reach. Um , three out of four users uh zaps a lot , as I uh quoted here from the uh results.  Zap buttons are used one hundred and sixty eight times per hour. That's quite a lot. Um ,  relevant options are , of course , power buttons. Although , only used once per hour. Uh , channel selection , volume and buttons for text , and the more um , yeah , other functions , like audio settings , video settings , sound settings are not said to be very important and uh very much used. Furthermore , fifty percent says uh they only use ten percent of the buttons on a remote control. That doesn't say we got  we can leave ninety percent off. But it sure um says we shouldn't make it too uh complicated. Fifty percent also claims uh to have lost a remote control very often in the room. And um  an important thing here , the most important customers uh , which is over seventy percent of our market , is in the age range of thirty six to sixty five years old. And uh elderly people , our market , are less interested in uh nice features , but more willingly to spend more money on remote controls. So ,  what I was thinking  oh , wrong side. We shouldn't implement too much features on uh on our remote control , because elderly people will get th lost. Group features for a higher usability , uh what I was claiming in the previous meeting. Um , all the settings , about audio settings , video settings and channel settings , which are not very often used , we could group them uh on one button and make them accessible uh in one menu button or whatever , because they are used very rarely and well , it uh  there are a lot of options there , so we can really make uh  yeah , how do you say , we can spare at buttons over there.
Okay.
And um , if you want to implement V_C_R_ and D_V_D_ options , group them in the button , not too uh   Yeah. Small buttons , so they won't be very um , how do you say
Visually presents.