Posted on Nov 12, 2009

Use Firefox Betas on the Mac without Overriding Other Versions

On Windows, the Firefox installer (quite considerately) won’t override existing non-beta versions of the browser with a beta version (like the recently released Firefox 3.6 betas). Though it doesn’t explicitly say so, Mac OS X users can have a similar behavior, which by the surprised faces I see when  I tell people this, many people don’t know about.

It’s simple:

  1. Grab a Firefox beta download, then mount the disk image
  2. Instead of dragging the Firefox app to your Applications folder, drag it to your desktop temporarily
  3. Highlight the app on your desktop, hit the return key, and give it a new name (like “Firefox 3.6 Beta”)
  4. Drag the newly renamed app to your Applications folder

You can then run these two Firefox versions with little interaction between the two. I say ‘little’ because they will share the same profile (where your bookmarks, extensions and the like are kept), and so cannot be run at the same time. This has the plus side of meaning you won’t have to re-import bookmarks and such, but you will have to sit through a harmless extension compatibility check whenever you start a different version of Firefox than was last run.

Posted on Feb 19, 2009

Better iPhone User Agent Regex

David Walsh recently published a blog post detailing how to detect iPhone and iPod Touch users on your website via the user agent string, and while the concept is fine, I much prefer a slightly different method using regex to do the detection. In PHP:

  1. if(preg_match(‘/Apple.*Mobile.*Safari/’, $_SERVER[‘HTTP_USER_AGENT’])  {  
  2.     header(‘Location: http://yoursite.com/iphone’);  
  3.     exit();  
  4. }

Using this regex, you are not only covered for the iPhone and iPod Touch (in one call, even), but also potentially for any future Apple mobile devices.

And for those interested, the actual user agents for the iPhone and iPod Touch are variations of:

Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420+ (KHTML, like Gecko) Version/3.0 Mobile/1A543a Safari/419.3

Posted on Oct 7, 2008

How to Make a Full-Screen iPhone Web App

There has been a fair amount of talk lately about a feature introduced in iPhone firmware 2.0 and above that allows a developer to make a web application, once saved to a user’s iPhone home screen, run in a full-screen mode without the Safari toolbars. AppleInsider wrote about it, with a fantastic demo available on the website of the WebApp.net framework.

While there has been a lot of talk about the result of this technique, I haven’t seen anywhere that describes exactly how to make your application run full-screen (sans buried deep in the Apple Developer Connection documentation). It’s actually incredibly simple, just add the following code into the <head> of your site:

  1. <meta name="apple-mobile-web-app-capable" content="yes" />

Once you’ve done this, when someone saves your application to their home screen it will subsequently start without the Safari chrome. Make sure that if you do this your application has adequate navigation and plenty of feedback during loading, as users won’t be able to use the Safari back/forward buttons nor see the standard loading bar.

Posted on May 10, 2008

Pre-Launch Access to Schmap.com on the iPhone

Schmap.com, a local city guide and travel information provider, is all set to launch a very sexy looking iPhone interface in public beta on Monday. The Schmap iPhone interface encompasses the company’s City Guides and Local Search services, plus a unique feature that auto generates maps when the iPhone is turned sideways.

The Schmap guys were nice enough to pass on to me a code that will let you access the Schmap iPhone interface before it launches on Monday. To get a sneak-peek, browse to http://schmap.com/iphone on your iPhone and enter the access code 724627.

Posted on Feb 9, 2008

Simple iPhone 1.1.3 Upgrade Instructions (with Unlock)

After the resounding success of my firmware 1.1.2 guide, I have decided to put together a guide to upgrading an iPhone to firmware 1.1.3, both jailbroken and unlocked for use on any network. This guide involves a lot of steps, but it will ensure that you have the best possible result by the safest means. Keep in mind that there is no state you can get your iPhone into if you do something incorrectly that cannot be reversed, so don’t be afraid to try.

This guide is for owners of iPhones that came with firmware 1.1.1 or earlier out of the box. Unfortunately, iPhones that came with firmware 1.1.2 or 1.1.3 out of the box run a newer version of a key software component (called the bootloader) that prevents unlocking using this method. Continue Reading

Posted on Jan 20, 2008

Office 2008: First Thoughts

I have in no way given Office 2008 a thorough working over so do not take this post as a final conclusion, but after installing the new Mac version of Microsoft’s beast and having a little poke around, I have a few first thoughts.

Microsoft Office 2008 is a prime example of Microsoft taking the proven Mac way of doing things and trying to make it better. At this task, they have failed, and what results is a mess of Microsoft thinking on a Mac framework.

The first thing that I noticed is the toolbar, which indeed mimics the standard Leopard toolbar, but is actually Microsoft’s implementation of it and as such the look just isn’t the same. This make Office stand out amongst other Mac applications, and I have absolutely no idea why Microsoft couldn’t just use the standard toolbar. These little user interface inconsistencies are one of the reasons I left the Windows platform, yet Microsoft has again felt the need to make things that little bit different.

The second most annoying thing I have come across are the useless and absurd effects applied across the UI, especially in the Mac equivalent of the ribbon from Office 07. Every click on any element in this area triggers transition effects, and while they might look pretty the first time you see them, it adds a significant amount of time to navigate around and find things in the applications. These effects extend to most of the UI, and even the small view change icons in the lower left-hand corner of the windows glimmer and blink when you point at them. Why?

The design of the Preferences window also bugs me, albeit to a lesser extent. The window pointlessly attempts to mimic the Mac OS System Preferences window, and this really just makes accessing preferences cumbersome and slow – why can the preference windows not look like they do on every other Mac application?

In any event, these UI-level problems aren’t completely deal-breakers, and I am yet to really evaluate the Office 08 applications for their intended purposes. Word is my most used Office application and I will be using the new version to put together my next review, so time will tell if it is good enough to drag me away from Pages.

Posted on Nov 13, 2007

Cautious Android Excitement

Like many, I have been watching the news related to Google, among other’s, announcement of the Android mobile platform and the Open Handset Alliance. Until today’s release of several videos demonstrating the UI and parts of the system itself, there was not a lot of meat to get excited about. Now, I am filled with cautious optimism over Android.

After viewing this video in particular, one can see that at this point in the development cycle, it appears as though Google is looking to pull in the best features of Windows Mobile and the iPhone UI. On first inspection, Android looks most like Windows Mobile, especially the home screen. Once the device is in use, however, a very ‘smooth’ quality reminiscant of the iPhone can be seen. The browser especially is obviously modeled off Apple’s efforts, though there is a lack of finish at this early stage.

The most interesting and exciting part of Android is the level of openness. The iPhone is a great product, but like many Apple releases, it is basically Apple’s way or the highway. Sure, Apple has now announced an SDK for third party applications, but it is an afterthought, rather than Google’s release of an SDK months before devices are in the hands of customers.

Don’t get me wrong, I love my iPhone, but should Android provide the same slick UI elements on an open platform, I will switch in a second. Many features demonstrated on Android so far are available on other handsets, such as Google maps, but with Google’s announcement of a $10 million competition for the best applications, I am looking forward to seeing what can be done. Particularity, I am keen to see where developers go with the built-in OpenGL support. Already Google has shown some pretty cool features, though, like Street View in the Maps application.

What I am really curious about is where this leaves the Apple/Google relationship. Google is basically releasing the best competitor to the iPhone, despite Eric Schmidt serving on Apple’s board, and Google taking a large part in the development of the iPhone. I was surprised at Google’s involvement with the development of the iPhone originally, considering its love of all things open, and this proves my point in a way.

Indeed, if Android shapes up to be the open version of the iPhone as it is appearing as at this early stage, there might just be an iPhone for sale out of my place.

Posted on Nov 10, 2007

An Apple a Day

After a few weeks of talking about it, I took the plundge and bought a new MacBook Pro. This isn’t my first Mac, but I have been using Windows machines only for a while. This means that the house is totally Mac now, with my better half a dedicated Mac user (iMac 20″ currently).

It is the top-end 15″ model, 2.4GHz Core 2 Duo, 2GB RAM, and 160GB HD. It screams, and so far I have very little to complain about with it. My only issues thus far: the screen doesn’t open wide enough for how I sit it on my lap, my Logitech MX Revolution mouse doesn’t work quite right, and Firefox looks pathetic on Mac OS. Only one of those issues is Apple’s fault, though it is incredibly minor, and other than that I am completely satisfied with the machine and Leopard.

And yes, I am completely aware of the lack of originality in the title of this post.

On top of that, I came in to work on Friday to see my new workstation waiting for me on my desk. That box is a Core 2 Duo 2.0GHz, 2GB RAM, and twin 20″ LCDs (1600×1200 resolution each). Thanks boss, but it isn’t a Mac…

Posted on Jul 4, 2007

The iPhone UI Revolution

I have held off from blogging about the iPhone here much thus far, but I am going to chuck some opinion out there. This is not just about the iPhone though, it is more about how the industry needs to react because of it.

Let me say this right off the bad: the iPhone is not a device I would buy myself. It is an influential device that will do fantastically in the market, that is for sure, but its omissions are too deal breaking for me. They are also things that could have been easily remedied by Apple, and I am sure they will be fixed in a second-generation product, but for now I will do without a device that can’t record video, use 3G networks and A2DP headphones, and other things I appreciate. But more on my actual iPhone pros and cons in a future post.

What the iPhone has achieved though, is forcing the industry in general to rethink the whole user interface paradigm. Touch sensitive devices have long used a stylus, and are only now evolving to use the finger. This fact, combined with the swishing, swirling, and sliding seen in the iPhone’s UI make it a much more organic device, one that consumers may find easier to ‘relate’ to.

On top of this more organic approach to UI design, the iPhone’s interface just looks so damn good. Sure, Windows Mobile is functional, S60 is pretty, and so on, but the iPhone interface is sexy. User interface design cannot take a back seat to device design any longer, and Apple has shown us that an attractive physical design can be accompanied by a functional and attractive UI design.

While other manufacturers may not have to play catch up to Apple with technical specifications, they definitely need to with UI design. Verizon’s new Motorola Q9m features a fun circular UI enhancement, and devices like the LG Prada and HTC Touch are certainly steps in the right direction, but the iPhone just integrates everything so nicely; this is what Apple does best.

The iPhone is not the device it could have been, but for UI design, it is revolutionary. If manufacturers take nothing else away from the iPhone release, I hope it at least forces them to take a step back and reevaluate the user interface experience.

Posted on Aug 19, 2006

Click Wheel – Not the Solution for Phones

To begin, I’m not one to bad mouth convergence. While I have no real use for a music phone, I certainly don’t have a problem with manufacturers combining an audio player and a phone – it does seem like a good match. What I do have a problem with, is the fact that many are trying to take the interface of one very popular music player and make it work on a mobile handset.

Of course, the device I’m referring to is the iPod, and the interface is the click (or scroll) wheel. This input device is great in the audio player space, but it was not designed as, and will never work as, an input device for a phone.

Two recent handsets that come to mind are the Samsung i300/i310 and the LG KV2400. Both are respectable devices in their own right, especially with Samsung’s 4GB/8GB hard drives, yet both spoil functionality by using a click wheel.

One of the biggest problems with adding a click wheel to a phone is the space constraints. While the iPod’s wheel is very easy to use, when you reduce its size and place it with a myriad of other buttons, usability is severally compromised. Nokia, for once, have actually taken the right step on this issue – their N91 music phone still uses traditional phone navigation, and modifies the music player to accommodate this – the addition of non-click wheel music control keys is the icing on the cake.

I do hope that the trend I’m seeing of adding a click wheel to a phone does not continue, and that manufacturers wake up to the face that the usability of the handset should not be compromised to add a ‘cool factor’ to the music side of things.