Moodify Studio desktop-v1.0.1-rc.4

Verification

Source:
https://github.com/huliye24/moodify-ai

License:
GNU GPL v3

Build:
GitHub Actions

Windows code signing:
SignPath Foundation

Integrity:
SHA256SUMS.txt

Provenance:
GitHub Artifact Attestation

Verify the download before running it

# 1. Integrity — the checksum must match the file you downloaded
sha256sum -c SHA256SUMS.txt

# 2. Provenance — this binary was built by this repository's CI, from a specific commit
gh attestation verify Moodify_Studio_*_Setup_x64.exe --repo huliye24/moodify-ai

# 3. Publisher — Windows Authenticode signature
#    PowerShell:
Get-AuthenticodeSignature .\Moodify_Studio_*_Setup_x64.exe | Format-List Status, SignerCertificate, TimeStamperCertificate

Honest boundaries

• Windows code signing is performed by SignPath Foundation, not by
  Moodify. The publisher shown in the Windows properties dialog is SignPath Foundation.
  This is the accepted trade-off while the project is zero-cost. See
  WINDOWS_CODE_SIGNING.md.
• Signing and provenance are different guarantees. Signing says who published the bytes;
  attestation says which commit and workflow produced them. Neither one says the software is
  free of defects, and neither is a claim that the app is "safe" or "certified".
• A valid signature does not by itself remove the SmartScreen warning. Reputation
  accumulates over downloads; a newly signed binary may still prompt for a while.
• Before signing is enabled, RELEASE_MANIFEST.json reports code_signed: false. That value is
  measured from the artifact, not hardcoded. Do not read an unsigned release as a signed one.

What is in the artifact set

File	What it is
Moodify_Studio_<version>_Setup_x64.exe	NSIS installer
Moodify_Studio_<version>_Portable_x64.exe	portable executable
SHA256SUMS.txt	SHA-256 of the executable(s) above, computed after signing
RELEASE_MANIFEST.json	version, commit, measured signature facts, artifact digests
SIGNATURE_FACTS.json	raw output of the signature verification step

Moodify Music 3.1.0

Moodify Music 3.1.0 for Android

This release completes the local-file handoff flow used by QQ and similar apps:

QQ file preview -> Open with -> Moodify -> play the handed-off file

Behavior

• Accepts the temporary content:// file permission supplied by QQ.
• Reads audio URIs from Intent data, EXTRA_STREAM, or ClipData because sender implementations differ.
• Does not require the Moodify cloud catalogue before showing or playing the local file.
• Displays the handed-off file's actual display name on the existing Moodify player screen.
• Preserves sender order when multiple audio files are handed off; vertical swipe changes tracks as before.
• A cloud catalogue refresh cannot replace the active local queue.

Compatibility

• Package: com.moodify.app
• Version: 3.1.0 (versionCode 31)
• Minimum Android: 8.0 (API 26)
• Same signing identity as Moodify 2.0/3.0 for direct upgrade.
• Launcher icon and visual design unchanged.

Verification

• testDebugUnitTest: passed.
• assembleDebug: passed.
• APK SHA-256: 60acfcfac9a73c3ef74932dd4d1855d1246f8b169b0e4d66c1e2daf323874337.

Final QQ validation requires opening a QQ-hosted audio file on the physical phone because QQ's content provider is not present on the build machine.

Moodify Music 3.0.0

Moodify Music 3.0.0 for Android

Moodify 3.0 extends the 2.0 player so existing and older songs can enter Moodify directly from Android's “Open with” and sharing flows, supporting the product direction: preserve the song's identity while giving it a new listening experience.

Install

• APK: Moodify_Music_3.0.0_Android_20260816.apk
• Package: com.moodify.app
• Version: 3.0.0 (versionCode 30)
• Minimum Android: 8.0 (API 26)
• Signing: same Android debug certificate as Moodify 2.0, so the installed 2.0 build can be upgraded directly.

Added in 3.0

• Moodify appears as a candidate for audio files opened from QQ, WeChat, file managers, and compatible apps.
• Supports Android VIEW, SEND, and SEND_MULTIPLE handoff for audio/* and Ogg audio.
• The first handed-off song is loaded as the active single-song queue and starts playing in the existing Moodify player.
• The existing player surface displays the handed-off file's own name instead of a cloud catalogue title.
• A background catalogue refresh cannot replace an external song while it is playing.
• Repeated handoff reuses the existing activity and replaces the active queue without duplicating the UI.

Explicitly unchanged

• Desktop/launcher icon and round icon.
• Existing 2.0 Compose UI, navigation, typography, colors, launch screen, and controls.
• Package/application identity and signing certificate.
• Cloud catalogue and existing streaming behavior.

Android and OEM resolver ranking is adaptive. The manifest gives Moodify a direct, specific audio match, but Android does not provide an API for an app to force itself permanently to the first position. Selecting Moodify repeatedly or setting it as the default can move it forward according to the device's resolver behavior.

Verification

• testDebugUnitTest: passed.
• assembleDebug: passed.
• APK manifest inspected: package/version and all three audio intents present.
• 2.0 and 3.0 signer SHA-256: 721bd3ca7b6f852205eb0c866fb2e2e4d6af3d2ef39cffdb85db7e986160c38c.
• UI and launcher resource directories have no source diff from the 2.0 release commit.

Physical-device QQ/WeChat resolver visibility still requires installation on the target phone and one manual handoff check because those apps and OEM resolvers vary.

Moodify Music 2.0.1

Moodify Music 2.0.1 for Android

Moodify Music 2.0.0

Moodify Music Android 2.0.0

发布日期：2026-08-15

安装

在 Android 8.0（API 26）或更高版本设备上安装 Moodify_Music_2.0.0_Android_20260815.apk。

从 Moodify 1.0.0-rc.2 升级时可以直接覆盖安装；两个版本使用相同的内部 Debug 签名证书，覆盖安装会保留本地数据。

首次使用

1. 打开 App，等待公共曲库载入。
2. 首次进入不会自动播放，点击 Play 开始。
3. 上下滑动切换歌曲；播放启动后会连续播放，主动暂停后切歌保持暂停。
4. 点击心形收藏当前歌曲；点击“＋”加入已有歌单或创建新歌单。
5. 子界面左侧边缘向内滑打开抽屉，右侧边缘向内滑返回 Play。

缓存

App 会在后台预取最多 10 首歌曲的起播数据，并使用上限 512 MB 的磁盘 LRU 缓存。缓存可以被 Android 系统或用户安全清理，清理后会自动重新建立。

文件完整性

安装前可使用 SHA256SUMS.txt 校验 APK、日志和说明文件。此包是内部体验固定版，不是应用商店生产签名版本。