An open desktop home for HWP
HOP addresses a problem that is easy to miss outside Korea: HWP documents remain common, but convenient, high-fidelity software for them is not equally available on every desktop platform. HOP packages the open-source rhwp engine inside a Tauri 2 application for macOS, Windows, and Linux. It adds the behavior people expect from a desktop editor, including file associations, drag and drop, native menus, multiple windows, printing, PDF export, and save commands.
The scope is deliberately modest. The README calls HOP a thin shell over rhwp, which handles parsing, rendering, and editing. That is a sound split. HOP can focus on operating-system integration while upstream improves the difficult document engine. The MIT license applies to HOP, and the project gives clear credit to its engine rather than presenting upstream work as its own.
The main language is Korean. That matches its audience, and the documentation is direct, but international users should know that the README, setup notes, development guide, and issue discussion are mostly Korean. The keyboard-shortcut reference is in English, yet there is no equivalent English user guide. Browser translation can cover the basics, not nuanced troubleshooting.
The everyday workflow is already coherent
HOP opens both HWP and HWPX files. It can save HWP, save under a new name, export a document as PDF, open the system print dialog, associate file extensions, and keep documents in separate windows. Those basics make it more useful than a parser demo. Installers cover Apple Silicon and Intel Macs, Windows x64, DEB and RPM Linux systems, Linux ARM64, and a portable AppImage. Homebrew and an AUR package widen the practical install options.
The project also shows good desktop engineering instincts. The development guide describes atomic HWP saves: write a temporary file, parse it again with rhwp, and replace the original only after structural validation succeeds. It also detects external file changes before saving. macOS integration includes recent documents and Quick Look work in the source tree. A healthy set of TypeScript and Rust tests covers commands, document files, platform behavior, rendering, fonts, and Linux runtime handling.
None of that makes format fidelity automatic. HWP is a complex document format, and desktop rendering adds fonts, printer paths, webviews, graphics drivers, and input methods. HOP inherits engine limitations from rhwp and can introduce shell-specific faults of its own. The issue template usefully asks reporters to compare the same file in the upstream demo, which helps locate ownership.
Saving is where caution matters most
HWPX saving is disabled. The development guide says HWPX can be opened but will remain read-only until a safe serializer is available. Anyone who receives HWPX and expects a normal edit-save cycle should stop there. Exporting or converting through another route is not the same as preserving an editable original.
HWP saving exists, but important files still deserve a copy. Issue 73 reports that an HWP edited and saved in version 0.3.1 became unreadable in both Hancom's client and HOP. The maintainer's version 0.4 design prevents a structurally invalid result from replacing the original, which is meaningful protection. The response also says this cannot prove Hancom compatibility or catch semantic damage to particular control characters or objects without a reproducible source document. The issue remains open.
There is no autosave or recovery yet. A crash, power loss, or mistaken overwrite therefore has fewer safety nets than users may expect from an established office suite. Until those pieces exist, duplicate the original before editing and open the result in its intended recipient application before sending it.
Printing and Linux input remain uneven
Issue 78 provides a concrete complex-table case where direct printing omitted or overlapped cell text. The maintainer traced the overlap to upstream layout and pagination, and an upstream correction later merged. HOP still needed to update its embedded engine and complete regression testing, so the report stayed open. PDF export behaved better in the reporter's original workflow, making export-first a sensible check, not a universal guarantee.
Linux has the usual webview and input-method matrix. The README recommends DEB or RPM packages before AppImage and warns that some Wayland or IME environments may show unstable Korean-English switching or windows. Issue 77 describes visibly slow Korean composition with Fcitx5 on Fedora KDE, tied to graphics workarounds that trade flicker or crashes against redraw cost. Issue 79 reports Korean input not working on Pop!_OS. Users should test their exact distribution, session type, and IME before adopting HOP for daily writing.
Package trust is another rough edge. Windows builds are not signed, so SmartScreen or browser warnings are expected. The README says macOS DMGs are signed and notarized, but issue 89 reports that the version 0.4.1 Apple Silicon app installed through Homebrew fails strict code-signature and Gatekeeper checks despite carrying a notarization ticket. Managed environments should verify the downloaded artifact rather than rely on the label.
A fast-moving project, not a finished office suite
HOP was created in April 2026 and released versions 0.1.5 through 0.4.1 by July 21. The repository's last push and latest release were both July 21, while issue activity continued into August. GitHub showed 14 open issues and one open pull request on August 13. Maintainer replies often include reproduction details, upstream ownership, and a specific verification request, which is a good sign for a young project.
The development guide is equally candid: autosave, recovery, safe HWPX serialization, large-document architecture, and parts of signing and updater infrastructure still need work before the stated public-beta threshold. That honesty makes HOP easier to recommend within limits. Use it to read HWP files, export a checked PDF, or make reversible edits to a copy. Do not yet make it the sole editor in a workflow where one damaged layout or incompatible save has serious consequences.