Great presentation with great learnings out of controlled experiments
- UX principle: “Don’t make me think”
- Controlled experiments are not the panacea for everything -> see paper
- If you’re going to experiment, try more variants, especially if they’re easy to implement
Great examples of AB testing for user screens.
The related paper
by Rupert Breheny
- All web pages should render legibly on mobile devices
- We write content once, and can view it on any device
- We never show a horizontal scrollbar, regardless of device or screen-size
Make sure to check out all the links in this presentation
WebGoat is a deliberately insecure J2EE web application maintained by OWASP designed to teach web application security lessons.
Give it a go web devs!
Great post that shows the basic steps to Simple Responsive Design and some great tools around it.
Don’t forget to charge a Premium for your services! ;-)
Responsive Web Development as a Standard, Step-by-Step
Nice infographic showing 29 ways why HTML5 will change websites for the better
The stats they are using are not the latest ones (year 2008/2009) but just the numbers and the releationship between the numbers are impressive
Great presentation from Martin Fowler about “Developing Software for Multiple Mobile Devices”
Covers concepts like
- Downsides of native, cross-platform and hybrid apps
- Product VS Channel
- Uncanny valley
- Native Veneer
Make sure to do a “View Source”
An interesting tool mobile web development on the iPhone, Android, iPod Touch, and other forward-thinking devices is jQTouch. http://www.jqtouch.com/
Great experience report from Microsoft about AB testing
When Bing had a bug in an experiment, which resulted in very poor results being shown to users, two key organizational metrics improved significantly: distinct queries per user went up over 10%, and revenue per user went up over 30%! …. Degrading algorithmic results shown on a search engine result page gives users an obviously worse search experience but causes users to click more on ads, whose relative relevance increases, which increases short-term revenue … [This shows] it’s critical to understand that long-term goals do not always align with short-term metrics.
Generating numbers is easy; generating numbers you should trust is hard!
Great article by Dave Ward
I would boil it down to “WebAPI” has 1 major advantage over “MVC APIs”
- Content negotiation
- Removal of XML support
- Tweaking of JSON Format
"Flexibility" is a clear advantage when you are building an API.
But should you use ASP.NET MVC to build an API anyway??
At the Summit they estimated that MVC would only be applicable for ~10% of all new web development projects
MVC usage is ~30%
Interesting read about WebForms and MVC.
By Shaun Walker from the DNN blog (DotNetNuke)
Have a look yourself
DNS Prefetching & TCP Preconnect…and a “Predictor” to anticipate the user behavior…
If we guess right, the DNS and TCP handshake may complete before we even hit enter!
Interesting to see the growth of mobile.
Full article: Bandwidth explosion: As Internet use soars, can bottlenecks be averted?