QUIK: a GPLv3 SMS messenger for Android that continues QKSMS

What QUIK replaces and who it is for

Android phones ship with a messaging app chosen by the manufacturer, and that app is usually tied to the vendor's account, telemetry or update cycle. QUIK is the open source alternative. The README describes it as "an open source replacement to the stock messaging app on Android" and as "a continuation of QKSMS", the messenger Moez Bhatti built and maintained before it stopped moving. QUIK picks up that codebase under the GPLv3 and keeps it building.

The audience is narrow and specific. You need an Android device, you need to send SMS or MMS through a carrier SIM, and you want the client to be something you can read the source of. QUIK is not a VoIP service, not an encrypted messenger, and not a way to message someone who does not have a phone number. If your messages travel over the internet rather than the carrier network, this is the wrong class of app entirely.

The feature list in the README is where the practical case sits: scheduled messages, delayed sending, message backup, message blocking and archiving, voice messages, attachments of any type, message pinning and sorting, quick reply from notifications, swipe actions, and emoji reaction handling. Those are the things people leave the stock app for.

How QUIK is put together: modules and the SMS/MMS layer

The repository is a multi-module Gradle project rather than a single app folder. The top level contains presentation/, domain/, data/ and common/, which is a layered split: presentation holds the UI, domain holds the use cases, data holds persistence and repositories, common holds shared code. There is also android-smsmms/, a vendored copy of the SMS/MMS library that the README credits to Jake and Luke Klinker. That library is the part that actually talks to the Android telephony stack for SMS and MMS, so it is the piece to look at when MMS behaves differently from SMS on a given device.

Build configuration lives in build.gradle, settings.gradle and gradle.properties, with the Gradle wrapper checked in as gradlew and gradlew.bat. There is a fdroid/ directory for the F-Droid build flavour and a metadata/ directory, which is the usual place for F-Droid store metadata. The releases/ and repo/ directories sit alongside a secrets.tar.enc file, which indicates signing material is kept encrypted in the tree rather than in the repository in the clear.

The practical consequence of this layout: the app is not a thin wrapper around an Android intent. It carries its own messaging stack, which is why it can support attachments of any file type and MMS handling at all, and also why device-specific MMS bugs are a recurring category rather than a solved problem.

Installing QUIK on Android and sending a first scheduled message

The README does not document a build-from-source walkthrough, so the supported route is to install a prebuilt APK. Two sources are named: the official GitHub releases page, and F-Droid. The README also offers an Obtainium link that points at the GitHub repository, which is a way to have Obtainium track new releases and install them for you.

If you install manually, download the APK from the releases page and open it. Android will ask you to allow installing unknown apps for whichever app you used to open the file. The package name matters here: the GitHub builds use dev.octoshrimpy.quik and the F-Droid build uses dev.octoshrimpy.quik.fdroid. Because those are different application IDs, the two builds install side by side rather than over each other, and switching between them means your message history does not follow automatically.

Once QUIK is running, Android will prompt for it to become the default SMS app. That step is required: only the default SMS app can read and write the SMS database on modern Android, so QUIK will show an empty conversation list until you accept the role. The README's feature list is what you exercise next, and scheduled messages are the clearest example of something the stock app does not offer. The repository ships the Gradle wrapper at its root, and the top-level entries include the fdroid/ directory used for the F-Droid build flavour.

Where QUIK will disappoint you

The most obvious limit is stated by the project itself: the README says QUIK is a continuation of QKSMS, which means the codebase is inherited rather than new. That shows up in the module layout and in the vendored android-smsmms library, which is a third-party component the maintainer does not control. When MMS breaks on a particular carrier or device, the fix may sit in code QUIK does not own.

MMS is the second limit. The README thanks the Klinker brothers for their work on android-smsmms and calls it "an unspeakably large help in implementing MMS into QUIK", which is an acknowledgement that MMS is hard enough to need a dedicated library. MMS depends on carrier APN settings, and the README does not document any APN configuration UI or troubleshooting procedure.

Third, the README does not document rollback. If a release breaks something on your device, there is no described downgrade path, no described data migration, and no described compatibility guarantee between versions. Message backup is a listed feature, which gives you a way to preserve history, but the README does not say whether a backup taken on one version restores cleanly on another.

Finally, the README's bug reporting section asks for steps to reproduce, the QUIK version, and device and OS information. That is a reasonable template, but it also tells you the maintainer expects device-specific reports, not a single reproducible failure across all hardware.

Fossify Messages and the difference in approach

The natural comparison is Fossify Messages, which appears in the related searches alongside QUIK. Both are open source Android SMS clients, but they come from different lineages. QUIK is a continuation of QKSMS and carries the layered presentation/domain/data/common module split plus the vendored android-smsmms library for MMS. Fossify Messages belongs to the Fossify family of apps, a set of forks that share a common approach to Android app development across several utilities.

That difference matters when you are choosing. If you already use other Fossify apps, their messaging client gives you a consistent set of settings and a shared maintenance model. If you used QKSMS and want the feature set you remember, including scheduled messages, message pinning, swipe actions and emoji reaction handling, QUIK is the direct continuation. Neither choice is about which app is better in the abstract; it is about whether you want a single-app lineage or a family of apps maintained together.

The README does not offer a feature-by-feature comparison with Fossify Messages, so any claim about which one handles a specific case better would have to come from testing both on your own device.

Maintenance, releases and what GPLv3 means here

The repository is not archived, and the last push was on 2026-09-23. The releases shown are v4.3.7 on 2026-09-23, v4.3.6 on 2026-04-19 and v4.3.4 on 2026-01-25. That is a release roughly every few months, with the gap between v4.3.6 and v4.3.7 being the longest of the three. The README does not publish a support policy, a deprecation timeline, or a minimum Android version, so the release cadence is the only signal available about how quickly a fix will reach you.

Upgrade cost is low if you install through F-Droid or Obtainium, since both track new releases. It is higher if you build from source, because the README does not pin toolchain versions and you are relying on the Gradle wrapper and whatever CONTRIBUTING.md says. There is also the package-name split to remember: dev.octoshrimpy.quik for GitHub builds and dev.octoshrimpy.quik.fdroid for F-Droid, which means an upgrade path between the two is not automatic.

On licensing, QUIK is released under GPLv3, with the licence text in the LICENSE file at the repository root. For someone installing the app, that changes nothing about daily use. For someone modifying and redistributing it, GPLv3 carries obligations about source availability and licence propagation that a permissive licence would not. That is a description of the licence, not legal advice; read LICENSE and, if you plan to redistribute, get proper counsel.

Editorial conclusion

QUIK fits Android users who want scheduled sending, message backup and blocking in a GPLv3 app they can install from F-Droid or the GitHub releases page, and it fits anyone still running QKSMS who wants the maintained continuation. It is not for anyone who needs an iPhone client, a cross-platform desktop messenger, or an app whose release cadence is guaranteed, since the README does not describe one. Before installing, check the release notes for the version you pick, confirm the package name (dev.octoshrimpy.quik on GitHub, dev.octoshrimpy.quik.fdroid on F-Droid) because the two builds are not interchangeable, and read the PRIVACY file to see what the app does with your messages.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. quik-sms/quik on GitHub
4. README
5. Releases