Sailfish Mobile OS

Original Article ↗ Hacker News Discussion ↗

Sailfish OS, a Linux-based mobile operating system descended from Nokia’s Maemo/Meego efforts, is praised for its Unix-like openness (SSH access, RPM packages, Firejail sandboxing) and distinctive gesture-driven interface, but opinions on its usability and design are sharply divided. Users report that the platform is viable as a daily driver only for less demanding use cases, citing uneven Android app compatibility, limited native app ecosystem, hardware constraints (mainly certain Sony Xperia phones), and issues around VoLTE, cameras, and documentation. The conversation broadens into whether any alternative mobile OS can realistically compete with Android and iOS given banking apps, SafetyNet-style checks, proprietary drivers, and EU-style 2FA requirements, with many concluding that such systems will remain niche unless backed by a major hardware vendor and stronger open-source foundations.

Overall sentiment on Sailfish OS

  • Long-time users describe Sailfish as usable as a daily driver if needs are modest and rough edges are acceptable.
  • Some consider it “best mobile OS” with a simple, consistent UX and strong offline maps.
  • Others report poor UX, slow UI, awkward workflows (e.g., attaching photos to messages), and ultimately switched back to Android or hardened Android ROMs.

UI/UX and gestures

  • Gesture-driven interface (edge vs inner swipes, drag-down menus) is polarizing.
    • Fans find it elegant, one-handed, and ahead of its time (heritage from Maemo/Meego/N9).
    • Critics find it unintuitive, hard to discover, gesture-heavy, and sensitive to cases/screen protectors.
  • Visual design is seen as either pleasantly minimalist or ugly/retro (dithered, TUI-like).

Android app support and app ecosystem

  • Native app ecosystem is thin; many apps are hobby-grade.
  • Official Android support (Alien Dalvik) is described as “hit and miss”:
    • Some run major apps (Signal, WhatsApp, browsers) fine.
    • Others report networking/GPS issues, instability, and incompatibility with banking and security-sensitive apps (SafetyNet / Play Integrity).
  • Waydroid is used on some community ports but has limitations (e.g., lockscreen, some app refusals).

Architecture, libhybris, and hardware

  • Sailfish uses libhybris to talk to Android drivers; you must flash Android first and reuse its kernel and blobs (camera, GPU, modem, RIL).
  • This is seen as a pragmatic necessity a decade ago, but also a technical debt that entrenches Android’s kernel/driver model.
  • Official support is focused on specific Sony Xperia models; community ports exist for various OnePlus, Motorola, Xiaomi, etc., but usually without official Android app support.
  • Some report issues like slow cameras, GPS quirks, VoLTE gaps, or regional SIM problems.

Openness, business history, and geopolitics

  • Sailfish markets as an alternative to Android but key UI and components are proprietary; this is a deal-breaker for some.
  • Past Russian investment and a derivative (Aurora OS) used by Russian state entities are controversial.
  • Jolla restructured, shed Russian ownership, and continues under a new name; some see this as principled, others as “too late” or still wary.

Position among alternative mobile OSes

  • Frequently compared to Maemo/Meego, Ubuntu Touch, Plasma Mobile, Mobian, postmarketOS, webOS.
  • Many feel all these offer nicer UX than Android but fail on app availability, VoLTE, and polish.
  • Consensus: true third mobile ecosystem remains niche without a major hardware backer and broad app support.