Whilst sat around an open fire drinking sherry and wearing Santa hats, James and Per record a podcast about podcasts. In this meta-show we explain how podcasts help us in our work. What is it that makes us like a podcast? What kind of challenges do podcaster face in producing awesome shows? Finally we recommend a bunch of podcasts that we listen to and explain why you should give them a try.
Pour yourself a glass of something nice and enjoy the last UX Podcast show of 2013.(Listening time: 49 minutes)
— UX Podcast (@uxpodcast) December 27, 2013
- Stitcher (all the podcasts recommended are available on Stitcher apart from the two with links provided to RSS Feeds)
- UX Podcast interview with Nathalie Nahai
- The Good, The Bad and The Dirty – RSS feed
- Sex Nerd Sandra
- The Big Web Show
- UIE Brainsparks – RSS feed
- The Psych Files
- Snap Judgement
- The Dirt
- UX Podcast on Spotify
James and Per are both fans of quantified self. In this show we take a look at what quantified self and life logging are. We chat about some of the potential benefits plus some of the challenges that surface from a UX and user perspective. Is quantified self ready for mainstream, or is it still a play thing of early adopters and gadget geeks?(Listening time 37 mins)
— UX Podcast (@uxpodcast) August 9, 2013
- Jawbone UP
- Fitbix Flex
- Nike Fuelband
- Nike+ sensor (and Nathan sensor pouch)
- Cognitive behavioural therapy
- No link between fatigue and sleep
- Kevin Kelly
- Steg-för-steg med Fitbit Flex och Jawbone UP (Per’s blog post, in Swedish)
James: Hello and welcome to episode 53 of UX Podcast with me James Royal-Lawson.
Per: And me Per Axbom.
James: It’s a little bit odd when we do that the other way around. Not as often we do it that way.
Per: No, that’s true. I usually start off. It feels kind of weird.
James: It’s like wearing someone else’s underwear.
Per: Yeah. It’s August 6th of 2013. It’s a Tuesday today, I think. I have been working a bit that I’m off again and I’m actually at the summer house now.
James: I’m at Beantin HQ.
Per: Yeah. I’m sitting in a really hot car because this is the only place I could find that would be silent.
James: You’re in your car!
Per: I’m in my car in the passenger seat because I have five kids I’m taking care of. Well, two of them are mine at the summer house here. So it’s really loud.
James: Beantin HQ is 29 degrees at the moment. I’ve got two, maybe three kids. I don’t really know, to look after. I’m clearly not doing it very well.
Per: Instead we are recording.
James: Exactly. Well, OK, let’s jump into it. First of all, welcome back to all of you in Sweden who have bothered to start working again and is starting to listen to the show.
Per: Right. A lot of people are returning this week and next week …
James: of our Swedish audience..
James: …We can see that they roll back into work now and start listening again. So, hello there. Welcome back. Today though, we’re going to be talking about quantified self and life logging. What’s all that about?
Per: Well, interesting that you should ask James because I think we’ve talked about a bit before, you and I, about life logging and what’s the difference between life logging and self quantification. The gist of it is that you gather as much data about something as you possibly can to like make out trends and behaviour of yourself or in trips you’re making, your weight, whatever.
So usually when you talk about quantified self, you’re talking about data that you’re collecting about yourself and your body and your behaviour but life logging goes even beyond that. I think one of the hugely massive great examples that’s making the rounds and it should have been out by now is the Swedish innovative Kickstarter project Memoto where you actually have a wearable camera. You could even argue that that’s quantifying yourself but it’s also quantifying your life and what you’re seeing around you.
So that’s a camera that you attach to your clothes and it’s taking a snapshot. I don’t know what it is actually. It’s maybe every 30 seconds something. Yeah, something like that. So once you start doing all this life logging, you’re starting to see trends and behaviour because then you can see maybe from the photos. You see what you’re eating or how much you’re exercising and the gadgets that you and I will be talking a lot about today, the wrist bands that we wear to monitor our sleep and see how much we moved during the night. You can connect that and how badly you sleep, to exercise, and how much you’re moving around where you’re checking in.
Sometimes you see trends which could be quite interesting and that’s the incentive or the appeal for people to actually realize stuff that they haven’t realized before about themselves, but also to be able to look back I guess to previous behaviour and previous data about yourself that has changed over time.
James: Yeah. I’m just going to have to go and shut the window.
Per: Oh, absolutely.
James: I can hear the kids that I’m meant to be looking after far too much. I don’t want to hear them at all. So just hold on a second.
James: So sounds are gone. Yeah, well for me, the quantified self aspect is when you gain insights from the data you gathered by various means whether it’s weighing yourself or taking pictures every 30 seconds or counting how many steps you’ve done and so on.
Per: You could argue even then that it’s a variant of behavioural therapy that to be able to change your own behaviour you need to become aware of your own behaviour and that’s the basis of behavioural therapy. So what you’re doing here is automating that using a device of some sort. Well, it can actually be that you’re entering data yourself but as long as you’re doing it consistently over time.
James: Well yes, exactly. I think it’s just – like all statistics, you’ve got to be careful to make sure that you understand what you’re reading and what it is that you’re looking at. So for self-improvement or the behavioural therapy side of things, I mean if you look at a chart that tells you you’ve had this much sleep, and you believe it’s correct, you’re going to be changing your behaviour best on that information.
James: And whether it’s correct or not is something that’s questionable.
James: Or how correct is it.
Per: Exactly, how correct is it and what type of conclusions should you be drawing from the data.
James: Yeah. One of the reasons I mentioned just that is because I have a Jawbone UP band.
James: Which I wear on my wrist. It says – looking down at the wrist, realizing it’s not there. Where is it? Then I’ve just remembered now, I put it in my pocket, which is a thing in itself actually that I have to put in the pocket around that, but I will get to that. Now I have a Jawbone UP band I wear and I keep it on during the night as well and it measures steps during the day and it measures how little I move during the night and from how little I’ve moved or how much I’ve moved, it judges whether I’ve been sleeping deeply, lightly or awake.
James: Now this produces lovely little graphs. I think the Fitbit Flex that you have, you know collection, does a similar thing. It measures how little you move and produces nice little sleep graphs.
Per: Exactly, basically the same output from these different devices actually.
Per: To be clear, I have the Jawbone UP as well before and we both had it while we were travelling to UX Lx. So we were sort of comparing the data we were getting from that as well at that time, which was really interesting.
James: It was very interesting because we were sharing a hotel room as well so we had very similar sleep patterns because we were going out together and so we’re waking up together.
Per: Oh my god. We’re going there again.
James: Oh, really. Anyhow, what you could see was that you Per for example, you actually – my wife as well. You’re very still during the night.
Per: Yeah, exactly.
James: So even though you’re awake, it doesn’t register you’re awake because you’re not moving enough and my wife, when she was using hers at first, she ended up getting to the habit of when she woke up during the night, she would shake her arm so that the UP knew she was awake. So it would register an awake moment.
Per: So basically telling the – that’s how you talk to your arm band. You shake it …
James: Yeah, which is silly really. But no, but for her that was her pattern of sleep. So to try and improve the graph, she was doing this kind of – she was having to work a little bit extra to get better data but that’s a learning thing. when the app presents the graph to you, it doesn’t really – there isn’t really so much talk about it’s inaccuracy or potential inaccuracy. The marketing and the drive of a lot of these quantified self things is this is how much sleep you’ve got. This is how many steps you’ve taken.
Per: Yeah. When you open up the app, it actually tells you you’ve been awake seven times this night.
Per: And the funny thing about that is that a lot of people are going to take it literally because it is presented literally.
James: It is presented literally.
Per: Yeah, and that pisses a lot of people off and they realize, “Well, I haven’t been awake that many times.”
Per: And you have to start interpreting the data. Well, that means that you’ve moved around quite a lot perhaps seven times during the night and you may and may not have woken up specifically during those times.
James: You want to peel back a little of the UI effectively and say OK, when it says this, it really means this. My wife, she actually stopped using her Jawbone UP for two months, the last couple of months, because she just got so disappointed that it wasn’t really telling her how much sleep she was getting and I explained to her in my usual way. Well, of course it’s not going to know exactly how much sleep you’ve gained because you haven’t got electrodes attached to your head. The only way you can tell exactly how much of six different levels of sleep you’ve got and the four different types of REM sleep and so on is by the electrodes attached to your head. This is just a kind of gyroscope that’s attached to your wrist. Of course it doesn’t know.
Per: But I mean most people won’t know that and I mean they will trust the app, what it’s telling them, because this is a new thing. It’s a great new device. It’s being marketed that way. It doesn’t have a big disclaimer when you open a box that – don’t trust the data. It tells you that this will measure sleep patterns. It will measure the number of steps you’re taking – and that’s it.
James: You had both on your wrist for a while, the Jawbone UP and the Fitbit Flex.
Per: Yes, I did.
James: So there you got to see how each of them has different formulas you could say for judging what kind of movement is a step.
Per: Yes. When I walked more than 10,000 or 12,000 steps per day, usually the Jawbone UP was almost 1500, 2000 steps less than the other one. So I mean that’s how you can tell that they’re not really exact and usually you probably have to calibrate these to your own walking style, your own gait, which is really interesting as well. I mean you can’t take a device and be sure that it will fit with your body and the way that you move around and if you’re – and as we’ve both noticed I think is that if you’re riding in a car or riding a bicycle and stuff like that, it does register something and sometimes not as much as other times. So many different aspects of this that can affect the data that you’re seeing.
James: Shopping trolleys Per.
Per: Shopping trolleys, oh that’s interesting.
James: I realized that when I do shopping which sometimes can take an hour and a half, I just get almost a flat line on my graph of how many steps I’ve taken even though I’ve been walking for an hour and a half.
Per: It doesn’t register.
James: And that’s because my arms are holing the trolley.
Per: So you will have to start walking with only one arm pushing the trolley.
James: So you put your Jawbone UP in your pocket which is why mine was in my pocket now because we went shopping this morning and I put it in my pocket while we were shopping. So again, you have to learn an interaction in order to fix the limitations of this particular device. I mean OK, if we’re talking about the – what is it? Withing scale, the Wi-Fi scale that can measure your weights and it transfers up to the app it’s on. That’s a little bit different thing because with the scale, I expect it to be 100 percent accurate when it comes to weighing me. Although as we know, if you weigh yourself in the evening or morning and so on, you get different weights because of different liquids and different food in you and so on and waste in you.
Per: You’re even actually – well how do you say it? Less tall in the evening than you are in the morning.
James: That’s right. Your spine compresses and it can be a couple of centimetres.
James: Or a half an inch. But yeah, so even there, there’s a certain pattern you got to follow because – to get the accuracy. Then there’s some other guessing aspects to it that he tries to do but the weird thing is a pretty definite thing because you’re still in the platform and it tells you how much …
Per: So if we connect this to a UX perspective, then I think it’s really interesting how you communicate to the user will set the expectations of that experience and if that experience is not aligned with what you’re telling them, then they’re not going to like it.
James: But if you told someone, “Ah, this is all a bit of fun. It’s not really accurate,” would they sell any? Would people be interested in changing their behaviour? Doesn’t it have to lie a little bit given the limitation, the intrinsic limitation?
Per: Excellent point. Could it perhaps be saying something in the lines of that this is accurate to the point of X and we can’t really promise anything but it gives you something to work with. I’m not sure what I’m saying here but …
James: No, I know what you mean but there is going to be a lot of people – there are going to be a lot of people that – like my wife that think, “Oh god, if you can’t do it properly, I’m not interested.”
Per: Yeah, so that’s interesting. So people would buy it. Well, they use it. So does that really mean that people are not ready? Is the device not ready for the mass market yet? Is it just ready for the geeks like us?
James: I would say so. I think generally a lot of this quantify self stuff demands you to be quite – well, highly engaged. You’ve really got to be driven to want to keep it on you, to keep syncing or checking the app or learning these little tweaks to make it good. Most people aren’t going to bother doing that.
James: OK. Maybe we go beyond geeks here. We’re going to get into the fitness geeks as well.
Per: Yeah, exactly. Like my wife currently who is running a lot and she has been using a Fitbit One which is not the arm band but the one that you attach to your clothes. She has been using that for over a year now. She has been using it like everyday and she’s really fond of it and it has changed her behaviour a lot because I mean – and mine sort of. I mean I had a Fitbit One and didn’t have anything for half a year or something but we started taking walks in the evening to get up to 10,000 steps as per recommendation of what someone our age probably would need to walk everyday to keep healthy. That’s really interesting how that behaviour changes and we can bring people together as well, not only in the virtual world but in the physical world.
We’re actually starting to take walks together and which is an interesting effect. Whether or not the accuracy of the device is an issue here, I’m not sure, because I have – I think I have the same discussion with her that it’s not that accurate but it’s a trend and that’s sort of fine with her.
James: I think that’s the key. Just when it comes to these bands, being aware of the days when you’ve not moved so much is quite useful. It’s a reminder to say, “Oh, you actually do need to move more than this.” It can make a couple of hundred calorie difference in your burn rate by walking a few thousand steps less. I noticed that during the summer. When you’re in holiday and you sat around, you’re drinking beers and relaxing, I’m not walking about. You understand why people go gain weight during the summer, during the holidays. Have you tried the FuelBand, Nike FuelBand?
Per: No, I have not.
James: This is for people that run. This is another wristband that you put on and the FuelBand in my impression – and I’ve got no real idea about this – is that there’s more normal people who have the FuelBand than the UP and the Fitbit.
Per: Oh, interesting.
James: It’s pushed by Nike with trainers and everything. I’ve got a couple of running friends in England that have the FuelBand.
Per: I’m guessing it’s also time to market and I’m guessing in the fitness world the FuelBand is a lot more used. The FuelBand though does not have the sleep monitoring, I think. It only has steps.
James: Yeah, steps. What’s that with the little satellite thing, the little – there has got to be a name, the little thing that you put on your trainers.
Per: Oh, that you put in your shoe. I actually have shoes that one of those fit in.
James: It’s called Jeremy or something. No, not Jeremy. It has got like a man’s name.
Per: I don’t know.
James: I’m sure it has but that’s another little thing. Is that something you have in addition to the band or you have just that and an app?
Per: Just that and an app I think.
James: Right, OK. That measures steps as well.
Per: That was a Nike Plus thing that they – that’s the first launch they did together with Apple I think, one of the first devices that could actually talk with your phone and give you information about how far you were running.
James: Right, yeah. One of the first ones on the market. But this whole – back to the question about whether I still – I think generally it’s just geek stuff. To go mainstream, with almost all of these things we know that to go mainstream, involves a level – I think a level of simplification that isn’t there yet or a level of desire that isn’t really there yet.
Per: Right, and something that they are trying to do is be able – you’re making people able to personalize these armbands more and more and have your own colour. They’re trying to design them in a way to make them more appealing as well. So that’s one big aspect of these arm bands is that they have to be designed really well for people to even want to wear them and that’s one reason that my wife actually doesn’t have an armband. She doesn’t want to wear one though all the time. She has the one that she has in her clothes even if that means that she sometimes forgets to put it on.
James: The thing there is you could use it sometimes with these telephones and have apps on their telephones.
Per: Oh, yeah.
James: But I get the impression they’re really – even less accurate. I’ve got that impression.
Per: Yeah, I can’t really say.
James: Also you don’t wear it around – it’s not with you maybe every single hour of the day, so you can see things.
Per: And having the phone on your arm when you’re sleeping isn’t really that comfortable and believe me, because I’ve tried because there are apps for that. Oh, actually when you attach it to your chest.
James: You mean you strap an iPhone.
Per: You strap an iPhone to your chest. I have tried this but not – like two times.
James: Like Iron man. The generator thing in the middle of your chest.
Per: And that was the first one time I tried what you have in the Jawbone UP which I don’t have in the Fitbit Flex where it actually wakes you up when you’re in light sleep.
So that’s one of, I think, the main features that I am sort of envious of you that you have is that it wakes you up. It can tell when you’re moving around a lot so it wakes you up before you’ve set your alarm for it, before the time that you set the alarm for it because if you wake up now, you will feel better than if you wake up later or maybe in deep sleep.
James: Exactly, that’s the thing. It is a Smart Alarm and you’re right. This is my killer feature with the UP and I love this. I’ve changed using this every single day now as my alarm. You give it an alarm window of 20 minutes or half an hour and you tell it this is the latest time I want to get up. Say 20 past 7:00 and if you get an alarm window of 20 minutes, the band will – it will of course be monitoring your sleep. It’s monitoring your movements and if it notices you’ve come up from deep sleep into light sleep or rather if it notices you in deep sleep when it’s your alarm time. It won’t wake you. It will wait as long as it can to let you come out of deep sleep naturally and start moving around a bit. Then a few more minutes and it will vibrate unless it reaches the end of it.
It’s right. What happens is that, that you wake up more naturally. You wake up at a point where you’re actually ready to wake up and you feel much less tired than that car crash of an alarm when suddenly something starts wailing at you at a certain time. You have move around then to go to snooze and so on. It’s an excellent feature. I’m hoping they develop it a bit more to make it a bit more – a little bit more flexible.
Per: And I’m hoping that the Fitbit Flex will develop it because I mean that is a software feature that they have the data so they could implement it afterwards.
Per: It’s what I’m thinking.
James: Yeah, it’s software mainly but at the same time, I’ve noticed that you can only see what alarms are set by looking in the app.
James: An app will only show you the alarms when the band is connected and because the UP isn’t wireless, you have to plug it in. So to check your alarm for the morning, is actually quite complicated especially – it’s happened several times – I get into bed, put my band to sleep into night mode. Then realize, “Oh god, have I actually set the alarm for the morning?”
So I have to get out of bed, go to my phone because I don’t charge my phone in my bedroom and plug the band into the app, open the app, check the alarm, see that it sets and undo all that. Go back to bed. It takes minutes whereas if there was some kind of display, it could just tell me so many hours the next alarm.
Per: Right. That’s true. Yeah, I agree and I’ve been comparing the Jawbone UP because I’ve had both with the Fitbit Flex and what has been surprising for me is how enormously different these two arm bands are based on – well, they’re supposed to be doing the same thing really, measuring steps and like monitoring your sleep.
They’re designed very differently. Just studying these two devices, it’s interesting from a UX perspective looking at how they actually implement it and how you charge it, how you sync it which is wireless for the Fitbit Flex if you have certain phone times like the 4S and up, iPhone 4S and certain Android phones as well.
James: Does it use Wi-Fi or does it use Bluetooth?
Per: It uses a special type of Bluetooth. I’m not sure if it’s called Bluetooth 4.0 or low energy Bluetooth but one of those and not all phones have it.
James: It might be the same thing. I’m not quite sure.
Per: It could be.
James: Yeah, OK. That’s interesting but I like the fact that the Jawbone UP needs to be charged every 10 days and it’s pretty much true. It’s more than a week anyway so I change it every Monday morning.
Per: I can easily say that the UP has better battery life than the Flex and the Flex does not always last a week which means that I can’t have like a set day in the week that I can recharge it because I have to monitor it and there’s another big issue with the Fitbit Flex as well actually. It does not have a battery indicator which is …
James: At all?
Per: … insane. Yes. There is an API and there is a third party app for – that I’m using that actually emails me when it’s getting low in battery but I’m so surprised they haven’t implemented it on the device.
James: I mean that’s the kind of thing we’re talking about, this extra step, these little extra things you got to learn and tweak and do to make this work which implies that it’s clearly not ready for mainstream.
Per: Right, which makes me think also because I mean the display that my wife has on the Fitbit One, it’s a large display. You can just look down and see how many steps you walked. It has a clock which none of our devices have and stuff like that and I’m not sure if it shows the alarm. Maybe it does. Maybe it doesn’t. But you can see so much more without having to sync it, without having to go into the app, which I think is a real benefit as well for the most people who are just getting started with this device and who are more accustomed to the old types of pedometers and stuff.
James: I mean I wonder if the whole quantify self thing is kind of doomed to be like low adoption and inaccurate, given that we know that most people don’t bother configuring things. Is it ready out of the box? And just with quantified self, it’s incredibly personal. You’re measuring you and so if you are prepared to customize, and most people aren’t, then how can you make a product that is a one size fits all?
Per: Exactly. I think that’s a really good point and I mean just one example is that both of them comes at actually – you’re supposed to walk 10,000 steps everyday.
Per: And there are a lot of people who don’t do that and aren’t able to. So what happens is that you get all these sad faces and red alerts and stuff that you haven’t and you get that for two weeks and I mean you’re ready to give up and the thing about UX and your experience in behavioural psychology is that you need to get quick wins fast. You need to see the benefits of using it really fast. So it should be set like at 5000 and then my recommendation is usually set it at 5000 and when you manage to do 5000 steps everyday for a week, then raise it to 6000.
James: But if you’re a jogger, wouldn’t you be really kind of frustrated and disappointed with that, that you get this thing, new thing and even the first week, it’s kind of like oh my god, you’re utterly fantastic. You’ve done 30,000 steps. I mean you’re just going to go, “Come on. Of course I am. I’m running.”
Per: Yeah, yeah.
James: Again, one size fits all. It’s a very different use case.
Per: You need the quick setup guide.
James: Yeah, me and you and not runners. So we don’t knock up that kind of number of steps in the same way because we’re just walking.
James: Yeah. So we need a quick setup in the beginning. Yeah, that maybe it is.
Per: It would help at least, I think.
James: Yeah. I mean we’ve focused an awful lot on just these bands in the show because that’s probably because we both got them and we’ve been talking a lot about this during the summer and you’ve written a blog post in Swedish about this. But I don’t think the problems are limited to this type …
Per: No, it’s all the same things. How do you get started? How do you talk to it? I mean the Jawbone UP has a physical button. The Fitbit Flex, I have to tap it, different stuff like that. How do you get it to talk to the device, to the app?
James: The interaction itself.
Per: How does the app talk to you? Is it telling you stuff that aren’t true and how do you react to that? Like the example I gave with waking up seven times even though you haven’t and there are so many aspects in UX to this – since it’s a physical device in which I love about it and you have to think about – well, from the point that you wake up in the morning and how you interact with it during the day and how many days before you charge it and stuff like that and all of those things combined is what creates your experience.
I mean the main reason for me, using the Fitbit Flex right now is because I’m competing with my wife who has also a Fitbit device. But I mean I can’t say that there’s a clear winner between the both of them even though they’re very different in design and functionality. They both have benefits and well, disadvantages to them. But there’s so much more to do in that area actually I think.
James: I didn’t realize until we talked about it a little bit ago that you have to shake the Flex to tell it what to do because there’s no button. I had no idea …
Per: Well actually, you have to tap it and you like tap it twice and you see how far you went. Oh, there’s an indicator for how far you’ve reached, how close you are to your goal and you have to tap it like four times quickly in a row when you’re telling it that you’re going to sleep and usually that fails for me and I have to do it like three different times.
James: Have you seen – there was a sketch on an American – one American talk show kind of late night – late evening talk show ones where they did Google Glass and he was tacking the mickey – go back glass back! And he was shaking it flicking his head flicking his head and it looks like you’ve got some kind of crazy tick because you’re going to do this head motion thing to make it go back.
Per: And sometimes I have an alarm going off when I’m like in the store or something or standing by the cashier and I have to start tapping violently on my wrist and they can’t really understand why. At one point I actually – I was shaking a juice carton and I realized that my band was set to sleep because it thought I was tapping it.
So I mean that type of interface has lots of disadvantages to it. I mean you have to think about people actually move their arm in real life even though they’re telling you that you should put it on the arm that’s not your strongest. I mean that doesn’t always like solve all the problems that you can encounter during the normal day.
James: Fascinating, but it’s – there’s a lot of stuff here and a lot of stuff to do that you said, the interaction and about a two-way interaction with a physical device and communication feedback. Not just feedback in the from of graphs but feedback from a small visual acknowledgements or sensual acknowledgements.
Yeah, it’s a fascinating area when it comes to these bands, but even with some of the other quantify self things and how you – why do it, what you can do from it and the incentive side of things is crucially important. I’m thinking of Memoto there and taking the photos all the time and trying to build up some excuse as to why the hell you would want to take a picture every 30 seconds of your life. I can say that that’s definitely not going to go main stream. Same thing with Google Glass. I just can’t see why or maybe I’m just being old there, Per. Are we being old again?
Per: I’m not sure. I was sort of thinking the same thing. Are we being too old? This spring I was – at a talk with – there was a Quantified Self Stockholm meetup and Kevin Kelly came.
James: Oh, yeah.
Per: He’s the founder of all this quantified self groups and also the founder of Wired, a co-founder of Wired Magazine. But he was talking about how important it is to keep measuring even though you don’t know why you’re measuring.
James: He’s right there.
Per: Because sometimes you just find stuff because you’re measuring.
Per: Yeah, and I really love that, what he was saying there because that’s really an important point. If we stop measuring, if we don’t see the point of it, then we’re not going to discover anything new. But if we start collecting data, as much data as we can and start seeing trends, then all of a sudden new stuff is going to appear that we can draw conclusions from and probably change the world basically in the end.
James: Now he’s absolutely right with that. You can never go back and start collecting data again. You don’t do it. That’s true of everything, whatever we’re talking about, analytics for our website or temperature values from your house or your wristband that’s measuring you.
Per: And that’s something we haven’t talked about today is the data that we’re actually collecting can be used by our respective apps and the companies that they’re behind, so you can actually get – I mean you’re inputting your age, your weight, your height and everything. So you can get on the whole population. You can start seeing trends on how much our people are walking during the day in different age groups and what is the norm and what is the mean and what should be the recommendations. We’re seeing that people are walking less over time and you can start seeing that over the next 10, 12 years if people are using these types of apps.
James: Yeah. Why don’t we just all get the chips fitted?
Per: I mean it’s inevitable, isn’t it?
James: To be honest, I’m starting to think probably. It’s going to be so much – I mean you’ve already had the night clubs. A few high end night clubs have the little chips inserted, injected into your arm.
Per: Oh, yeah.
James: It is a way of kind of having VIP pass and non-transferable. So I think there is going to be a growing group of people who are quite willing to have a little thing injected somewhere. Now people have got tattoos and all the rest of it, and piercing. So I can’t say there would be too much of a problem with a chip, provided they’re reassured about the integrity side of things. You’ve got control over it and it’s not some kind of like dog tagging system where you are getting hooked up to a government database somewhere to monitor how much you’re sleeping.
Per: I think the conclusion here is that I mean these devices that we’re talking about, the sensors and the self-quantification, I mean it’s ripe for the picking for us geeks and it’s fine for us early adopters but it’s not really there yet for the mass market. But perhaps that’s what we’re for, that we have to use these devices so that they can like calibrate them and make them better over time so that more people can use them.
James: And learn a huge amount. This is an excellent opportunity for us to analyze what we’re doing, analyze and to look at – how does this physical object that we carry with us all the time, how does it work? What’s making this work, user-interaction-wise or UX-wise? What don’t work? I mean give us a little chance to experiment. That’s what us early adopters are for. We are for testing up.
Per: We are guinea pigs.
James: Yeah, we’re guinea pigs and we like complaining about it a bit and so on. But it’s fun and I mean that’s the most important thing to remember of the quantified self stuff. It’s actually fun.
Per: Exactly. Yeah. Good point. It’s getting really, really hot in this car.
James: And me too. I shut the windows so I’m up to 30 degrees now in here and I need to stop. But before we go …
James: A little reminder, now that our Swedish listeners have come back and come back to work after the summer break. We’re going to be at Conversion Jam 3 on the 10th of September like we were last year.
Per: Really, really fun.
James: It was really good fun. It’s a really intensive day of speakers here in Stockholm, Sweden. Really well-organized little conference and …
Per: Lots of international speakers.
James: Yeah, including one of our favourites, Craig Sullivan.
James: Also Brian Massey. He did that last year too. Sorry, André Mores was there last year. So no, it’s normally a really good day and for you listeners out there, we have a discount code if you want to come along or you are in Stockholm or in Sweden and want to come along.
Per: And just for the sake of meeting us.
James: Yeah, that works too. The code is simply “UXPODCAST” if I can remember correctly.
Per: Yes, it is.
James: Yeah, UX Podcast and you get …
Per: When I saw it, it said “UX Podcast” in capital letters. I don’t think that matters.
James: If you don’t get the 200 kroner discount with it in lower case, try it in capitals..
Per: Oh, yeah. I’m really looking forward. Yeah, we will be recording our shows on location there as well, which would be excellent fun.
Per: One great way to get access to the speakers.
James: It’s, as always, great fun. So thank you very much for listening today.
Per: Yes, and we will talk to you again in two weeks.
James: What do you say?
Per: I say remember to keep moving.
James: I say see you on the other side.
Per: Ah, that’s it.
Hide the transcript
Inspired by a question Bruno Figueiredo posted to Facebook, James and Per try to answer the question – How do you decide what resolution to design for? We talk about screen resolutions, viewports, typography, whitespace, languages, statistics. To finish off, we even try to provide an answer to the question…(Listening time 44 minutes)
— UX Podcast (@uxpodcast) July 29, 2013
- Bruno’s question on Facebook
- Life beyond 960
- Screens are getting bigger, but no the browser viewport
- The length of CSS (units of measurement)
- Realtime face-tracking responsive typography demo
- Logical breakpoints for your responsive design (Languages & line lengths)
- The Art of Explanation by Lee LeFever
- Australian weather and the seasons
Per: Hello and welcome to episode 52 of the UX Podcast. You’re listening to me Per Axbom.
James: And me James Royal-Lawson.
Per: And we’re set – what date is it?
Per: Eighteenth of July, Thursday. I’m recording this a week ahead because you’re going to Spain.
James: I am.
James: On Monday and well, I’ve bottled it. We recorded one episode when you were in America but to be honest, I just got excited about the fact we could use our new microphones.
Per: Right, new microphones, condenser microphones hooked up to Blue Icicle. So you will have to let us know on Twitter if this sounds better than usual. I really hope so.
James: I just couldn’t bear the fact that you would be recording using these new microphones and I would be using Skype on my tablet from a little apartment somewhere in the south of Spain.
Per: You want to sound as good as I do.
James: Yeah, hold on. You’re making me very confused now. So we’ve been here for an hour and you said, “And now we’re fully dressed.”
Per: Don’t go there. You’re always confusing the listener. I was going to explain one of the fun things about doing a podcast is you don’t really have to take a shower but people don’t really care what you look like or smell like because you only had to listen to our voices, our beautiful voices. When we decided to do this – we just decided yesterday. You made a joke that when it’s coming over here early, that you wouldn’t be fully dressed probably.
James: I said that you were scared of Jimbo flesh.
Per: Yes. Thankfully you were dressed when I came over here. You hadn’t had breakfast yet.
James: No, I hadn’t.
Per: Oh, well.
James: Sorry, I’m fully of food now. I’m dressed.
James: Everyone is dressed. To calm you all down, we’re all dressed.
Per: But it is really hot and it’s getting hotter in here.
James: Yeah. People who have been listening to this show for a long time will know that the – well Beantin HQ, the studio where we record this, during the summer months, it does get warm in here but we’re only up to 24 degrees.
Per: And we have entertainment because just outside our window there are bouncing kids. Well, two right now but …
James: It’s just two but not the same two as it was a second ago, the trampoline in the garden, which we can see from the studio window.
Per: Which also is a good test of the soundproofness of your studio and the quality of our microphones.
James: Yeah, and the loudness of my kids.
James: It’s not going to go well, is it? So what are we talking about today?
Per: Well, I think it was last Friday. Bruno Figueiredo, you will know him from UX Lx, the curator of the UX Lx Conference.
James: And we talked to him in one of our …
Per: Yes, we did on the first conference show. He posted on Facebook about screen sizes and he was looking at statistics and seeing that with the 1440 pixels is becoming more and more common, 1440 and wider and the general question was, “Should we start moving away from the 960 pixel width standard of our designs and go higher than that?”
My first thought was well, hold on. We have all these tablets and mobile and we’re thinking mobile first. Should we start going wider? But then I realized it was like – it was a good question partly because mobile first is valid in countries where mobile first is true but also as you pointed out to me James, clients are still designing or wanting websites that look like websites.
James: Yeah, there’s an actual element there that it’s not just about the kind of design utopia. You still got to – a clients relationship and a lot of times, they’re going to want to have a desktop design or something they can give an opinion about and look at and I know that you have to deliver that kind of thing quite a few occasions.
Per: Yeah. And other stuff going through your head is like, “Oh, do we go wider?” Does that mean wider columns for content? I mean must decrease legibility and readability and all that stuff. It would be so hard to read. What would you put in all that space? It’s like some Manhattan architect seeing a new space and you have to build something there. But do you really have to fill every space on screen just because people have bigger screens?
James: You threw a lot of questions out there all in one go. But I mean the 960 grid, there has been the – that has been the kind of foundation of a lot of the design work for a long time.
Per: And people have loved it.
James: Well obviously about 2007 or something, 2006 or something like that.
Per: And it has worked nice because it split it into four columns, six columns, eight columns.
James: Exactly. It’s a beautiful number. It came along when laptops suddenly got bigger. We got bigger screens and desktops and monitors got better and we end up with these 1024 by 768 4:3 aspect ratio screens and 960 became a real good thing. Everybody stayed with it. It was across the board. It was valid but then I think for the – when I did a little research last night, I saw that basically for the last I think five years, you can find articles talking about, “Is it time to move on from 960? Is 960 dead?”
So even before the mobile revolution, people have been questioning the 960. Should we move up? And now …
Per: Is that probably because as a designer you’re aching, aching to design new stuff that fits the screen that you’re on everyday?
James: Or as an agency or something as a team delivering to the client. You want to deliver that little bit of magic, that new thinking to push you ahead of the crowd.
James: But then we got the whole mobile thing comes and we’re all going to mobile first and small things first. So you get people saying, “Well 960 is dead because we shouldn’t be starting with 960.”
Per: Now the interesting thing of course then is can we even have this discussion about what size to design for without knowing what we are designing. That’s kind of funny. So when we talked about this yesterday, we thought, “So how do you actually decide what is the best screen size to design for?” It’s really impossible unless you actually know what product you’re designing, what goals you have.
So I mean the gut feeling is start looking at statistics like Bruno did and seeing that oh my god, people are using all these large screen sizes now. Should we start taking them into account? Then the research you’ve done James is pointing out that people actually have large screens but they’re maybe not even having the browser maximized meaning that they really don’t have the need for actually having that big large real estate screen size that you’re designing for.
James: Well, we talked about, for a while ago now, I think it was autumn last year. Jakob Nielsen, he altered his recommendation. I think it was – how long is that? It was the end of last year, I think it was. His recommendation for what width design for from 1024 wide to 1440. He went up 50 percent in his recommendation based on screen resolution research he had done showing people are using screen resolutions that are huge amount bigger.
Per: That’s about the time when we started wondering if Jakob Nielsen was getting high.
James: Oh, we just presumed he was not writing the articles anymore. He was getting a student or something to write them because there was a whole row of articles there which were just off the wall. They really weren’t quality and good like they used to be. One day we have to interview him.
Per: Yes, we do.
James: But anyway, so what I did, I updated my – I’ve been doing viewport research for a few years now and I’ve created methods that can help you log viewports in Google Analytics. They log it themselves on Google Analytics but you can access the data in a good way.
Per: So just to clarify now so that everybody is on the same plate. Viewport size is the size of the browser that’s – the actual screen size. Do you have the definition? That what you’re seeing is the viewport. I mean you can make your browser smaller and then the viewport is what you see.
James: But your laptop still has the same screen size.
Per: Yeah, exactly.
James: But you’re using less of it for your webpage.
Per: Right, yeah.
James: So this is the viewport. It’s the real estate you’re actually using to put your webpage on.
Per: Right, and you also have to subtract the address bar and whatever …
James: Yeah, this bevel around, stuff like this. So everything has a viewport whether it’s mobile phone or it’s a smart TV or a laptop. You still – there’s a bit of the screen you’re using to show a webpage on.
Per: So you could basically say that the webpage is never the size of the screen.
James: That’s impossible.
Per: Unless you’re maximized.
James: Now, it’s not – I think even then you find that it’s like a one pixel bit here or there.
Per: Yeah, OK.
James: It’s difficult to watch it getting maximized even on tablets because you even got pixel density ratios.
Per: Right. Oh, that’s another story.
James: We don’t need to get into it just now really but I mean it’s complicated. My research, I’ve seen – I’ve been monitoring, I’ve been tracking the viewport size on Beantin.se for three years I think now or more and I’ve seen the resolutions of visitors go up. I mean there’s just a lot more huge screens anywhere. These Retina Displays are two and a half thousand pixels and so on.
But what I’ve seen over the last two years or so is that the width, the average width hasn’t really increased. It’s still hanging around the kind of – well, 1280 or just under 1280 wide.
James: And it has been like that 2010, 2011, 2012. It has not got bigger. I’m excluding mobile from that because this is – when we’re talking about these giant screen sizes, I think it’s relevant to talk about just the desktops.
Per: So can we make any assumptions about why that is? Is that like people don’t like to maximize their browser even if they have bigger screens or …
James: I think you would have to do some proper research onsite with real users and what’s their behaviour because you can’t see that from your statistics.
James: But I know from ones I’m looking around is that the people who do have the giant screens, I’ve seen – what I see there is that there were maybe two side by side that you and I have a giant 27-inch screen. You’ve got two Safaris or you’ve got programmers for example. This is where I see it quite often that they would have test version of – webpage will be open on one side and then the other side would be the coding screen.
Per: Tools and Photoshop.
James: Or where they’re writing, when they’re doing something. So that’s huge split screens. We used to have – I mean I still do. I have two monitors here in the office.
Per: Right, yeah, and I like to do that as well.
James: So these giant screens, they just allow you to have two screens.
Per: Yeah, to see more at the same time.
James: Yeah, because you’re viewing angle – you can’t look at these big screens all at the same time. You’ve got to turn your head.
James: So if you designed a website that was two and a half thousand pixels wide, a person looking on the content of the left of the screen would have to move their head to see the content on the right.
James: That’s a design that’s huge by itself. Interaction design, how do you solve that? So you can argue there’s no point trying to fill up that space because it’s – most people are not going to stretch your site that wide.
Per: You also have to think about the incentive from manufacturers to actually build these fantastically large screens. It’s not so that you can view your webpage or your corporate webpage in a fantastic, beautiful big size in which case you would like to have to stand 20 feet away from the monitor to read it correctly. But it is actually too that you can get more work done faster and you can multitask and see stuff at the same time. So you can put windows side by side. That’s the main reason for these monitors …
James: These desktop screen sizes, yeah. Then smart TVs have a massive resolution as well.
James: People don’t use the browser on them because it’s awful.
Per: I tried.
James: It’s horrible. Interestingly there, if you do run the browser on them, they don’t use the full resolution anyway.
Per: Oh, yeah. You were saying that. It’s interesting as well. So I mean you can’t even …
James: They adjust it so that they’ve had to zoom in without getting too deep into the ratios and things. It’s not about the pixels that you kind of – you’re being sold. It’s about the way that your operating system or your laptop or device is presenting those pixels to you or that real estate to you.
Per: And should we really even be talking about pixels anymore? I thought we were beyond all that. We should be talking about the content, the content living in any device and you guided me into this article that you were reading yesterday and life beyond 960 pixels, designing for large screens in which …
James: That’s from last year, wasn’t it?
Per: Yeah, I think it is and Ian Yates, he makes the case for the responsive. Then you don’t always talk about responsive in this way because you always think about responsive web design being as something that you do to accommodate mobile devices. But responsive goes both ways. It goes smaller. It goes wider.
Per: So responsive is all about accommodating the large screens and he makes a lot of examples or provides a lot of examples of what could you do with this new real estate that you have.
James: Because we have to fill it.
Per: Because we have to fill it and it does make a point in the end that you don’t have to fill it. It means you don’t have to fill – the obligation to fill every space on the screen but it does provide some examples of what you could do, like have more right hand columns, move the footer to the right hand side and again, that’s why I don’t like responsive because you get disoriented when you’re actually moving from one device to another on the same website and you can’t find this stuff where you expect to find it.
James: Was it his article that had the Windows 8 screenshots?
Per: Yes, yes. It was.
James: I love that screenshot because it shows Windows 8 like on a tablet and a reasonably regular smallish device and it has got like 12 bricks or something or 16 bricks, something laid across. It looks – and they’re all on the Microsoft standard, nice colours, the primary colour kind of thing and orange or so.
It looks really quite stylish and nice and then there’s a screenshot of someone with a 27-inch monitor or whatever it is and they filled up the whole thing with tiles and that must be like 150, 200 tiles and it looks like your grandma has made a patchwork quilt from all the leftover material you had.
Per: It’s impossible to find anything.
James: It’s just mad.
Per: That’s something that we know and we know it from psychology studies. We know it from a research and from just experience working with the web for so long.
James: Less is more.
Per: Less is more. The more choices you give the user, the harder of a time they will have finding something useful and making a decision about where to go next in solving their task.
James: That’s the risk with more real estate. You fill it for the sake of filling it.
Per: So we have this case of larger screens but we want to have less information. We’re moving towards less information in most designs I’m working with and I made the case tons of times about – I mean the right hand column, just ditch it.
Per: It’s not helping your user. It’s just distracting your user.
James: And then we can expand that and say that while if you’re going to have a super-sized monitor, the right right hand column that you’ve added to fill the space even further beyond the right column. It’s definitely not going to be used, so just get rid of both of them.
But another aspect I think one of the articles brought up that we read last night, we have to put the links to these articles that we’ve read because we’re not referencing them properly but we have read them so it’s good if listeners read them as well. I was talking about the viewing distance we have for these monitors and comfortability, readability of fonts and so on, on the screens.
Like when you’ve got the very large monitors, you’re expected – well, your font is going to be tiny. You can’t read them, so you need those to be bigger. There was a demo I saw with someone who had done – I think using the webcam or something that he did a demo so that when you came further and closer away from the screen, it automatically adjusted the size of the fonts. It’s like an eye tracking kind of demo thing.
James: Because readability is all down to how clear letters are from a distance, viewing distance, comfortable viewing distance from the screen. You know that you hold a phone a certain distance away from you. You hold a tablet a certain distance away. You generally sit a certain distance away from your desktop machine and that’s the same and true for even giant monitors.
So we’ve got an added aspect there that we need to know more about where you are in relation to the device, decide what font size or typography we use to make it comfortable for you to read it. Then the pixels don’t really matter in that sense.
James: So yes, EMs, again getting into measurement units. That is much more sensible to use rather than pixels because the web is a reading medium.
James: We have to make sure everything is readable so you can take actions and you can achieve what you need to achieve. So typography is maybe a more sensible starting point than physical pixels on the device.
Per: I think it is, yeah. Typography, content. I mean well, the content is your starting point. What is the content that you put in there? And the goals, yeah.
James: Yeah, what you want to do and the content from that.
Per: So if you were putting out content, think about what could support that content, not what else could you put on the screen, but what supports the content that you’re showing currently just now.
Per: And so few websites do actually, which is a pain. But also what I found – I mean at the same time as I’m saying that you shouldn’t fill every pixel on the screen just for the fun of it, I actually stumbled – and this article reminded me of it.
I stumbled upon it when I was first designing for the iPad, realized that yeah, I want to have all these buttons over here and I want to have this and then there was space left and it was designing an app for the iPad. You need to fill the space. You can’t have empty space in an app and that’s really interesting because then you have to really think about it and that’s when you have these background images coming along, that you would have something that actually fills the space but doesn’t distract you from the content, but actually just makes something that’s in the background, something to rest your eyes on. Not even notice basically but it doesn’t make this page seem strange when you’re looking at it.
There is a case – I mean going back to Bruno’s original question is that so many people actually have larger screens and sometimes you actually do have this wide space on the sides and people are wondering and I know that some of the clients I have been working with are asking – this looks strange. This looks weird. Why is there so much space over here? Should we do something with it?
Something like background images and stuff like that. I like more than putting more banners or links or whatever, sponsored ads on the sides.
James: Yeah. I get some complaints about my blog because it’s a very narrow single column at the moment and on the giant screens, if you do happen to run it full width, then you’ve got like 1000 pixels either side of white space. It looks very strange.
Per: You were mentioning also – now I’m blabbering here but all the things at the same time but you were mentioning – when you were talking about typography and stuff there as well, you were mentioning before to me as well this thing about language and some languages have longer words than others, so column width actually has to be wider for certain types of languages as well.
James: Yeah, that was really interesting. I’m speaking Swedish of course but we know the Swedish where you do have a habit of …
Per: You have composite words.
James: You have composite words. It does get strung together to be very, very long at times. I mean generally speaking, you would say – well, one of the things that you could find with the research and what I recommend is that you never go lower than 45 characters on a row, on a line. So when you’re doing responsive, one of the checks you need to do there is see how few letters you’ve got left on a line when you’ve shrunk it to its minimum viewport because less than 45, it starts being ridiculous. You end up with one word on each line quite often.
Then you shouldn’t go beyond like what – between 70, 75, somewhere around there and it’s the maximum length for each row. After that, readability drops because nine, ten words on a row is roughly good readability. Generally speaking for us English speaking people, that would be 70 odd characters.
James: But that’s not true for all languages. German is one of the examples that German has longer words, largely speaking or broadly speaking, which means you might prefer to have a little bit more than that – or towards 80 plus, 85 maybe is more sensible for German. So you get on average maybe the nine, ten words still.
But there then we’re saying maybe it’s more sensible to design for each language you tend to use rather than each resolution, the user specs the user might be using.
Per: Yeah, I like that, adding a completely new complicated dimension to your web design. Yeah, using it to another language.
James: But from a user point of view, that’s much more relevant. I mean if I’m looking at a site in German that was designed in English, with the 960 grid and the right hand column is 50 characters wide or something, when I look at it in German, or – the web editors, the web managers are not looking after the site when they’re trying to put all their headlines in. You suddenly find that the German part of the organization can’t put the title in for that particular function because it’s 25 characters instead of the 14 in English.
Per: I’ve been there, done that. Working with Vattenfall, the large energy company because …
James: Oh, you’re naming names.
Per: I know because I stopped working with them. It’s so long ago. But they have operations in Finland, in Poland and in Germany. Also Finnish and Polish also have extremely long words.
James: Oh, Finnish has some monstrous words, yeah.
Per: I mean Finnish, it was impossible. I mean the lengths, you had big tabs.
James: Finnish is impossible.
Per: No, but the design was impossible. Let’s not go there!
Per: The tabs on the front page. They were just saying like home, business, private. They couldn’t fit. They couldn’t fit!
James: Yeah, the sale content first but language – well, you go to content first then language automatically becomes part of the content first because you’re going to – it would help you produce all your languages beforehand. We know this doesn’t happen. This is the thing about reality – theory in reality. All the great web minds are saying mobile first or content first or both.
That’s what we’re meant to do and we know usability-wise, we’re not meant to confuse our users. We got to keep it simple, focus on tasks, focus on conversion, all that kind of optimization and so on. Yet when it comes to building this stuff, it’s just …
Per: We do it in the wrong way all the time.
James: We do it in the wrong way all the time or we’re forced to do it in the wrong way all the time. I think this is – we talked about this with Brad in the last show about how – I mean it’s one thing standing up and being counted and saying I believe in future-friendly – in doing stuff right and following my heart, my web brain and knowing what I should be doing.
James: But then your client comes along and goes, “Yeah. Well, I want a new desktop site.” You design me of a new product page or landing page or whatever it is.
Per: Right. Sometimes you’re just caught up in building more pages on the website that’s already there.
James: Yes, they don’t want to replace their content management system and they haven’t budgeted or they aren’t ready for doing a major redesign to maybe go responsive.
James: They just come to you and they’ve asked you to do a new – do a wireframe for a new product page.
James: You forced them maybe into a certain width…
Per: Maybe they’re saying that well, you told me it was future-friendly six years ago. But apparently it wasn’t because then all these mobiles came and what we did before wasn’t future-friendly. So how can I be sure it’s future-friendly now if you just do it responsive? We can’t because maybe that changes in two years. We have some new technology that makes it easier for us to push out content in different devices. Someone will think of something new.
So of course you’re never safe and that’s why – I mean going back to two episodes ago when we had that webpage. “This is a webpage.”
James: Oh, yeah.
Per: That’s where we should be starting with our content, putting it out there, just in plain text. Then start adding the pictures, start adjusting the fonts, the width. Test it. Then start adding the navigation. So do it in the right way instead of so many times going to the ad agency or whatever agency you’re going to and they will design something before having any content at all and you’re trying to squeeze it in.
James: I joked last night when we were chatting about what topic to record today, about web design being impossible.
Per: It is impossible.
James: It is.
Per: The more you know, the more – I mean …
James: The more enlightened you become.
James: The more dark and evil the whole thing becomes. I mean OK, we’re 25 minutes into a podcast show now and we’re trying to help people here and we just said it’s impossible. So you might as well switch off now and go out in the garden.
It’s very, very difficult to mix all of this together and even the greatest web minds out there still don’t really have the perfect answers to everything. It’s a changing landscape as well as a complicated one. We’ve got all these devices. We’ve got all these languages.
Per: And you can’t trust the statistics.
James: You can’t – I think more there is – yeah, at times you can’t trust the statistics. You can’t also maybe trust your own analysis or analytics.
James: Because most people actually don’t know what they’re reading. The people’s knowledge about what does that mean.
Per: You’re looking at quantitative data and unique …
James: Lots of visits.
Per: Yeah, you need qualitative data to actually go out there and like you were saying, see people using your site, using your services and that’s where you draw your conclusions from.
James: So we’ve got language. We’ve got typography. We’ve got behavioural science. We’ve got – the list is endless. We got clients. We’ve got agencies.
Per: Yeah, and the experts online as well, saying something.
James: Also you maybe work for an agency and that agency itself has sales goals. You’ve got a sales team who sold in a project to a client. The whole complexity of how we built up the industry and what we’re expected to deliver. It makes it impossible to do the perfect website.
Per: So I’m the CEO of Kellogg’s James. I don’t know why I pulled that out and I come to you and I’m asking we want to build a website. How do you decide what resolution to build for?
James: Oh, I like that. If I turn around slightly, can I look at my whiteboard?
James: Well, first of all, you’ve got to make sure they’ve got their goals set right.
James: Because you come to me Mr. Kelloggs and so you want that. I want to ask you and check that you know what you want from it. Why are you doing it? What’s the point behind your website? How does it fit into the rest of your business, your business goals? What are you trying to achieve? Or even just that one page you want me to design. What’s that going to achieve?
And after that, we can then start getting into maybe what’s going to be on it, the content. Shall I go through – I actually wrote a six-step answer to how you could go about this.
Per: Go for it.
James: Yeah, first of all were goals as I said Mr. Kelloggs, and then research, research and measure. Really the measure. You know that I push this so much that you’ve got to measure the viewport being used and see what is happening because I’ve done this on several sites now and I know it varies from site to site quite a lot and I know that resolution is irrelevant.
Per: OK, James, but I’m Mr. Kelloggs now and we haven’t measured this at all over the years and we need that …
James: And you’re not going to do it before then.
James: In that sense, I’m going to recommend that you try and put that in place for the future so we can do a better job next time. But then we’re just going to have to basically guess based on resolution and yeah, then we know as well though that from other research, that – well, depending on what resolution was popular, that we can properly guess that – the laptop, the standard laptop size is still the most common, 1378 by 768.
Almost every single laptop screen is still that even though it’s pixels and we said about don’t use pixels anymore. That’s the size it is. Retina Macs and things, that’s different but most normal laptops and in business environments, a lot of people are still using those resolutions.
Per: This is where I want to go out and verify the goals with the actual users and actually like go – well, call some people up that are actually using the service or know something about Kelloggs based on the goals that you got from the CEO. Actually make sure that those match some of the goals that users have because if there’s no match, if there’s no win-win situation to be held here …
Per: … then you may have to go back and actually you need to find the goals.
James: So you’ve got to do the research there and even as you can’t do analysis and measure the viewport, then yes, you got to – exactly what you said. Reaffirm that these goals are going to work and the same time, you bring out some empirical research that says oh look, our users are mainly doing this or look, consuming the website or the content in this way.
Per: And then also set how you’re going to measure the goals.
James: Yeah. And then I want you to take – to do the content. Actually produce the content.
James: That is going to support the goals.
Per: But I haven’t hired a copywriter yet.
James: Then we have to try and use the existing content, if it’s an existing website and this also may be difficult in that you might – I think some people are going to struggle maybe to do content for a page, all content, including micro content for micro copy for various bits. We got any kind of design whatsoever. If I tell you to write a webpage, and you’ve got no idea of menus, you’ve got no idea of whatever site you are, what they’re all called, if it’s going to be – you’ve got nothing. You’re building from zero.
Per: I think I love trying to do that. I can honestly say I haven’t done it. I think it’s a really good way to do it.
Per: And I’m going to try it at some point in the future.
James: It would be interesting because I think it’s going to be a real challenge – with a blank piece of paper doing content first.
Per: Then you’re really focusing on the goal. What do you want the user to understand or achieve or do after doing this?
James: You’re right. It has got to have the goal and even some – yeah, and even SEO comes into it though. That maybe is a way of helping with content first.
James: Making people think about the – the kind of good headlines then how it’s going to be appearing in search engines. What’s the readability level? What’s good? Making sure content is easy to read not just from a number of words on the row but also the language level.
James: Not making it too technical or too high level language, keep your readability age down because we know people find that easier and allow people wonderful reading.
Per: I’m actually reading The Art of Explanation now by – I forget his name but I will post it on the show notes but the guy – do you remember these videos about RSS in plain English?
Per: All those, the Common Craft …
James: Yeah, Common Craft.
Per: Yeah. Sold the guy who made those. He also made the video for Dropbox.
Per: And there’s a lot about explanation, how you have to really dumb down the language and make people – start off at least explaining stuff, getting the context of stuff so that people know where are they. What do you want them to do and why? Understanding why before you understand what and I really like that.
James: You try to solve something. Yeah. Then once you’ve actually worked out your goals and you’ve got all your content produced, then I think you should design for the smallest screen.
James: Produce something for the smallest screen size. Do the whole mobile first thing.
Per: From my perspective, the smallest screen will always be the iPhone.
James: Yeah. Well, I mean depending on where you were in the world and what markets because there are still groups of – there are countries and groups of people that are using feature phones.
Per: Yeah, future-friendly.
James: You’ve already done your research.
Per: James, it has to be future-friendly. These people are going to buy iPhones.
James: Yeah. They will. But if you’ve done your research and you understand your users then it doesn’t matter because you choose the right device to do that smallest one first.
James: But OK, now you’ve done a design and it’s – we’re probably talking about three-inch and 320 pixels wide now because it’s the smallest group first.
Per: Yeah, bump that up to 1440.
James: I don’t think you should. The step there I reckon, prototype, because if you then prototype that smallest one, you got something to play with and I’d – well, you test it in the smallest device but also you could start then to – seeing how this copes in the other devices or other sizes that your research has shown that are relevant for your products or site.
So rather than kind of saying, “OK, we do 960,” you might not need 960. You actually might find that other sizes are more relevant to look at and then you can start stretching and playing and see what breaks and tweak and adjust to make it work on the larger sizes.
James: Or smaller ones. It might be that the one you realize afterwards that you want to go a little bit smaller to cope with an edge case.
Per: Yeah, that’s what I’m thinking because I mean designed for the smaller screen. Well, we’re actually saying design for the smallest …
James: Relevant screen.
Per: That most users use.
James: The smallest, relevant screen.
Per: Exactly, the smallest relevant screen because I mean if 60 percent of the users have 1290 whatever and, I don’t know, five percent have less than that. Then that’s probably …
James: I’m not going to start …
Per: You’re not going to start with the mobile.
James: You would struggle to justify to your client starting with the smallest one I think, because if you’re a live site, live product just selling stuff or doing stuff now on the site, then you’ve got to care for that big chunk and so maybe you start with that one first and then move down. So maybe there’s a star next to my “smallest screen first” there…
Per: Now I’m getting really complicated and you’re realizing that you have some power users and the power users are the ones that are buying and they’re going online and have a ready shopping cart and then perhaps a few of them are actually going and pushing the buy button in the mobile resolution. Then you would realize that those are the guys that you want to design for. So it’s all down to which ones are making the money as well. If that’s your goal, if you have money making goals.
James: Which ones are relevant. The smallest relevant screen size first.
Per: So many parameters there that you have to take into account.
James: Told you it was impossible.
Per: Exactly, totally. Well, it’s complicated but there are like – I will make a template for it.
James: Yeah. So you can grow – with the whole mobile first thing and start with the smaller one first and it is easier to grow because you’ve already done the job of focusing your content and making sure you’ve got just the bare minimum you need to fulfil your goals because we know as soon as you start – you said as soon as you start more real estate, there’s an instant desire or you need to fill it and there’s often the battle to get stuff left alone. I mean not fill stuff. You’ve got an AD or some designer that’s filling up the page and then maybe aren’t the ones who has worked with the content. They aren’t the ones who are going to program it and so on. We’ve got these islands of – these silos of competence that are involved in these kinds of projects. You are going to fight to get your white space or to not add extra features just because there’s room for extra features.
James: And making sure you make – whatever you do add, you measure to make sure you understand the success of it.
Per: Or the failure of it.
James: Or the failure of it.
Per: Yeah, because sometimes you have to add something because the client is just on you all the time.
Per: And you add it and you have to measure them and see how does that take away from what you’re trying to accomplish with the webpage.
James: I got a question the other day about – oh, there was a suggestion of a mobile’s version of a page my client is asked to be produced for his agency. It doesn’t include like five features from the desktop site.
James: I haven’t answered yet. I haven’t had time. But just that. Well, if the agency decided not to include these five features, is that because they’re really not that relevant?
Per: Yeah, we’ve encountered that before.
James: Or is it that they’re trying to save time and money? There’s no budget to produce all these features in the mobile version but the client wants the mobile version. You end up getting it – you’ve lifted a stone and so now you go, OK, what’s the business needs? What are the business limitations? Is it a budget thing here or is it a lack of research, a lack of understanding or readiness in the organization for certain decisions?
James: Suddenly, a simple web design question becomes a business question…
Per: Yeah, that’s what I’m thinking. We started out with the screen size and we’re now into business goals. You have to dive into every part, every crevice of the organization and actually realize what they are all about. What can they accomplish? How much money do they have? What competencies do they have? How much time and money do they have to actually work with this over time?
After you’ve done the prototype, I mean you’re launching and your point number five on the whiteboard there is you actually grow as dictated by research. OK. So do we have any money left to do research and to actually do the redesign? Maybe not. How sure are we that we’re right when we launch?
James: Probably a good thing to finish off on now is just say that in digital and on web, any – if there’s a quick and easy answer to one of your questions, it probably means you’re doing it wrong or doing it in a quick and dirty way, and you’re not doing it the best way.
James: And in some ways, that’s fine because that’s how it is. If I came to you and say, yes, design for 960, then I’m just giving you a quick and dirty answer and I’m not giving you the full picture because we just explained – just spent 40 minutes explaining a lot about the full picture and it’s very, very complicated.
Per: But are people going to have time to understand the full picture?
James: But then that’s the business decision itself. As long as you’re aware of the fact that these quick, simple answers mean that you’re ignoring a lot of elements and a lot of factors and as long as you understand that by taking these quick, simple decisions, then you probably are doing that. You’re not doing the right thing. Then fair enough. Just keep it in mind for the future that you probably need to allocate some time and money to doing it a bit better later on.
Per: I can’t stop thinking about the quick, simple decision people are making nowadays is responsive web design.
James: You’re right.
Per: And I’ve met so many people who – well, owners of websites that are thinking now, “Oh my god, what did I do?”
James: Yeah. I emplore you, if you’re doing responsive, make sure that you monitor your page load times as part of your web analytics and segment it by mobile and desktop and so on.
Per: Yeah, just make sure you visit your website now and again in your mobile and see what’s going on there.
Per: Wow, thank you for listening to all this rant about screen size. But it has been fun actually, I think. You’re going off to Spain.
James: I am. But you’re not back at work yet, are you?
Per: No, no. I’m – well, I’m semi-back first of August. I will be working on and off from the summerhouse I think, and so living the good life of the freelancer.
James: But for our listeners, we’re always open.
Per: Of course we are. Yeah, Twitter, email, yes. I’m in there all the time as always.
James: Yeah. And as usual, if you like the show, then give us some feedback. Get in touch with us or if you’ve got any questions or any points you want to argue about or correct us on, then yeah, get in touch. We would love to hear from you all.
Per: Check back in two weeks. Continue having a great summer everyone and remember to keep moving.
James: And winter for the people in the other side of the world.
James: Winter for the people in Australia.
Per: Oh my god! I always forget that this is a podcast and internet is global.
James: We’re a big round thing.
James: It’s not the same everywhere.
Per: But it’s summer.
James: Not down there.
Per: Yeah, but it’s summer months.
James: No. It’s winter months down there. Their seasons are the same.
Per: Do they actually say winter?
James: Yeah, absolutely! Because it’s winter. It’s colder.
Per: I didn’t know that. I’ve been to South Africa although it’s not …
James: Oh, South Africa is not that far south really.
James: Not when you look at Australia.
Per: Well, the seasons don’t change as much.
James: They don’t need the geography lesson.
Per: I didn’t realize this.
James: This is not a geography podcast.
Per: No, but this is interesting, because that means when you’re …
James: Can I get a cup of tea?
Per: We will save it. We will save it but I didn’t know that. It was fun and so I hope some other people didn’t know that as well. Now remember to keep moving.
James: And see you on the other side.
After returning from Intranätverk, an intranet conference recently held in Sweden, James shares some reflections. We also talk about user centered design for the digital workplace and how intranets are the “poorer brother” of the world of web. Has the world of intranets finally started to catch up? Read More
Two giggly old men begin this episode of UX Podcast by corpsing. Once we had composed ourselves, the topic was misunderstanding the term UX. What is UX? Can it be definied? Can you be a “UX-er”? Is the phrase “UX” needed or are we just unnecessarily compliating things?(Listening time: 36 minutes)
Many people and families share login details and profiles for various digital services. Why are so many of these services failing from a UX perspective in such common user scenarios? Netflix, Spotify, Facebook, even the iPad itself all suffer from these problems.
In Episode 35 James and Per dive into the topic, discuss some examples and try to come up with some answers.(Listening time: 32 minutes)
- Netflix (on Wikipedia)
- Spotify to introduce family subscriptions
- Personal accounts are personal
- Netflixs shows off user profiles
- Share your password and go to jail
- Magine (steaming TV service)
- Digital life at 40 (James’s nostalgic blog post)
- Min första dator (Per’s nostalgic blog post, in Swedish)
This time James and Per discuss usability rules and recommendations. Jakob Nielsen earlier this year updated his web design recommendation, saying that you should now design for around 1440 pixels wide. With this as a starting point we cover browser viewports, research, recommendations, responsive web design and mobile web sites. Phew, all that and a little more in 29 minutes!
(Listening time 29 minutes)
- Computer screens are getting bigger
- Screens are getting bigger, but not the browser viewport
- The Right column is a black hole for content (Swedish)
- WordPress plugin: Measuring viewport size
- How Moving the Call-to-Action below the Fold Generated a 304% Lift in Conversions
- Whitney Hess’s “one column” site
In this month’s episode of UX Podcast James Royal-Lawson and Per Axbom talk about the darling of 2011 – responsive web design – what is it? what are the benefits? What are the pitfalls? Is responsive web design the ultimate solution to web design? or is it, in many ways, a step backwards?(Listening time: 21 minutes)
This month’s episode of UXPodcast with James Royal-Lawson and Per Axbom discusses the quality of websites and digital activities –
Why do so many end up being below par?
Why do some end up being great?
What can we do raise the quality of the web stuff we make and run?
This month’s episode of UXPodcast with James Royal-Lawson and Per Axbom talks about when offline meets online – stories and examples highlighting how attempts at connecting the two often fail, as well as suggestions as to how to improve your chances of succeeding.
In part three it get’s so hot in the studio James and Per start getting delirious – and talk about “digital dating” (building relationships through marketing) and the mobile device as the hub to marketing, taking offline/online beyond campaigns.
This month’s episode of UXPodcast with James Royal-Lawson and Per Axbom talks about when offline meets online – stories and examples highlighting how attempts at connecting the two often fail, as well as suggestions as to how to improve your chances of succeeding.
In part two the temperature is rising in the studio but Per and James still manage to share some ideas about what companies should be doing – Creating a digital experience that fits into people’s lives as well as adding value. Making sure that the journey from offline to online is easy for the people coming into contact with your campaigns.
This month’s episode of UXPodcast with James Royal-Lawson and Per Axbom talks about when offline meets online – stories and examples highlighting how attempts at connecting the two often fail as well as suggestions as to how to improve your chances of succeeding.
In part one James and Per talk you through a number of recent campaigns where the offline element fails in its attempt to get you online.