Archive for the ‘Standards’ Category

Safari update makes itself obsolete on Windows

Wednesday, March 4th, 2009

Last week, Apple announced the Safari 4 beta with a whole host of updates and enhancements. Whilst all of this is great for Mac users, it renders the browser completely obsolete for Windows users. Let me explain:

Lets go through the list of new features.

  • Top SitesOpera first added this feature 3 years ago, Google Chrome has it, all Apple did was make it fancy and unusable
  • Cover Flow – I like the live page preview (other browsers do have that) but cover flow, to me, is something that windows users will never understand
  • Full history search – Safari is the last browser to get this function
  • Tabs on top – Google spent a lot of effort getting this right, Apple haven’t put the same level of thought into it. If anything, it makes Apple look like they’re copying Google, badly.
  • Nitro engine – Makes pages run fast. Cool
  • Native look and feel – looks good in Vista, awful in XP. Considering Vista usage is < 10%, that’s not a good thing
  • Developer tools – once again, Apple is playing catch-up

So, what does this all mean exactly? Well, Safari is becoming more and more like Chrome. In fact, all Google has to do is update their Webkit rendering engine and they will be the same browser. In this manner, Safari for Windows has just shot itself in the foot by removing any differentiating features between itself and its nearest competitior.

I fully expect Safari 5 to make itself even more like Google Chrome (whatever that may look like in 2 years time).

Don’t just complain about CSS3, do something!

Tuesday, March 3rd, 2009

A colleague of mine and I were discussing the current state of the internet, CSS3 and IE being behind the rest of the browsers in terms of standards adoption. He argued that IE was “rubbish because it doesn’t support CSS3 selectors/borders etc”. My reply to this was, “well, do something about it”.

IE doesn’t support any non-candidate recommendation CSS3 modules so they can’t be accused of not supporting standards. If you want this to change, we have to get CSS3 finished (at least one module!). To do that, the W3C needs help.

The CSS Working Group is made up of invited experts and representatives of the major web companies (Microsoft, Mozilla, Apple, Google, Opera and Adobe). It’s unlikely that you’ll get to go to one of their meetings any time soon, but everything that they talk about is discussed openly on their mailing list. I’ve been subscribing to this list for around 6 months and haven’t contributed a lot, but anyone can. They currently want people to comment on working drafts and come up with suggestions on how things should work and any problems you have day to day that you think can be solved with CSS.

So seriously, if you want to help, don’t just complain, do something.

Why iPhone Web Apps are Still Worthwhile

Friday, February 20th, 2009

I’ve been playing with iPhone development for a month now and I’ve understood the concepts and am ready to make my first app, but I haven’t.

See, my first exposure to the iPhone world was through a web app my company made for its partner group. It was a simple ruby on rails web app that used my patched version of iUI to drive the experience. It was such a big hit that I’m currently finishing up a third demo branch of this for a client, hoping to convince them that even large organisations can get on the mobile bandwagon. So, you may ask, why isn’t it being done as a native app? Well, there’s a lot of good reasons, but what it really boils down to is that if you’re writing a native app for the iPhone, you’re only writing it for the iPhone.

At Mobile World Congress this week we’ve seen new Android devices, new Windows Mobile devices and more of the Palm Pre, devices that have one important thing in common with the iPhone, a web connection and a browser.

The best thing about all of them having a browser is that 3 of the 4 run a version of Webkit with Apple’s transforms and animations built in (Windows Mobile users can download Opera ;-) ) So, really, when you’re creating a web app for an iPhone, you’re creating a web app for all other mobile devices with a half-decent browser (S60 included).

How much work would it be to port an Objective-C (iPhone)-based app to Java (S60 and Android) and then to .NET (Windows Mobile), only to have to create a web-based version for the Palm Pre! What all these iPhone developers need to understand is that if they want the full potential of the market they’d better start learning HTML5 databases and Javascript. Web apps are certainly still worthwhile.

All that said, App stores can’t push web sites to your phone, which is the main source of advertising and how the iPhone apps have become so successful. Maybe Apple should allow you to browse web apps too?

What Would the Best Mobile Web Toolkit Do?

Tuesday, November 18th, 2008

As I mentioned in a previous post, I’m planning a mobile web toolkit to replace iUI, but what would you want in it that’s not in iUI already? Should is work across all browsers, even Pocket IE and that godawful Blackberry Web Browser? Should it use progressive enhancement all over the shop or just create a new version for each browser? Should it focus on touch screens or is clicking important too?

Put your thoughts in the comments!