The MeeGo interface
MeeGo OS presented two entirely different interfaces during its short life: a Clutter-based netbook shell inherited from Intel’s Moblin, and the Qt-based Swipe interface of MeeGo 1.2 Harmattan, which reached the public on the Nokia N9 in 2011 and is the one people mean when they talk about how MeeGo looked.
The two faces of the MeeGo OS interface
The MeeGo OS interface was never one design, and treating it as one design is why descriptions of it contradict each other. The netbook build, which was the first to reach finished hardware in May 2010, used a full-screen home area called Myzone with a toolbar of panels across the top for applications, status, people, media and devices. It descended directly from Moblin’s Clutter and Mutter shell and it was built for a keyboard, a trackpad and a widescreen Atom laptop.
The handset build was a separate lineage. A reference handset user experience appeared as a preview with MeeGo 1.1 in October 2010, but the interface that actually shipped to buyers was Harmattan’s, written in Qt with QML on top of the MeeGo Touch Framework. Nothing visual was shared between the two. A person who used a MeeGo netbook and a person who used an N9 did not use the same operating system in any sense they would recognise.
Swipe: navigation with no home button
Swipe was the navigation model of MeeGo 1.2 Harmattan, and its defining decision was the absence of a home button. The N9’s front face carries no button at all below the display. Leaving an application is a gesture instead: a swipe inward from any edge of the screen minimises what is open and returns to the home views, while a swipe downward from the top edge closes the application outright. A short pull from the top edge opens the status menu, with connectivity, profile and account switches.
Two further gestures completed the model. The lock screen woke on a double tap rather than a button press, and it kept a dim clock visible on the AMOLED panel while the device was idle, which costs nothing on a display that only lights the pixels it needs. Notifications accumulated on that lock screen so the device could be read without unlocking it.
The three home views
The three home views were Events, Applications and open windows, arranged side by side and reached by swiping horizontally between them. Each did one job and did not overlap with the others.
- Events collected notifications, missed calls, messages and social network updates into one scrolling feed.
- Applications held the installed software as a scrolling grid of icons, in a single list rather than in folders.
- Open windows showed running applications as live thumbnail cards, closed with a small cross on each card.
The arrangement is worth stating plainly because it is unusual even now: there was no separate desktop with widgets on it, and no distinction between a home screen and a task switcher. The three views were the shell in its entirety, and the device always sat in one of them or in an application.
Icon packs sold or given away for other operating systems that imitate the N9 look are not connected to this reference and are not distributed here. This site hosts no images, applications or theme files of any kind.
How the MeeGo interface differed from Maemo 5
The MeeGo interface differed from Maemo 5 in almost every mechanic, despite the two systems being separated by only two years and one hardware generation.
| Aspect | Maemo 5 on the N900 | MeeGo 1.2 Harmattan on the N9 |
|---|---|---|
| Input | Resistive touchscreen plus slide-out hardware keyboard | Capacitive multi-touch, on-screen keyboard only |
| Home | Four scrolling desktop panes holding widgets and shortcuts | Three fixed views: Events, Applications, open windows |
| Leaving an app | Hardware key or the title bar control | Edge swipe, with no button involved |
| Toolkit | Hildon on GTK, with Qt arriving later | Qt with QML throughout |
| Display | 3.5in, 800×480 | 3.9in AMOLED, 854×480 under curved glass |
The continuity between them is underneath rather than on the surface. Both kept Debian packaging, both gave the owner a real shell, and both assumed the person holding the device was allowed to change it. The Nokia N9 looked nothing like the N900 and behaved nothing like it, but it was the same kind of machine.
Why the MeeGo interface failed to spread
The MeeGo interface failed to spread for reasons that had almost nothing to do with the interface. Nokia announced in February 2011 that Windows Phone would be its primary smartphone platform, four months before the N9 was even shown, so the shell arrived on a device its own maker had already declined to build a line around. The N9 went on sale in a restricted set of markets from late September 2011, and no second Harmattan handset followed.
The timing compounded it. A handset interface that only reached buyers in late 2011 was entering a market where two other platforms had spent four years accumulating applications, and MeeGo had two incompatible shells rather than one, splitting what developer attention it had. The design was finished; the platform under it was not, and by September 2011 the project was being folded toward Tizen.
What survived of the design
What survived of the design outlived the operating system that carried it. Sailfish OS, built by Jolla on the Mer fork of the MeeGo core, continues the gesture model directly rather than by resemblance: it is still shipping, and it still has no home button. That is a straight line of descent from Harmattan, drawn by many of the same engineers.
The wider pattern is a matter of chronology rather than credit, and it is worth stating without overclaiming. BlackBerry 10 shipped edge-gesture navigation in January 2013, Apple removed the home button from the iPhone in 2017, and Android added system-wide gesture navigation with version 10 in 2019. No causal chain from the N9 to any of those has ever been demonstrated, and this reference does not assert one. What can be said flatly is that a phone with no home button, running an interface driven entirely by edge swipes, was on sale in 2011.