Let me start off with it is great that SkyFire is launching in the UK, more browser competition is a good thing and no where more so than on the mobile platform.  This isn’t meant to be an in depth review or critique rather a brain dump following a a conversation I had yesterday
with SkyFire and in part a response to RobK’s article over on Mobile Industry Review.

I have concerns about SkyFire.  I raised this on Twitter yesterday briefly so I will try to articulate them here in the hope that it will i) spark more discussion and ii) hopefully set me straight.

Architecture
Up front I am not an architecture expert but even I can see that essentially what SkyFire are doing is providing a proxied web cache server-side so that response times client-side are nice and snappy.  That’s a good thing.  The flip side is that everything you do in the browser is done through SkyFire’s caching servers.

Do your banking on the mobile and it’s cached.  Browse for some interesting PRON and that’ll get cached to.  Now this may not sound like a big problem, afterall ISP’s often cache frequently accessed content to improve response times and reduce upstream bandwidth so read on.

Privacy and Your Information
Remember when Google first launched Chrome and people got all in a tiz over the EULA and how effectively it gave Google a seriously strong hold over well everything one did online?

Google backed down on that one and  I only hope that the provisions in question are not backin the newly revamped v.1 release.

Well SkyFire has some pretty interesting terms in their Privacy statement also.  Aside from collecting a bundle of personal information on signup they also grab, store and dive around in those logs of everything you do.  Whilst the privacy policy clearly states that anything that leaves SkyFire or it’s partners to be used for advertising generation is anonymised I’m not such just how comfortable I am about having every single part of my browsing habit correlated with my personal information anonymised or not.

The other side of the privacy issue here that bothers me right now is that whilst SkyFire have placed caching boxes UK side, there is no mention of where within SkyFire my personal information is stored or U are a  hell of a lot more robust than those in the US – where SkyFire corporate is based.

Don’t think this is a potential problem?  Just go have a dig around the web about some of the provisions in US legislature regarding federal access to your information.

There is a really good reason why in 2007 the French Government banned it’s  employees from using RIM Blackberry devices in official capacity when all email goes via RIM’s US based servers.

User Experience
There are many components to a great user experience (UX).  SkyFire’s browser looks great, the caching technology provides responsive rendering (assuming the UK servers are up) and overall it’s a nice little browser to use so plus one there.

Another aspect to UX of a web browser though is usability.  Not usability of the software itself (that’s fine) but of the web sites being rendered themselves.

Back in the day web designers built web pages to suit different browsers, screen resolutions and so on.  Then IE kind of won out for a while but along came CSS and content separation from layout.  All of a sudden it was possible to fairly easily create fluid, dynamic layouts easily repurposed for different delivery channels.

Today savvy web development accepts that the mobile platform is rapidly gaining acceptance and is in all likelihood going to rule the roost  in the not too distant future.  To that end they take account not only of the reduced screen real estate but also of the subtly differing uses of popular websites by mobile users.  For example viewing Flickr.com and m.flickr.com give slightly different view points on the same content.

Apple gave a nice nod towards this being a sensible approach when they threw the iPhone to the baying masses.  The Safari browser will render sites in their full glory allowing you to scroll around and zoom in and out effortlessly.  BUT applications builts around the iPhone are more list orientated to take account of the form factor, fat fingers instead of precise mouse pointers, and also the need for simpler easily navigable menuesque structures.

So far few have complained of this dual approach being a bad one.

SkyFire are currently claiming one of it’s killer UX features is it’s ability to render full size web sites in their original glory.  No, no, no.  This is not a killer feature.  The demo I was given showed the YouTube homepage squished down to fit a QVGA screen.  Now true enough it looked like the original and sure the video ran really well (good skills there) BUT you couldn’t read the options, comments or pretty well anything without an electron microscope.   Showing a facsimile of a site does not automatically create a great experience.  That’s why YouTube have i) a mobile site and ii) an api allowing third parties to create differing and more suitable experiences based on the form factor being used.

Now I know I am banging on about this a fair bit, but it is a massive bug bear of mine.  You see I currently only have a netbook (all the ‘real’ kit is in storage still).  Much as I love this little thing the screen resolution of 1024×600 can let me down.   Or more to the point web developers that insist on constricting layouts to suit their own design aesthetics leaves me cold when they just don’t work.  Sites that require me to squish the display or scroll the entire desktop just to click a confirm button are an instant and never revisited FAIL.
Why would I want to do this on my mobile as well?

But in SkyFire’s defense I do openly admit and applaud their commitment to bringing full sized sites to the mobile – afterall until web designers get their act together and allow for this form factor shift we need easy to use browsers that can give us some help.

Open vs Closed Source
Does anyone know?  I asked if the core of SkyFire’s browser was proprietory to which I was given a yes, but as to any parts being open sourced a blank stare was the response.  This is not the place to enter into a debate on the pro’s and con’s of open vs closed source (IMHO there is a place and need for both, often within the same product) but I suspect that as the majority of those likely to install SkyFire over a default browser on their phone may have a vague understanding of the issues it seems only sensible for SkyFire’s people to be able to give a coherent answer.

Revenue Model
SkyFire have not yet publically announced their revenue model, although they will admit to already being in receipt of some advertising cash – I believe from Google adwords.  If I’m reading the Privacy policy right the whole product is designed to create a managed channel through which they can fairly accurately create profiles for users and throw advertising at them.

Whilst I personally think this type of advertising model is beyond broken I will admit right now it delivers.  What bothers me though is that for SkyFire to succeed it needs lots of users, signed up, browsing and creating complete profiles.

Without overtly stating that by signing up SkyFire will be collecting and onselling the right to advertise at you it all just seems a little well, underhand.  Afterall who else out there actually reads those T&C’s that have an easily clickable “Agree” button?

I co
uld, and indeed would love to be wrong here.  Given SkyFire’s complete control over the channel they are potentially putting themselves in a very good position BUT IMHO they really really need to be upfront  about what they are actually doing, why and how.

So for now I’m happy to see SkyFire on the scene, as a Beta product it’s well polished and offers up a far better experience than other S60 browsers for sure but as web developers get more savvy and the advertising models that underpin so much of today’s online business get deconstructed, disrupted and destroyed I just hope that SkyFire have a really good plan.