crimera/piko: Morphe patches for Twitter/X and Instagram

What Piko changes, and who it is written for

Piko is not an app. It is a set of patch definitions that Morphe applies to an APKM file you already own, rewriting the compiled Android client rather than replacing it. The README describes the project as "Morphe patches focused on Twitter/X & Instagram," and the patch table in the README lists 74 patches for X and the remainder for Instagram, 128 in total at v3.8.0.

The audience is narrow and specific. You already use the official X or Instagram app and you want to keep using it, because the parts you care about (the login flow, XChat, the media pipeline) only exist there. What you want gone are individual behaviours: the new X Android UI on launch, the swipe-up immersive player, the floating action button, the recommended-users prompt after a follow, the tracking parameters on shared links. Piko's patch names read like a list of exactly those complaints. Block redirecting to X Lite, Hide immersive player, Hide nudge button, Clear tracking params.

That framing matters for expectations. Piko does not give you a client with a different privacy model or a different backend. It gives you the same client with a long list of switches, and the value is in how granular those switches are.

How a patch bundle actually gets applied

The mechanism is offline APK rewriting. Starting with patches v3.0.0, Piko uses Morphe, and the deliverable is a .mpp bundle, which the README's CLI example passes as piko.mpp. Morphe reads the patch definitions from that bundle, opens the APKM you supply, and produces a patched APKM you install.

The README is explicit that the input must be untouched: download the original APKM from ApkMirror, and do not unspilt or modify the file, because Morphe patches APKM directly. That is a real constraint, not a style preference. An APKM is a container holding split APKs, and the patcher needs the splits in their original arrangement to locate and rewrite the right classes.

The repository layout reflects a Gradle-based patch project: build.gradle.kts, settings.gradle.kts, a patches/ directory, plus patches-bundle.json and patches-list.json at the top level. Release automation runs through semantic-release with conventional commits, and the changelog is generated with @MorpheApp/changelog. Crowdin is wired in via crowdin.yml, so translations of patch strings are handled outside the main tree. None of this is visible to someone who only uses Morphe Manager, but it explains why the patch metadata files exist and why they are worth checking against a release.

Adding Piko to Morphe Manager and patching X

The README gives a deep link as the supported install path. Opening it registers the repository as a patch source, so there is no manual file to move.

https://morphe.software/add-source?github=crimera/piko

After that, the README lists three steps: tap the X or Instagram app icon in Morphe, download the original APKM from ApkMirror without unspiltting or modifying it, then wait for patching to finish and install. The README adds that an active internet connection is required during patching, which is easy to miss on a device you have put into airplane mode out of habit.

If you prefer to patch on a desktop, the README shows the CLI form:

java -jar cli.jar patch --patches piko.mpp input.apkm

Here piko.mpp is the downloaded patch bundle and input.apkm is the unmodified APKM. You should end up with a patched APKM in the working directory that installs over the original app. Note that the CLI invocation is the one the README gives; it does not document a rollback path or an output-path flag, so plan on keeping the original APKM if you want to start over.

One historical note the README still carries, struck through: patching X 11.88 and above once required X-Shim from another repository. The README states that starting 12.5.0-release.0 you need not apply X-Shim alongside Piko patches, and that X login and XChat work without it. The struck-through section also warns that X-Shim only adds a compatibility shim layer and does not remove pairip.

The version pin is the sharpest edge

The X patch table in the README lists exactly one supported version: 12.7.1-release.0. Not a range. One build.

That single fact drives most of the operational cost. If ApkMirror has moved on to a later X release, the APKM you download will not be the one the patches were written against, and the README does not describe what happens then. It does not promise graceful degradation, and it does not document a fallback. The conservative reading is that you must find the specific 12.7.1-release.0 APKM, which becomes harder as the version ages out of mirror listings.

The Change version code patch interacts with this in a way worth understanding. Its README description says it changes the app's version code, which turns off app store updates and allows downgrading an existing install to an older app version. That is what makes the pin survivable: you can install a patched 12.7.1-release.0 over a newer official install instead of uninstalling first. It is also a commitment, because you are now responsible for your own update cadence.

The second edge is the release channel. The three most recent releases are all v3.9.0-dev tags, the newest dated 2026-08-28. If you want a non-dev tag, the README's patch table is generated against v3.8.0. Nothing in the README says dev builds are unstable, but the naming is the only signal available, and it is worth reading as one.

Where Piko is the wrong tool

Piko is the wrong choice if your goal is to stop using the official client. Every patch here assumes the official X or Instagram binary as its base, so if you want a different client, a web wrapper, or a self-hosted front end, there is nothing in this bundle for you.

It is also the wrong choice if you are not comfortable sourcing an APKM yourself. The README points at ApkMirror and warns against modifying the file. If your device or your policy does not allow installing a patched build of a proprietary app, or if you need the app store update path to keep working, the Change version code patch is a one-way door you should not walk through.

There is a scope limit too. The README's X bundle covers a long list of interface and behaviour toggles, but the patch descriptions are mostly about what is hidden, moved, or unlocked. If you need something the list does not name, the correct move is to check patches-list.json in the repository rather than assume a nearby patch covers it. And for YouTube, which is what most people mean when they say they patch an Android app, Piko has nothing; that is a different project's territory.

The closest alternative in approach is ReVanced Extended, which the related searches themselves pair with Piko. The difference is architectural: ReVanced Extended is built around the ReVanced patcher and its own manager, while Piko moved to Morphe at v3.0.0 and ships a Morphe-format bundle consumed either by Morphe Manager or the Morphe CLI. If you already run a ReVanced-based workflow for other apps, adding Piko means running a second patching stack, not extending the one you have.

Licence, maintenance and what upgrading costs

Piko is GPL-3.0, and the repository carries both LICENSE and NOTICE files. The practical consequence for most users is nil, since you are consuming a patch bundle rather than redistributing it. If you fork the patches or ship a modified bundle, GPL-3.0's copyleft terms apply to what you distribute, and the NOTICE file is there to be carried along. That is a description of the licence, not legal advice; read the LICENSE file if you plan to redistribute.

The last push to the repository was on 2026-08-28, and the repository is not archived. Releases are frequent: v3.9.0-dev.10 landed on 2026-08-28, v3.9.0-dev.9 on 2026-08-17, and v3.9.0-dev.8 on 2026-08-16.

Upgrade cost is where the design bites. Because the X patch set targets one app version, a Piko update is only useful to you if it either adds patches you want or moves the supported version forward. When it moves, you re-download an APKM, re-patch, and reinstall, and the Change version code patch is what lets that reinstall land over the previous one. The README does not document a migration path for patch options you had configured, so treat your selections as something you may need to redo. Budget for that rather than assuming an in-place upgrade.

Editorial conclusion

Adopt Piko if you want to keep the official X or Instagram client on Android and strip specific behaviours out of it, and you accept that the X bundle is pinned to 12.7.1-release.0 and that the current release line is a dev tag. Skip it if you need a stable release tag, if you are not willing to source an unmodified APKM from ApkMirror, or if you want a patch set that also covers YouTube, where ReVanced Extended is the closer fit. Before patching, verify three things: that the patch list still names 12.7.1-release.0 as the supported X version, that patches-bundle.json and patches-list.json in the repository match the release you downloaded, and that your build of Morphe Manager is new enough to consume a Morphe-format bundle, since Piko moved to Morphe at v3.0.0.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes