Sep 02

What were they thinking: iTunes 10

Apple has been known to be a company that puts a great deal of emphasis on ensuring that applications meet users expectations. This can easily be seen by the strict review process that all iPhone applications have to go through. While watching the live keynote at 3am(Sydney time) I quickly noticed one very interesting feature within iTunes 10…

Screenshot of iTunes 10 titlebar buttonsFor those that cant notice what it is, the ‘close’, ‘minimise’ and ‘optimise?’ buttons are kinda… weird….

  • No titlebar
  • Vertically placed
  • Smaller then all other system buttons.

After thinking about this strange layout I have a theory as to why they did this. Since iTunes 8(or 9… im not too sure) the pesky green ‘optimise?’ button has not done what all other apple applications do… optimise the size of the application window for the content thats inside. Yea sure some applications (like firefox and even microsoft word for mac) choose not to adhere to Apples interesting philosophy of ‘optimise?’ and choose to make the button behave in a ‘maximise’ manner like on windows computers. For some weird reason, the iTunes 8 button collapsed the application window to the mini-player mode.

Does Apple think that making the buttons appear to be different to the rest of the OS mean that users will be reminded that pressing them wont do what they expect?.. I don’t know.. I most certainly don’t like it! I think today is the first day that i haven’t been able to minimise iTunes by double clicking. Sigh. Nothing I can do now but get used to it. What a bad fruit.

Feb 24

iWebKit5 comes to Firefox

Recently i have been working on taking the iWebKit 5.0 framework and producing a CSS extension that allows pages to be ‘better’ rendered on Firefox. Checkout its homepage at:

Checkout the a screen shot of it in action:)

Using this couldn’t be easier! All you have to do is add the ‘extension’ CSS to your header after the official CSS.

Special thanks to the Soft-V2 theme of iPhone icons for the ‘installer’ icon. Grab the fill list of icons at:

Feb 15

iPhone Web Application frameworks

Have you ever wanted to create a web application for iPhone/iPod touch but didnt want to fiddle with the CSS to make it look right? Well fortunately there are a few different frameworks that you can use to do this.

The Apple way

If you are hip enough to be running a mac, you can use Dashcode, It gives you:

  • Super quick and easy.
  • Drag and drop.
  • RSS
    • Maybe more?
  • Works on iPhone and iPod touch.
    • More then 66% mobile market share in March 2009 probably more today.
  • Does not work on non safari browsers(not even WebKit!).
    • Including Google Chrome!
    • Means 95% of web users cant use your application!
  • Have to learn to use Dashcode.

The other way

Lets face it, Dashcode sucks and most people dont have access to a mac for development. There are a few different 3rd party frameworks available which might be harder to use but give you(the web developer) real control on how you want your content to appear! Here are some frameworks that I have seen or used in the past.

  • iUI. Used it before.
  • CiUI. Cnet’s tweaked version of iUi
  • UiUIKit. This is what its called, I’m not making this up!
  • Never used but looks promising.
  • QuickConnectiPhone. Not too sure about this.
  • iWebKit. I have used this framework many times. It’s easy to use and allows you to make webapps that look like native apps.
  • jQTouch. jquery with touch! If you want all the bells and whistels like animations, this is the framework for you! I’m looking into using this for a project in the future, I’ll be sure to post what I think of it.

If you don’t know where to start, I would suggest iWebKit or jQTouch, but it won’t be a bad idea checking out the others.

What about Mozilla Firefox?

Some readers will notice that I haven’t mentioned the use of these frameworks on non-webkit browsers like Firefox. I have found that the best frameworks don’t do a very good job at being cross platform due to the fact that they are all trying to save your precious download quota by using the draft WebKit CSS3 functionality to render the gradients and boxes instead of static images.

If your framework of choice is iWebKit, I have extended the css stylesheet to allow FireFox 3.x to render half decently. You can grab the iWebKit_4.6.2 framework here(Its no longer available on its homepage anymore)and the iWebKit 4.6.2 Firefox CSS Style. I am currently working on a iWebKit5 version which has a better structured, I’ll post that here when its ready;).