Messaging and MMS
WhatsApp on the Nokia N900 is not supported: Nokia never certified the application, the store never delivered it, and the Maemo 5 platform could not run the Android or iOS builds that WhatsApp shipped in 2009 and 2010. The N900 did carry a full messaging stack of its own, built around the Maemo platform, and it handled SMS, MMS, email and instant messaging through programs you could install yourself from the community repositories. The short answer for the N900 is no, and the long answer explains what you could actually install instead, how MMS worked on these tablets, which store supplied it, what the community added afterwards, and why the successor hardware changed the answer.
The Nokia N900 is the device this page is about: Nokia's internet tablet, sold from 2008 to 2010, running Maemo 5 on the N800 chip set at a 600 MHz processor speed. The rest of the mainstream Nokia range took a different path. The N8, the 2010 flagship running Symbian, was where Nokia's messaging focus actually lived, and the N8 received the first Nokia-branded WhatsApp in 2013, roughly 3 years after the N900 had been discontinued.
The messaging stack that shipped on Maemo
The messaging stack that shipped on Maemo split into 4 layers: the modem, the core service, the client applications, and the store that distributed them. The N900 carried a 3G modem with EDGE and GSM fallback, so a single data connection carried both the internet traffic and the SMS and MMS signalling. The core service ran as a background daemon on the Maemo platform, holding the SMS and MMS stores in local memory rather than in a phone book app. The client layer was a family of separate applications instead of one combined Messages app: the Messages program for SMS and MMS, Picaso for email, and an instant messaging client for the chat protocols of the era. The distribution layer is where the N900 diverged from a normal phone, as the next section explains.
Where applications came from on the N900
Where applications came from on the N900 is the part most people who own the device still remember, and it comes down to two different channels. The Ovi Store was Nokia's official application marketplace, and on the N900 it carried a curated selection of programs that Nokia had signed off. The Ovi Store on this device never carried WhatsApp, and it never carried a large general catalogue either, so most owners moved their attention to the second channel, the community repositories. Through the package manager you could search the repositories by name and install an application in a single tap, the same Debian-based mechanism that a desktop Linux user would recognise. The practical result was that the N900's application world was wider than the store listing suggested, and narrower than the Android world of the same years. What you could actually install covered the daily needs of a tablet user: an email client, a web browser with a full desktop site mode, an instant messaging client for Jabber and Google Talk, an office suite, media players, and a selection of games. What you could not install, on the official channels, was the mobile messengers that dominated 2010, and that gap is the one that later surfaced in the search results for this device.
How SMS and MMS worked in practice
How SMS and MMS worked in practice on the N900 came down to the configuration of the carrier, not to the hardware. Once the network profile was set, the Messages client sent and received SMS over the GSM channel and handled MMS over the packet data connection. MMS on Maemo had 3 limits that owners learned by heart: the size ceiling per message, the number of parts per message, and the expiry window after which an unsent draft was dropped. A typical MMS carried one photo compressed to a few hundred kilobytes plus a short text, which sat comfortably under the ceiling. The N900's camera recorded video at up to 720p, and a single frame from that footage made a reasonable MMS attachment, while a 1 minute clip of it did not. Group messages used the MMS path, which is why a group text behaved differently from a one to one SMS: the sender saw a delivery report per recipient, and the recipients saw the group as a single thread only if the carrier supported it. For a tablet that most people used as a data device with a secondary role as a phone, that level of MMS support covered the use cases that actually came up, from a holiday photo to a quick file handoff.
What the community added after the store era
What the community added after the store era is the part that kept the N900 usable well past its end of official support. The Maemo community, organised around the maemo.org project and the repositories that fed the package manager, kept building for the platform after Nokia's investment shifted to MeeGo and then to the Jolla phones that followed. The additions fell into 3 groups. The first group filled the messenger gap with clients for the protocols that WhatsApp had displaced or outgrew: Jabber, Google Talk, IRC, and later a growing set of open chat protocols, so group conversation moved to those rooms. The second group hardened the MMS and SMS path, with fixes for the expiry behaviour, better handling of message parts, and tools to export the local message store. The third group was the general application layer, from a hardened web browser to file managers and terminal tools that treated the N900 as a small Linux machine rather than a phone. None of these projects were the work of Nokia or of the original Maemo Freak blog, and none of them ship the branded messengers of the era. The independent status matters: this page documents what existed, and it hosts no firmware, no ROMs, and no repackaged applications, the way the community archives that still carry the original packages do. If you hold a working N900 today, the community packages remain the honest path for messaging, and the expectation should be set at the level of SMS, MMS and open chat, not at the level of the branded messengers.
What happened on the successor hardware
What happened on the successor hardware explains why the answer to the WhatsApp question is different now than it was in 2010. After the N900, the lineage of Maemo hardware moved through Jolla, and the Jolla phones of 2013 and 2016 ran Sailfish OS, the platform that Maemo's code and its community had carried forward. Sailfish OS shipped with a working Android compatibility layer, so a device that could not run WhatsApp in 2010 could run the Android build of WhatsApp on a later handset in the same lineage, and that is the sense in which the question now has a yes answer, on the successor and not on the N900. The N8, by a separate route, got a native Nokia-branded WhatsApp in 2013, which is why search results pair the N8 with the question so often. The table below sets the three devices side by side.
| Device | Platform and years | WhatsApp status |
|---|---|---|
| Nokia N900 | Maemo 5, 2008 to 2010 | Never supported; no official client existed for the platform |
| Nokia N8 | Symbian, 2010 to 2012 | Nokia-branded WhatsApp arrived in 2013 |
| Jolla phones | Sailfish OS, 2013 and 2016 | Android compatibility layer runs the standard client |
The pattern across the 3 devices is the same story told 3 ways: the messenger followed the platform that the store could certify, and the N900's open application model, which was its strength for everything else, was exactly the reason it never received the one app that later became the default.