Will HTML5 replace native apps? It might: here’s how to figure out when.
The debate about using ‘native web‘ applications against ‘native applications‘ has forgotten about one important element in the process – the user:
Mobile web content adaptation techniques – my Ronan (@xbs) at mobiForge:
If you ask yourself, what fitml.com is doing: We have moved from purely Server-side Adaptation to The Hybrid Approach and adding more and more features to combine server/client side detection/adaptation in future.
Charted: Android Fragmentation,
the a new problem of the mobile web:
Optimizing for High Pixel Density Displays (@opticswerve):
Google’s ‘mobile friendly’ initiative, some thoughts about GoMo by .net:
Adventures in Web 3.0, use
overflow:hidden; (maybe you have noticed the problem at our start page (not fixed yet)):
<link rel="apple-touch-icon" .../> supported by Nokia (Meego 1.2):
iOS, Android, Blackberry and now Meego supports this
A new “standard“?
Never seen before:
<META HTTP-EQIV="cleartype" CONTENT="ON"/> causes cleartype to be turned on at Windows Mobile 6.5 and maybe Windows Phone 7:
Cross-browser kerning-pairs & ligatures
An explanation of the CSS animation on Apple’s iPhone 4S web page:
Share your favorite FITML examples:
Last but not least “Responsive web design is not only for mobile/tablet web”: