omarchy-app

Building an Omarchy App

Omarchy's own apps are dead simple on purpose: one window, one job, driven from the keyboard, following the desktop theme, and installed like any other package. Build new ones the same way. templates.md has the starter files; the published apps are the reference for anything bigger:

• Omacut, a video trimmer: https://github.com/omacom-io/omacut
• Monologue, a webcam recorder: https://github.com/omacom/monologue
• Hype, Markdown presentations: https://github.com/omacom/hype
• Signed, PDF signing: https://github.com/omacom/signed

Before writing code

Ask what the app should do if it isn't clear, and settle the one job it does. Pick a short lowercase name (tally, pomo); it is the binary, the package, the .desktop file, the icon, and the Wayland app id all at once. Create the project in ~/Work/<name> unless the user says otherwise, and git init it.

Everything an app needs is part of Omarchy: qmake6, make, a C++ compiler, Qt's base, declarative, multimedia, SVG, and Wayland modules, and ffmpeg. If qmake6 is missing, install the set with omarchy-pkg-add base-devel qt6-base qt6-declarative qt6-multimedia qt6-svg qt6-wayland ffmpeg.

Shape

<name>.pro              qmake project: Qt modules, sources, resources
bin/build               qmake6 + make into build/<name>
bin/test                builds and runs the Qt Test binary offscreen
bin/install             makepkg -fsi, so the app lands in the launcher
src/main.cpp            app setup; hands C++ objects to QML
src/backend.{h,cpp}     the app's state and work, as a QObject
src/theme.{h,cpp}       follows the Omarchy accent and Hyprland's rounding
src/Main.qml            the window: layout, keys, nothing else
src/resources.qrc       compiles the QML into the binary
tests/<name>_tests.{pro,cpp}
pkgbuild/PKGBUILD  pkgbuild/<name>.desktop  pkgbuild/<name>.svg
README.md  LICENSE  .gitignore

src/ stays flat. No CMake, no build directories checked in, no generated files committed.