Please update the public source to match the released app versions

[TarekMedhat]

Hi, thanks for sharing this project.

I’m trying to review the app before installing it, and right now it’s hard to verify the released APKs against the public repository because the public source does not appear to match the versions being advertised.

What I found:

• main and v0.12.0 currently point to the same commit: ad33ee2da161e8dd4ed008ab57d519ba145a024d.
• That commit is dated 2026-04-17 and its message is Update README.md to v0.12.
• The Android project in that same commit still reports versionName = "0.2.0" in android/app/build.gradle.kts.
• The README advertises later features such as REC / unlimited-length recording on the phone, but the public Android source does not appear to contain the corresponding implementation.

Could you please update the public repository so it matches the released APKs / announced versions?

Right now it’s difficult for users to independently verify that the published APKs correspond to the public source, which is especially important for a sideloaded app that requests sensitive permissions such as microphone access.

Thanks.

[przemek-nowicki]

Hi, first of all, thank you for your comment and interest in the project. Please see the Android README file for details. I agree, and I will update the source code with the REC-advertised functionality and all the permissions required by the APK distribution in upcoming releases. Just a bit busy recently, but it’s on my list.

[bhaskarblur]

Hi @przemek-nowicki Please update source code to the earliest, as i want to work on IoS version for this + some more features.

Thanks

[przemek-nowicki]

@bhaskarblur Thank you for your interest. I really appreciate it. I am thinking about how to do this in a way that works for you while not sharing things I would rather keep proprietary, as I have put a lot of effort and money into those modules.

Any ideas are welcome, of course ✌️

About the iOS we already have iOS but the problem is not implementation, but the distribution.
The issue is that the Meta SDK is not public, so we need to wait until Meta publishes it. Otherwise, it will not pass App Review. Sideloading on iOS means we will never publish it to the App Store. TestFlight also comes with tons of limitations.

[bhaskarblur]

@przemek-nowicki I see, Thanks for letting me know the actual reason.
You're doing great work and i respect that you want to keep some modules as private since you've put your efforts into this.

Please lay down a good way for community to contribute to this + you also keep your things private so that this project can grow. Maybe you can use some other repository as private to do distribution on app/play stores and monetize it. And this project you can sync the free features.

My aim is to be able to use this on my IoS device and add more features that make the meta glasses more useful, handy and worth buying

[przemek-nowicki]

Plan for this issue:
Step 1: The APK files with proprietary modules will be moved to a new repository.
Step 2: v0.14 will be the last APK version published through this repository, as the app is currently tied to the hardcoded release URL from this repo. Once users switch to the new URL with v0.14, the APKs will be removed from here so that this repository only contains APK builds based on the provided source code.
Step 3: The source code will be synced, excluding the proprietary modules.

bhaskarblur - thank you for your insight.

[bhaskarblur]

Sounds good,
looking forward to this plan