10 Web Predictions for 2013
Happy New Year! 2013 has arrived and, while we may not have hover boards or day trips to the moon, technology and the web is evolving faster than ever. My 2012 predictions were a little off but no matter. The spirits are communicating with me. So is the beer and wine…
1. Browser usage patterns will steady
Do you care whether visitors use Chrome, IE, Firefox, Safari or Opera? You shouldn’t. We’ve reached a point where there’s little difference between the top five browsers. They all support the core HTML5 technologies, they’re all fast and they’re all stable. Why switch?
Unfortunately, this hasn’t stopped developers doing silly things such as using webkit vendor prefixes in preference to all others. If you find yourself posting “this site works best with…” messages, get a grip and fix your code. Browser compatibility is better than it’s ever been.
2. Browser choice will become more limited
Unfortunately, choosing your preferred browser is becoming a thing of the past. Vendors are jumping on the iOS bandwagon and dictating what you can install on your device:
- Microsoft grants higher OS privileges to IE on Windows RT and Windows Phone. Other vendors cannot get on the same playing field; competing will be difficult.
- You can guess which browsers are provided with Chrome OS and Firefox OS.
3. IE11 (or 10.1) will be released
Microsoft’s historical 2-year browser release schedule has always been a joke but it’s no longer funny. IE10 was the first version to implement automated browser updates so I hope the company has plans to use it. Let’s also hope the gold release of IE10+ arrives on Windows 7 within a few months; we cannot wait for the world to upgrade to Windows 8…
4. A big Windows 8 update will arrive
Speaking of which, SP1 will bring back many of the business PC-friendly features Microsoft stripped from the OS. I wouldn’t be surprised to see less reliance on the gesture nonsense and a smaller Metro/whatever-its-name screen which looks suspiciously like a Start button.
5. Node.js will become a disruptive technology
This one’s a gamble. Server languages such as Ruby and Python may be popular among developers, but they’re niche technologies compared to PHP, .NET or even Java. The same can be said for Node.js, but it has several advantages in its favor:
- Development tools, sites and resources are rapidly becoming available.
- It’s trendy and backed by some large industry players.
While it will take time for Node.js to become entrenched in business applications, it has a far better chance of worldwide success.
6. 2013 is the year of Responsive Web Design
OK, so I thought RWD would become a mainstream technology in 2012 but I predict several important sites will adopt the techniques in 2013. Moving from fixed to (more) fluid layouts is difficult concept for designers to grasp, but tools are becoming available.
RWD may not be perfect, but it’s a cost-effective way to make your site work on a variety of devices. If you’re not offering the service to clients now, be prepared to lose some business.
7. A responsive image standard will be decided
One of the major RWD stumbling blocks is images. While you can scale an image for any screen size, it would be more efficient to send smaller images to smaller devices. Or — more specifically — use smaller images on devices where bandwidth is limited.
That said, do you really need that 1Mb bandwidth-hogging image? Perhaps it’s time to find a designer who understands the web!
8. Touch screen devices will come of age
Touch screen devices are not as ubiquitous as you’d expect. You may see them everywhere, but that’s because you’re hobnobbing with others in the technology industry. 2013 will be the year your parents replace their creaking Windows 98 PC with a new tablet.
However, I’m not predicting the death of the PC. A real keyboard, mouse and monitors will remain essential for anyone doing real work. But does your boss need a 27-inch iMac to answer three emails per day?
9. The native vs web app debate will continue
One observation stunned me in 2012; companies are blinded by native smartphone apps. Dumb assumptions include:
- Everyone uses their smartphone to do everything
Modern smart phones are great for quick messaging, taking photos and keeping you amused, but that doesn’t mean people use one to write a novel or calculate their annual tax bill. Context is everything.
- It’s easier to develop and release native apps
Writing a native app is no easier than writing an application on Windows, Mac OS or Linux. If anything, it’s more difficult given the limited hardware resources, clunkier development tools and wider range of devices and target operating systems.
- Native apps are easy to monetize
Really? For every flourishing native app, there are hundreds which make little if no money. Consider Rovio: they developed many titles but were close to bankruptcy before the success of Angry Birds.
Web applications may be a better solution for some projects but companies will still want native apps. Perhaps we should all switch to Objective C then take the money and run?
10. Average web page weights will reach 2Mb
I’ve been moaning about page weights for almost three years but no one’s listening (apart from enlightened SitePoint readers, of course!) In fact, my previous predictions consistently underestimate the problem. Perhaps it’ll be 3Mb?
For this reason, I’m starting the Lumbering And Rotund Design awards — or the SitePoint LARDs. Please send your nominations for the most ludicrously bloated pages to me on Twitter @craigbuckler. Let’s see if we can shame a few developers into dieting.
All the best for 2013!
If you enjoyed reading this post, you’ll love Learnable; the place to learn fresh skills and techniques from the masters. Members get instant access to all of SitePoint’s ebooks and interactive online courses, like Build Mobile Apps and Websites.