Earlier quoted context omitted.
> I doubt they did any proper UX testing at all Really? The BBC didn't bother doing any UX testing on a redesign of their flagship website? Really?
This reads like you're just point-scoring at this point. If the site worked on the Tube before, and now it doesn't, that's a pretty massive failing.
How we built the new BBC Homepage
81–90 of 96 posts
Re: How we built the new BBC Homepage
#82I do love when companies share this stuff. Thanks. > Rather than using PHP or Java (that was the requisite of the Forge platform), we have chosen a non-blocking framework, NodeJS with the Express framework . This allows us to serve more simultaneous requests, increasing the performance of the application. I don't doubt this is true, but its worth noting you can get good performance out of a "blocking" framework too.…
Re: How we built the new BBC Homepage
#83Earlier quoted context omitted.
And I totally hate that they're wasting taxpayers money on all this crap.
I for one don't mind that they use tax payers money - because for all its many and varied biases* (national & cultural blindspots, party political) - its output is valuable and often of benefit/interest beyond Blighty. * BBCs insistence that it is unbiased is unrealistic imo (but not as outlandish as Fox's 'fair and balanced'). Its more of an ideal rather than something anyone/org can achieve. I admire their attempts…
Re: How we built the new BBC Homepage
#84Earlier quoted context omitted.
Linux / Chrome middle clicking doesn't work. How can they break something so basic?
Also not working on Windows 7 / Chrome.
Edit: Actually, only working fine on the first link. All subsequent links get captured
Re: How we built the new BBC Homepage
#85Earlier quoted context omitted.
Yeah but every few years they seem to reprogram the entire website in "whatever is most fashionable at the moment". I'm not sure that's a good use of the publics money.
You'd rather we kept with outdated layouts like this[0], forever? Part of rebuilding the website is updating the layout and usability of the website. In order to keep the website usable, the people administering it have to have better tools to organise content on it (as we all know, UX isn't just design, you can't just write a new template over a site with bad UX to make it perfect). Developers use whatever is most r…
Re: How we built the new BBC Homepage
#86I do love when companies share this stuff. Thanks. > Rather than using PHP or Java (that was the requisite of the Forge platform), we have chosen a non-blocking framework, NodeJS with the Express framework . This allows us to serve more simultaneous requests, increasing the performance of the application. I don't doubt this is true, but its worth noting you can get good performance out of a "blocking" framework too.…
Re: How we built the new BBC Homepage
#87Re: How we built the new BBC Homepage
#88Earlier quoted context omitted.
You'd rather we kept with outdated layouts like this[0], forever? Part of rebuilding the website is updating the layout and usability of the website. In order to keep the website usable, the people administering it have to have better tools to organise content on it (as we all know, UX isn't just design, you can't just write a new template over a site with bad UX to make it perfect). Developers use whatever is most r…
I'm happy with that "outdated" layout yeah. It's pretty narrow on my screen - but so's the new one. The information is clear and accessible - more so than on the new one, actually. And I'd bet the filesize is smaller and the render time shorter as well.
Re: How we built the new BBC Homepage
#89I do love when companies share this stuff. Thanks. > Rather than using PHP or Java (that was the requisite of the Forge platform), we have chosen a non-blocking framework, NodeJS with the Express framework . This allows us to serve more simultaneous requests, increasing the performance of the application. I don't doubt this is true, but its worth noting you can get good performance out of a "blocking" framework too.…
Re: How we built the new BBC Homepage
#90Hmm. While it's nice to push rendering out to clients for saving your server CPU, that can lead to a suboptimal mobile experience, requiring more CPU and battery power on the mobile device to work on the javascript and render the page. There are other factors, for sure, but you want to be keeping client side javascript down to a minimum. Taking a quick spin through yslow in the mobile browser suggests they've got a n…