Showing posts with label Browser. Show all posts
Showing posts with label Browser. Show all posts

September 29, 2008

The broken Web

I have several computers, almost all of the time I'm using one (or several) or three: an HP laptop that with a 1024x768 resolution, the EEE PC 701 with a 800x480 resolution, and finally my BlackBerry 8100 and its way smaller screen. I use them to do everything I use computers for, including surfing the web. The experience is far from perfect, and here are some reasons why:

The web is about content, not displays


Please stop that really old mantra of "nobody uses 1024x768 anymore". I've been listening to that for a while, even if the biggest resolution I have on this three devices is exactly that one. Also, the argument isn't new: I remember at least the "nobody uses 640x480" and the "nobody uses 600x800" arguments, and I'm pretty sure that the thing didn't start there, but in other arguments like "nobody sees only 80 columns anymore". The biggest mistake here isn't to think that nobody uses 1024 while I still do. Nor trying to predict the smallest resolution out there. The mistake here is that the web is about content, not displays. Regardless of what you might think or want, a website is meant to be read by whoever crosses with it, using whatever device he's using. Your website must be visible, readable and usable by every device, with every resolution. It's not hard, and it doesn't mean you should ditch planning your website layout and make it into your CSS files. On the contrary, it means that you should treat content as content and put it in the document layer, presentation as presentation and put it in the presentation layer. But it also means that your presentation can't be made in a "if users are reading this in a 1024 screen", or "if users are reading this in a mobile device", but instead, "if users are reading a paragraph", "if users are reading a caption"...

One Web


Like I said in the previous item, your website should be platform-agnostic. But that doesn't only mean that I should read your website well in every resolution, it means that I should be able to read your website with every browser, in every device. One web, several ways of reaching it. So, remember this next time you're thinking about making a mobile version of your website: if you're planning on do it, you already did it wrong. See, your website should be readable everywhere. That means that if your website is well made, I can read it well in my mobile device without the need of going to a mobile version of it. On the other hand, if you're making me go to another website -- a mobile version -- you're not only stopping me of seeing the website I want to see, giving me a trimmed-down version of the real thing, you're actually making me see another webiste, with all the implications that might have. Remember, if your website doesn't look good in a mobile device in the first place, you already did something wrong...

The Web is The Web


The Web is The Web: nothing more. It's made of standards, composed by a set of documents written in a certain language. You have HTML, XHTML, CSS, Javascript, several formats for images and other objects... and that's it. The Web is just that. The web isn't made of "plugins" or "third-party applications". The web is made to be seen by a browser - any browser. So remember: if you have, for instance, flash in your website, the content must be 100% acessible by a browser without a Flash plugin. I'm serious: it's not my fault if I can't see your website in my mobile phone just because it full of flash. You chose to use a plugin that isn't available to every browser, in every platform, so you have to give an alternative for those visiting your website without that plugin. Oh, and spare me that "you don't have flash, get it here" messages, because you're just making me doing a couple of steps and going to another website where they'll tell me "your platform isn't supported". It's not my fault as a web user, and it's not their fault as a plugin provider: it's your fault as a content publisher.

What else?


There are tons of other things in the web that makes it as broken as it nowadays is. But for now, please think about this three. I bet that with those solved, my web experience would get a lot better.

April 03, 2008

Opera Mini 4.1 beta

Opera Mini is already aiming for its next release - 4.1 - and its beta is already out. If you follow this blog you know that I'm an user and fan of Opera Mini, but I'm still using Opera Mini 3, since Opera Mini 4 doesn't have an option of having the "mobile view" sliced in pages, like Opera Mini 3 has, and v4 eats too much memory trying to load an huge page at once, failing to do so and stoping me of using it to browse in my Motorola E1 cellphone.

Now that Opera announced the beta version of Opera Mini 4.1, I just had to try it. It comes with great new features:
  • autocomplete of URLs
  • offline access
  • search for text within a web page
  • download and upload files

The default search engine switched from Yahoo! back to Google (which is great, for me at least). Also, it is way quicker (enhancements were made server-side), and consumes a lot less memory (so, 4.1 fixes my issue with 4, and is going to replace my Opera Mini 3 installation). Yet, Opera Mini 4.1, even in "mobile view" mode, is slower than Opera Mini 3.

Regarding to the "beta" state of this release, like what happened with Opera Mini 4, beta really means beta: just to test out all this things, but nothing more than that, I had to fire up the browser four times because it kept crashing. So, it's still not to use, but I'm surely upgrade as soon as the final version is released.

October 10, 2007

Mobile Firefox


Two years ago I was talking with some Opera folks about browsers and the rising of the mobile browsing market. I told them that, while I was an Opera Mini user, I was really sad with that fact, because I would rather use an Open Source browser. We further discussed about the state of MiniMo: a project that few of you will remember but that stands for "Mini Mozilla", had two developers, and then only one. Of course it never went far. What surprises me is that today I'm reading about Minimo dyeing... and Mozilla creating a new project: Mobile Firefox. YAY!

Now, the not so good news: they're aiming to a minimum requirement of 64Mb of RAM. Now, that's really a lot more than Opera Mini requirements... And more than what my actual mobile phone has :-(


Read the announcement at http://weblogs.mozillazine.org/schrep/archives/2007/10/mozilla_and_mobile.html.