Apps: Web vs Native – swinging towards Web?
Last week I linked to a piece about Financial Times turning its iOS app off, to concentrate on the Web instead.
Technology Review wrote of their experience “The future of media on mobile devices isn’t with applications but with the Web.” in Why Publishers Don’t Like Apps.”Like almost all publishers, I was badly disappointed. What went wrong? Everything … We sold 353 subscriptions through the iPad. We wasted $124,000 on outsourced software development. We fought amongst ourselves, and people left the company. There was untold expense of spirit. I hated every moment of our experiment with apps, because it tried to impose something closed, old, and printlike on something open, new, and digital.”
Also How NSFW Corp Dodged The Newsstand Bullet And Lucked Into HTML5″ “when Not Safe For Work Corporation finally launched a few hours ago, there was no Newsstand edition, and no Kindle store edition. Instead, it’s HTML5 all the way.”
Mobilism mobile browser panel with Jeremy Keith and reps of RIM, Google, Nokia and Opera on
- Lea Verou on Text masking — The standards way. I have a lot of sympathy with the view expressed by Matt Wilcox – SVG is much harder to write than a line of CSS (and I feel a bit ewww at mixing presentational SVG with my HTML). But at least this works everywhere, which is Lea’s point.
- Jake Archibald’s funny and finely-researched article Application Cache is a Douchebag is vital for those thinking of offlinerifying a site, the and Fixing Application Cache Community Group want to, er, fix the AppCache spec.
- Opera’s representative on the CSS Working Group, Florian Rivoal, has a proposal to fix the vendor prefixing system:
When a browser vendor implements a new css feature, it should support it, from day 1, both prefixed and unprefixed, the two being aliased. If a style sheet contains both prefixed and unprefixed, the last one wins, according to the cascade.
Authors should write their style sheets using the unprefixed property, and only add a prefixed version of the property (below the unprefixed one) if they discover a bug or inconsistency that they need to work around in a particular browser.
If a large amount of content accumulates using the a particular vendor prefix to work around an issue with the early implementation in that browser, the vendor could decide to freeze the behavior of the prefixed property while continuing to improve the unprefixed one.
- A proposal from Edward O’Connor of Apple for <img srcset> for responsive bitmapped content images
- How browser engines work – a video presentation by Anthony Ricaud
- Research shows adhering to WCAG doesn’t solve blind users’ problems
- Dutch pass Net Neutrality Law (where’s mine, Mr Cameron?)
- A short, fun video about The EU cookie law
- This picture shows the size of a sphere that would contain all of Earth’s water in comparison to the size of the Earth
- Marriage in the bible – keep it sacred!
- Bad otter taxidermy