Crash Reporting

In the unfortunate event of a crash, a window apologizing for the interruption in your work flow will pop up, and suggest you send some anonymous information about this issue to our servers. We can then analyze it and fix it for a later version, to make Instantbird more stable for you.

This crash reporting system has already helped us a lot to improve the overall stability of Instantbird.

Crash detection and protection

In previous releases, the worst stability problem that occurred was a crash during start up (while automatically connecting accounts). This was very annoying since it was not possible to use the graphical user interface to change the configuration of the accounts likely to be related to the crash.

In Instantbird 0.2, we have addressed this issue by detecting if the last connection attempt finished correctly, that is, without the application being quit unexpectedly.

Start up crashes are very rare and you will most likely never run into one, but if it does occur to you: don’t worry! At the next start up, you will see the account manager pop up with a message explaining the situation and inviting you to either retry connecting or edit the configuration of your accounts:

If the crash occurred after you added an account or changed the configuration of an account, this account will be the only one that won’t connect at the next startup, and the message in the account manager will look like this:

Updates

When we identify the cause of common crashes, or when a serious issue is discovered (for example, an IM network no longer works), we try to quickly release a new minor version including a fix for the issue.

Instantbird will periodically check for updates and notify you automatically if a newer version is available. If you accept the update, it will then be downloaded automatically and applied during the next start up.

If you expect a new version, you can also force Instantbird to check now for an updates, using the “Check for updates” menu item:

Nightly builds

People who want to very closely follow the development of Instantbird can decide to receive the latest development version daily through this update system. We call these versions the “nightly builds.” These builds are produced automatically every day so that new issues can be detected early on, before they creep up into release builds.

Feel free to use them, but watch out! They may not be stable, and if you decide to use them, you are expected to do so to help us test the bleeding edge features, not just be a cool kid who’s got the new toy first. So if there are bugs, please report them (Filing a bug: what a bug report should contain) instead of complaining.

Find

Trying to find where a topic or keyword was mentioned in a long conversation is a common action. Instantbird uses the same findbar as Firefox to provide a search facility inside conversations. Just press Ctrl + F (Command + F on Mac OS X) and the findbar will appear:

However, when looking for something in a conversation, the most recent match is probably the most interesting. That’s why for Instantbird we adapted the findbar to search from bottom to top by default.

Zoom

Having trouble reading the text in conversations or fitting all the content on a small screen? Then the zoom feature is for you.

The keyboard shortcuts are the same as in Firefox: Ctrl + + to increase the size, Ctrl + - to decrease, and Ctrl + 0 to reset to the default size (Command instead of Ctrl on Mac OS X).

The changes in zoom settings are applied to all conversations at once and saved so that you do not need to adapt the zoom more than once.

Tab sizing

Tabs are sized to take full advantage of the available space: when there are only a few tabs, their width allows seeing most of the title of the conversations, and a close button is visible on each tab, making it easy to close a tab with a single click.

If there are more tabs or if the window is smaller, the tabs shrink, and the close button remains visible only on the selected tab to save space.

If the space is really too limited to fit all the conversation tabs, the tab bar becomes scrollable and a button appears to give the user a way to display a list of all tabs at once.

All this makes very small conversation windows usable.

Drag and drop

Tabs can be easily reordered, just drag a tab and drop it where you wish it to be.

Dropping a tab elsewhere detaches the tab to create a new window. The new window appears where the tab was dropped.

Tabs can also be dragged between windows:

OS integration

On Mac OS X, the active conversation window is easy to distinguish from the others, thanks to different colors of the tabs.

The way toward Instantbird 1.0

Let’s begin with a clarification about the way we are slowly but surely going to our future 1.0 release. Our initial roadmap contained the somewhat misleading claim that our goal for 1.0 was to reach “feature parity” with Pidgin. This led some people to believe that we were basically copying the Pidgin graphical user interface and reimplementing it in XUL. Although this could have held some truth for the earlier goal of Instantbird - which was to provide the extensibility that is loved in Firefox and features similar to those found in Pidgin - this is no longer the case.

When we implement a new feature in Instantbird, we carefully consider how it is likely to be used. We think about the use cases. We look at how the same problem has been handled by other existing IM clients, so that we can benefit from what others have done before us. Sometimes we take inspiration and implement something in a similar way to another client (for instance the message theme system that we have borrowed from Adium), but sometimes things don’t look satisfying and we have to look for a better solution. We especially try to avoid exposing the user to new popup dialogs that interrupt the user but don’t seem absolutely necessary.

Once something is implemented, we do our best to take advantage of the early feedback we get from our nightly testers.

So why are we doing this? Copying the interface of an existing application as quickly as possible would be easier, and would lead to a fast result. But it would be worthless. We don’t need another Pidgin, Adium, … (insert the name of your favorite multi-protocol IM application here). These applications already exist and are mostly great, there’s no point in cloning them. What we do care about is our users: our current users of course, but also future users. We believe instant messaging should be less frustrating. We want to build an all-in-one instant messaging application that is as easy as possible to use, yet powerful. We value simplicity and ease of use in the default configuration, and at the same time we want to allow advanced customizations. Developers with an idea should be able to easily customize their IM client, like they can already do with their web browser.

We value privacy, and respect your data. Instant messages often have confidential or intimate content. We believe that our users should have the power to decide how this information is used, and where it is stored. This is the reason why even though more and more users decide to use web applications like Gmail, Facebook or Meebo for their IM needs, we believe that it is still relevant in 2010 to build an IM application that runs directly on the computer you own.

We don’t know yet how Instantbird 1.0 will be, it will need to be discussed. With You. At this point we are discussing which improvements will compose the 0.3 release. If you want to take part in this discussion or have questions related to our long term goals, don’t hesitate to get in touch with us.

What’s next?

We are confident that if you have tried a release from the Instantbird 0.1.* series, you will see Instantbird 0.2 as major improvement. And if you haven’t used Instantbird before, then the 0.2 release is a great time to start! In the next few days, we will detail a few of the features that already make Instantbird 0.2 a very usable instant messaging application, despite its low version number.