UI design for Apple iPhone

As we started working on the iPhone, most of the time we got jinxed with reference to Nib files. Well, one never saw a file with extension .nib as the only available files were .xib. After some digging we found that Apple were referring to Xib files. So we got to wonder why they referred a Xib file as a Nib file as in ‘awakeFromNib’,  while it could plainly be referred to as Xib . Later we realised that Nib files come from the days of NeXTSTEP. Technically speaking whether it’s a Nib or Xib file both served the same purpose, but have different format of storing. Xib files are of XML format and Nib files are archives. But after Building an application if you open the *.app file you wont see any *.xib files, there are only *.nib files. But we haven’t created any *.nib files right? Then how did the Nib files come and where did the Xib files go? Actually while compiling the application, Xcode uses a tool named ibtool to convert Xib files into Nib files, so that we don’t have to worry about conversion from XIB to NIB. 

Enough about Nib files and Xib files, let’s talk about designing an interface using the interface builder tool.  It’s a great tool linked with Xcode.

It gives developers the choice to create xib files. Either you should create the Xib while creating the viewcontroller (used to manipulate views and subviews in Xib files) in Xcode or you could create Xib files separately and after adding to Xcode, specify the viewcontroller’s name to its File’s Owner. An application would be preferred to have a single window and multiple Views. Developers can use just the Interface Builder or Objective C to develop the GUI. Both have their own virtues and vices. Interface Builder gives an exact idea as to how components in the interface would look and feel. Developers can adjust the components to meet their needs and make sure it meets the requirements at the same instance. But to have a better dynamic behaviour and maintenance, Interface builder is a hard choice. However if it is done using pure coding it becomes hard to know whether it’s meeting the needs. It challenges the iPhone developer to have a great imagination because he can see what the interface looks like only after building and running it first time, although creating a dynamic interface is fairly simple. One need to use the right mix for best results and happy coding.

iPhone team @ Software Associates