#stable #release
App Manager v4.0.1
- Overlay management
In the App Details page, a new tab “Overlays” is added where per-app overlays are displayed. They can also be enabled or disabled using the toggle button. In addition, if the App Details page of an overlay package is opened, a “Overlay” tag will be displayed in the App Info tab. Clicking on the tag opens a dialog containing additional info along with a button that allows navigating to the App Details page of the overlay target package if it is installed.
Known limitation: At present, it only works for root/ADB users in Android 8 (Oreo) and later.
- Unfreeze option in activity shortcuts
If the application corresponding to the shortcut being launched is frozen, App Manager will now offer you to unfreeze the app temporarily so that the shortcut can be launched. The app will be frozen again once the screen is locked.
Known limitation: This may not work on devices without a screen lock or if the screen is locked some time after the display goes off.
-
Third-party applications can now open the App Details page of any installed package by invoking an Intent with an URL with the following format:
where
- Updated color codes
In order to improve accessibility, certain color codes have been improved. Visit Settings > About > Version/Changelog for details.
- Others
* Avoided waiting for the remote server to respond when no-root mode is set
* Fixed downgrading apps in Android 10 onwards
* Fixed installer issues in the Huawei stock operating systems
* Improved text formatting in the “What's New” dialog
* In the UI tracker window, fixed clicking on the icon after it is iconified
* Updated bloatware and suggestions
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.0...v4.0.1
App Manager v4.0.1
- Overlay management
In the App Details page, a new tab “Overlays” is added where per-app overlays are displayed. They can also be enabled or disabled using the toggle button. In addition, if the App Details page of an overlay package is opened, a “Overlay” tag will be displayed in the App Info tab. Clicking on the tag opens a dialog containing additional info along with a button that allows navigating to the App Details page of the overlay target package if it is installed.
Known limitation: At present, it only works for root/ADB users in Android 8 (Oreo) and later.
- Unfreeze option in activity shortcuts
If the application corresponding to the shortcut being launched is frozen, App Manager will now offer you to unfreeze the app temporarily so that the shortcut can be launched. The app will be frozen again once the screen is locked.
Known limitation: This may not work on devices without a screen lock or if the screen is locked some time after the display goes off.
-
market-like URL supportThird-party applications can now open the App Details page of any installed package by invoking an Intent with an URL with the following format:
app-manager://details?id=<pkg>&user=<user_id>
where
<pkg> stands for package name, and <user_id> stands for the user ID which is optional.- Updated color codes
In order to improve accessibility, certain color codes have been improved. Visit Settings > About > Version/Changelog for details.
- Others
* Avoided waiting for the remote server to respond when no-root mode is set
* Fixed downgrading apps in Android 10 onwards
* Fixed installer issues in the Huawei stock operating systems
* Improved text formatting in the “What's New” dialog
* In the UI tracker window, fixed clicking on the icon after it is iconified
* Updated bloatware and suggestions
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.0...v4.0.1
🎉32👍15❤6🥰1
📣 February'25 Updates.
- I've received some interesting feedbacks in the opinion poll (the poll is still open). I'll try to address a few of those, but before that, you should know that sorting or filtering is difficult to implement without affecting the overall loading speed of the Main page. Those who have been using App Manager from the very beginning knows how long it took to load this page without the caching mechanism that was implemented much later. However, for certain cases, caching needs to be bypassed. For example, a list of running applications cannot be cached as it is a real time information. Same goes for the size checks. For those cases, when the filter/sort is triggers, App Manager takes a snapshot of the running apps/size and apply the selected option. This is why you may see increased loading time when you use those options. Also, as the number of sorting and filtering options are increasing, it's also necessary for a (not a complete) re-design of the list options to make it less overwhelming to a regular user. The reason for the poll to have limited voting options is also this. I want to understand which sorting options are most likely used by a user so that they can be more accessible than the others at the initial stage. It is also possible to update the options dynamically based on usage, but this will have a negative impact because when you use a feature regularly, you develop muscle memory. So, you may end up being annoyed with the dynamic options due to occasional changes in the layout. These are some of the trade-offs that needs to be considered when working on a complex feature that requires a simple front-end.
- Grouping apps on the Main page based on predefined groups is an interesting idea. But when you think about it analytically, you can find that groups cannot be overlapped, unlike say categories, tags, or profiles. So, it is necessary to research on how all these can be integrated. For example, groups can be just categories with where only one app is allowed across groups. Tags and categories are likely the same thing. Also, there may also be collections of tags or categories which can be just filters. In that regard, a single group/category/tag can also be regarded as a filter with just one item. These are some of the interesting concepts that require some deep thinking. Profiles is another topic.
- What is the biggest obstacle in publishing a new release? Writing changelogs. Though it may be surprising to many people, writing changelog often takes several hours to finish, because it's necessary to take a look at the features implemented, improved or fixed, and then write it in a way that makes some sense. Then, certain platforms requires a certain amount of work as well. For example, F-Droid has a restriction on the number of characters a changelog may contain which is way too limited for an active project like App Manager. For the in-app changelog, it's necessary that all the changes are documented properly since we expect people to read it most often. In other cases, such as GitHub, Telegram, Matrix, or website, it is expected that the users will just skim over the changes, but at the same time, they may be referred by other channels, forums, etc. So, they have to sufficiently denoscriptive but easy to read and understand. Finally, we also need to post the update via the social networks (Mastodon and X). Possibly developing a feature is less tiresome than this since they tend to be more rewarding and enjoyable.
- A few months ago, I talked about permissions in Android. App Manager currently does not have a permission model. This, as you may recall, is because Android itself has a very complex and distributed permission model. Unifying them is a challenge that App Manager needs to eventually address. My estimation is that such unification attempt may take at least 5-6 years if I do this alone (and I probably have to do this alone).
- I've received some interesting feedbacks in the opinion poll (the poll is still open). I'll try to address a few of those, but before that, you should know that sorting or filtering is difficult to implement without affecting the overall loading speed of the Main page. Those who have been using App Manager from the very beginning knows how long it took to load this page without the caching mechanism that was implemented much later. However, for certain cases, caching needs to be bypassed. For example, a list of running applications cannot be cached as it is a real time information. Same goes for the size checks. For those cases, when the filter/sort is triggers, App Manager takes a snapshot of the running apps/size and apply the selected option. This is why you may see increased loading time when you use those options. Also, as the number of sorting and filtering options are increasing, it's also necessary for a (not a complete) re-design of the list options to make it less overwhelming to a regular user. The reason for the poll to have limited voting options is also this. I want to understand which sorting options are most likely used by a user so that they can be more accessible than the others at the initial stage. It is also possible to update the options dynamically based on usage, but this will have a negative impact because when you use a feature regularly, you develop muscle memory. So, you may end up being annoyed with the dynamic options due to occasional changes in the layout. These are some of the trade-offs that needs to be considered when working on a complex feature that requires a simple front-end.
- Grouping apps on the Main page based on predefined groups is an interesting idea. But when you think about it analytically, you can find that groups cannot be overlapped, unlike say categories, tags, or profiles. So, it is necessary to research on how all these can be integrated. For example, groups can be just categories with where only one app is allowed across groups. Tags and categories are likely the same thing. Also, there may also be collections of tags or categories which can be just filters. In that regard, a single group/category/tag can also be regarded as a filter with just one item. These are some of the interesting concepts that require some deep thinking. Profiles is another topic.
- What is the biggest obstacle in publishing a new release? Writing changelogs. Though it may be surprising to many people, writing changelog often takes several hours to finish, because it's necessary to take a look at the features implemented, improved or fixed, and then write it in a way that makes some sense. Then, certain platforms requires a certain amount of work as well. For example, F-Droid has a restriction on the number of characters a changelog may contain which is way too limited for an active project like App Manager. For the in-app changelog, it's necessary that all the changes are documented properly since we expect people to read it most often. In other cases, such as GitHub, Telegram, Matrix, or website, it is expected that the users will just skim over the changes, but at the same time, they may be referred by other channels, forums, etc. So, they have to sufficiently denoscriptive but easy to read and understand. Finally, we also need to post the update via the social networks (Mastodon and X). Possibly developing a feature is less tiresome than this since they tend to be more rewarding and enjoyable.
- A few months ago, I talked about permissions in Android. App Manager currently does not have a permission model. This, as you may recall, is because Android itself has a very complex and distributed permission model. Unifying them is a challenge that App Manager needs to eventually address. My estimation is that such unification attempt may take at least 5-6 years if I do this alone (and I probably have to do this alone).
👍24🏆13🔥5❤2🥰1🤩1
App Manager | CHANNEL
📣 February'25 Updates. - I've received some interesting feedbacks in the opinion poll (the poll is still open). I'll try to address a few of those, but before that, you should know that sorting or filtering is difficult to implement without affecting the…
- My rooted phone broke down. I suspected it has something to do with the battery as it's no longer charging. As a result, development of root-only features and bug fixes are paused until I can find a solution. I can use an emulator, but they aren't convenient for testing certain aspects of root.
- We actually have everything necessary to implement ADB backup/restore for supported apps inside App Manager, only a user interface is necessary. However, the primary problem is the convenience, because whenever you run ADB backup, a popup will be displayed by the Android system asking for a password (which you should not set since encryption is handled by App Manager on its own) which can be very annoying. Then, the primary concept is to convert an ADB backup into regular App Manager backup and vice versa to allow restoring arbitrary backups made using App Manager which may not hold in all cases, especially the apps that only support key-value backup/restore. This is an interesting problem that I need to look into. ADB backup can also back up launcher widgets which App Manager cannot right now.
- The contributor of the month for February is Theray Tharow. Tharow was chosen for their outstanding code contribution to App Manager which include implementing the front- and back-end of the overlay management features. I hope more people will be interested in code contribution because this is where more contributions are needed.
- We actually have everything necessary to implement ADB backup/restore for supported apps inside App Manager, only a user interface is necessary. However, the primary problem is the convenience, because whenever you run ADB backup, a popup will be displayed by the Android system asking for a password (which you should not set since encryption is handled by App Manager on its own) which can be very annoying. Then, the primary concept is to convert an ADB backup into regular App Manager backup and vice versa to allow restoring arbitrary backups made using App Manager which may not hold in all cases, especially the apps that only support key-value backup/restore. This is an interesting problem that I need to look into. ADB backup can also back up launcher widgets which App Manager cannot right now.
- The contributor of the month for February is Theray Tharow. Tharow was chosen for their outstanding code contribution to App Manager which include implementing the front- and back-end of the overlay management features. I hope more people will be interested in code contribution because this is where more contributions are needed.
GitHub
Tharow - Overview
Tharow has 19 repositories available. Follow their code on GitHub.
🙏41👍31🤔3😢3🤩3🏆3❤2🥰1
📣 Announcement.
I've launched a new website to make it easy for Android users to discover, share, understand, and investigate pre-installed applications (AKA bloatware).
https://muntashirakon.github.io/android-debloat-list
You also have an option to open the App Info of an installed application from the website (which will work from v4.0.2).
I've launched a new website to make it easy for Android users to discover, share, understand, and investigate pre-installed applications (AKA bloatware).
https://muntashirakon.github.io/android-debloat-list
You also have an option to open the App Info of an installed application from the website (which will work from v4.0.2).
🔥88👍25🤩7⚡3🥰3👌3❤2🎉2💯2❤🔥1🥴1
#stable #release
App Manager v4.0.2
- Updated bloatware
- Fixed fetching applications in multi-user environment in no-root mode
- Fixed opening
- Fixed updating SSAID
- Prevented a crash in Android < 9.0 that occurs due to invalid app ops.
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.1...v4.0.2
App Manager v4.0.2
- Updated bloatware
- Fixed fetching applications in multi-user environment in no-root mode
- Fixed opening
app-manager URLs from the web browsers- Fixed updating SSAID
- Prevented a crash in Android < 9.0 that occurs due to invalid app ops.
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.1...v4.0.2
🔥33❤13👍12🥰2🤨2
📣 March'25 Updates
Eid Mubarak to those who celebrate Eid Al Fitr!
- Some of you are still sending email related to App Manager in the old email address. Those emails will be ignored, because those messages aren't filtered. Also, please try to add a sane subject line (e.g., App Manager Crash Report, etc.) to your email. Otherwise, they will also not be filtered. I received thousands of emails per month from various sources (not just App Manager). So, unless the subject line looks important, most of them are ignored and deleted after some time. Finally, please use a sane email address as well. If you use lots of `x`s, for example, most spam filters will put it in the Spam folder ;)
- I have been making plans to improve the ADL project (which more-or-less follows UAD-NG project for now). Hopefully, the project will be more reliable in the future with verified and enhanced documentation. Android libraries project, on the other hand, still requires a lot of work on my end which I may be able to finish by this year.
Eid Mubarak to those who celebrate Eid Al Fitr!
- Some of you are still sending email related to App Manager in the old email address. Those emails will be ignored, because those messages aren't filtered. Also, please try to add a sane subject line (e.g., App Manager Crash Report, etc.) to your email. Otherwise, they will also not be filtered. I received thousands of emails per month from various sources (not just App Manager). So, unless the subject line looks important, most of them are ignored and deleted after some time. Finally, please use a sane email address as well. If you use lots of `x`s, for example, most spam filters will put it in the Spam folder ;)
- I have been making plans to improve the ADL project (which more-or-less follows UAD-NG project for now). Hopefully, the project will be more reliable in the future with verified and enhanced documentation. Android libraries project, on the other hand, still requires a lot of work on my end which I may be able to finish by this year.
❤58👍18🔥6👌3🥰1🙏1🤝1💅1
App Manager | CHANNEL
Translation Updates. [previous update] I have reviewed and merged 47 commits out of 91 commits (51.65%) from Weblate. These translators were blocked due to abuse: - Adminslot69 - Valter Skot These translators didn’t ask for permission as per policy: -…
Translation updates.
I have reviewed and merged 133 commits out of 233 commits (57.08%) from Weblate.
These translators didn't ask for permission as per policy:
- Максим Горпиніч
- Vladik01-11
- translater 616
- Abdullah Almalki
- sebastian knudsen
- ODK
- cat
- Gilson Fabiano
- Apious (suspected machine translation)
- AronnaxM
- StarsShine
- pringless1d2cb378852a4a6a
- cyberboh
- ali-ee
- XblateX
- Rostyslav
- Andrea Ferrario
- Sarah B
- Andrea Ferrario
- Nader Jafari
- na7grn
- 안세훈
- Peter (out of context translations)
- Balázs Meskó
- Yurt Page
These translators also didn’t ask for permission, but their contributions were considered valuable:
- Domi Adiwijaya
Thanks Astoritin Ambrosius and 大王叫我来巡山 for your efforts in translating the docs in simplified Chinese!
Those who are new to App Manager translation community: You need to ask for permission before you can start translating App Manager. This is done to prevent abuse which have been increasingly common nowadays. Even if your request is accepted, your translations are always subjected to review, and your request may be denied any time if you fail to comply with the terms.
I have reviewed and merged 133 commits out of 233 commits (57.08%) from Weblate.
These translators didn't ask for permission as per policy:
- Максим Горпиніч
- Vladik01-11
- translater 616
- Abdullah Almalki
- sebastian knudsen
- ODK
- cat
- Gilson Fabiano
- Apious (suspected machine translation)
- AronnaxM
- StarsShine
- pringless1d2cb378852a4a6a
- cyberboh
- ali-ee
- XblateX
- Rostyslav
- Andrea Ferrario
- Sarah B
- Andrea Ferrario
- Nader Jafari
- na7grn
- 안세훈
- Peter (out of context translations)
- Balázs Meskó
- Yurt Page
These translators also didn’t ask for permission, but their contributions were considered valuable:
- Domi Adiwijaya
Thanks Astoritin Ambrosius and 大王叫我来巡山 for your efforts in translating the docs in simplified Chinese!
Those who are new to App Manager translation community: You need to ask for permission before you can start translating App Manager. This is done to prevent abuse which have been increasingly common nowadays. Even if your request is accepted, your translations are always subjected to review, and your request may be denied any time if you fail to comply with the terms.
👍50❤8🤩3🥰2
#stable #release
App Manager v4.0.3
- Updated translations
- Improved handling the list items throughout App Manager
- Fixed a regression error in file manager
- Fixed spinners in the App Usage and the System Config pages.
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.2...v4.0.3
App Manager v4.0.3
- Updated translations
- Improved handling the list items throughout App Manager
- Fixed a regression error in file manager
- Fixed spinners in the App Usage and the System Config pages.
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.2...v4.0.3
🥰28👍8❤🔥6👏4❤1🤔1🎉1👌1
📣 April'25 Updates
So, I've started teaching as a Teaching Assistant. It is a new and interesting experience after spending over a decade in software and open source development. Also, in a foreign language that I've never spoken until 2021 when I got my first job abroad. This is yet another bad news for you, however. Because I now need to spend time on preparing for lectures, taking classes, grading along with my regular research and course work. I think many users have already noticed the seemingly "unstable" nature of the stable releases. This is because we now release all the changes made to the repository (well, except a few experimental features) without going through any kind of testing that we used to do. (This, in a way, makes the debug releases more "stable" than the stable release since they may get immediate fixes than the stable which is released last Friday of each month provided there are things to release.) Unfortunately, I cannot do any thing about it right now. My life is currently in a very difficult position where work-life balance does not exist: all work and no life.
A good news, though, is that the small amount of time I can manage for App Manager is largely spent on improving the user experience. This you may have already noticed if you have installed the latest version of App Manager.
Now and then, I receive requests for adding translations for docs in [placeholder] language. Please understand that translating docs is a very difficult task, and we do not approve such requests unless the existing translations for the language are very good and are backed by at least two person.
So, I've started teaching as a Teaching Assistant. It is a new and interesting experience after spending over a decade in software and open source development. Also, in a foreign language that I've never spoken until 2021 when I got my first job abroad. This is yet another bad news for you, however. Because I now need to spend time on preparing for lectures, taking classes, grading along with my regular research and course work. I think many users have already noticed the seemingly "unstable" nature of the stable releases. This is because we now release all the changes made to the repository (well, except a few experimental features) without going through any kind of testing that we used to do. (This, in a way, makes the debug releases more "stable" than the stable release since they may get immediate fixes than the stable which is released last Friday of each month provided there are things to release.) Unfortunately, I cannot do any thing about it right now. My life is currently in a very difficult position where work-life balance does not exist: all work and no life.
A good news, though, is that the small amount of time I can manage for App Manager is largely spent on improving the user experience. This you may have already noticed if you have installed the latest version of App Manager.
Now and then, I receive requests for adding translations for docs in [placeholder] language. Please understand that translating docs is a very difficult task, and we do not approve such requests unless the existing translations for the language are very good and are backed by at least two person.
👍91❤44🫡18🆒5🔥4🎉2⚡1👎1🥰1🤔1🤣1
#stable #release
App Manager v4.0.4
Main page
- Optimize searching and filtering
Profile page
- Use the configured state to execute a profile for simple shortcuts
Others
- Use sentence case for all strings
- Prevent crashing while searching
- Fix integer overflow in tar compression.
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.2...v4.0.4
App Manager v4.0.4
Main page
- Optimize searching and filtering
Profile page
- Use the configured state to execute a profile for simple shortcuts
Others
- Use sentence case for all strings
- Prevent crashing while searching
- Fix integer overflow in tar compression.
Full Changelog: https://github.com/MuntashirAkon/AppManager/compare/v4.0.2...v4.0.4
🔥45❤19👍7❤🔥1
📣 May'25 Updates
It's been five years since I've started developing App Manager, and it's been an interesting experience. I've been part of a lot of communities before this, but Android community is probably the most diverse community so far. In Hackintosh community, for example, most people were highly technical, because you needed to know a lot about the hardware in order to build a hackintosh. It was particularly challenging for laptops since most of the hardware (e.g., PCI(e) devices) cannot be replaced unlike, say a desktop. With the introduction of Clover, and then OpenCore, the complexity has been greatly reduced, but it's still challenging to work with a laptop, especially with the newer graphics cards which aren't even support by the recent version of macOS (but some people are trying to find workaround). Anyway, the amount of dedication displayed by the hackintosh community is really impressive, and it's also a showcase of how resilient software engineers can be when they encounter challenges. Then there was also the Croissant project (which has been renamed to something else that I have forgotten about) where I have made some initial contributions, but Chrome OS itself is a dead end, and Google knows it very well. The experiences I've gathered from these two communities, in particular, have largely enhanced my ability to sustain an open source project. My inspiration for documentation, for example, is the OpenCore project.
App Manager v4.0.3 had a terrible bug that caused App Manager to crash or freeze (depending on device/OS) if certain keywords are used during searching/filtering. The issue has been addressed in v4.0.4. Interestingly, this has resulted in the creation of 29 duplicate issues (so far). This demonstrates how important it is to look for similar issues before opening a new issue, or GitHub suggesting similar issue based on the noscript or issue content while the user is creating a new issue (similar to what we already have in many other websites). GitHub also has a terrible search option that tends to ignore older issues.
Shizuku has recently altered its license terms to make the project completely open source (as opposed to source available that it previously was). I absolutely welcome this change and thank vvb2060 for making this change. Some of you may now ask whether I've got any plan on supporting Shizuku. Let me explain this a bit.
Since v4.0.0, much of the compatibility layers in App Manager have been rewritten to allow a certain level of flexibility in terms of the mode of operations. From v4.0.1, it is also possible to alter the mode of operation to any UID of your choice provided they support reading and executing the start command. It is even possible albeit with certain modifications to run App Manager as a system app with permission whitelists or as a system level UID (latter is too risky). So, in a way, it is now possible to add Shizuku support in App Manager. At this point, I may need to spend some time with their API to understand how it works. My expectation would be a generic API (similar to Open KeyChain's) that would allow connecting to any Shizuku-style applications, including any future Shizuku forks (since it is open source now) instead of Shizuku "official" app alone.
Lastly, Eid Mubarak to those who celebrate Eid-ul Adha.
It's been five years since I've started developing App Manager, and it's been an interesting experience. I've been part of a lot of communities before this, but Android community is probably the most diverse community so far. In Hackintosh community, for example, most people were highly technical, because you needed to know a lot about the hardware in order to build a hackintosh. It was particularly challenging for laptops since most of the hardware (e.g., PCI(e) devices) cannot be replaced unlike, say a desktop. With the introduction of Clover, and then OpenCore, the complexity has been greatly reduced, but it's still challenging to work with a laptop, especially with the newer graphics cards which aren't even support by the recent version of macOS (but some people are trying to find workaround). Anyway, the amount of dedication displayed by the hackintosh community is really impressive, and it's also a showcase of how resilient software engineers can be when they encounter challenges. Then there was also the Croissant project (which has been renamed to something else that I have forgotten about) where I have made some initial contributions, but Chrome OS itself is a dead end, and Google knows it very well. The experiences I've gathered from these two communities, in particular, have largely enhanced my ability to sustain an open source project. My inspiration for documentation, for example, is the OpenCore project.
App Manager v4.0.3 had a terrible bug that caused App Manager to crash or freeze (depending on device/OS) if certain keywords are used during searching/filtering. The issue has been addressed in v4.0.4. Interestingly, this has resulted in the creation of 29 duplicate issues (so far). This demonstrates how important it is to look for similar issues before opening a new issue, or GitHub suggesting similar issue based on the noscript or issue content while the user is creating a new issue (similar to what we already have in many other websites). GitHub also has a terrible search option that tends to ignore older issues.
Shizuku has recently altered its license terms to make the project completely open source (as opposed to source available that it previously was). I absolutely welcome this change and thank vvb2060 for making this change. Some of you may now ask whether I've got any plan on supporting Shizuku. Let me explain this a bit.
Since v4.0.0, much of the compatibility layers in App Manager have been rewritten to allow a certain level of flexibility in terms of the mode of operations. From v4.0.1, it is also possible to alter the mode of operation to any UID of your choice provided they support reading and executing the start command. It is even possible albeit with certain modifications to run App Manager as a system app with permission whitelists or as a system level UID (latter is too risky). So, in a way, it is now possible to add Shizuku support in App Manager. At this point, I may need to spend some time with their API to understand how it works. My expectation would be a generic API (similar to Open KeyChain's) that would allow connecting to any Shizuku-style applications, including any future Shizuku forks (since it is open source now) instead of Shizuku "official" app alone.
Lastly, Eid Mubarak to those who celebrate Eid-ul Adha.
🥰87❤49👍21🎉11🔥3👏3⚡2🤔1🤩1🏆1
App Manager | CHANNEL
Privacy Digest: February 2025. From now on, I will no longer report curated statistics on crash reports or missing signatures as nowadays, I receive a lot of general purpose emails than those. Also, instead of emails, I'll be using communications because…
Privacy Digest: June 2025.
Time Interval: July 2024 - December 2024
Total communications: 242
Total active communications: 93 (149 communications were deleted)
In order to improve community transparency, I'm also publishing blacklists present on GitHub and Weblate:
1. GitHub: https://gist.github.com/MuntashirAkon/60f3988a23e90f767edb2f747febf567
2. Weblate: https://gist.github.com/MuntashirAkon/e4288f015898a152ffa4479e7e8985c0
The gists above will be periodically updated with the latest changes.
PS: As always, any inquiries regarding App Manager sent to any other email addresses other than the official email address were discarded regardless of the contents.
Time Interval: July 2024 - December 2024
Total communications: 242
Total active communications: 93 (149 communications were deleted)
In order to improve community transparency, I'm also publishing blacklists present on GitHub and Weblate:
1. GitHub: https://gist.github.com/MuntashirAkon/60f3988a23e90f767edb2f747febf567
2. Weblate: https://gist.github.com/MuntashirAkon/e4288f015898a152ffa4479e7e8985c0
The gists above will be periodically updated with the latest changes.
PS: As always, any inquiries regarding App Manager sent to any other email addresses other than the official email address were discarded regardless of the contents.
👍38✍9❤7🎉2
📣 June'25 Updates
There hasn't been a release last month because there were no significant changes to the project that requires a new release. Last month, I along with IzzySoft have tried to make App Manager reproducible and has largely been successful. All the debug releases are now reproducible, and the stable releases too shall be reproducible from the next release (v4.0.5).
The highly anticipated "Finder" feature is nearing completion, and I think, I can launch it at the end of this month or the next. This feature required some thorough planning in order to make it future-proof and usable for most users (and much more usable for advanced users). Initially, only a handful of features will be enabled for the stable releases, and gradually all the anticipated features will be released. The reason for this kind of rolling release is because we no longer have the beta testing system that we used to have, yet a certain level of confidence is required in order to release a feature like this. Similar to profiles, the possibilities with this feature is endless, some of which may remain unknown for some time. There are also a few small but exciting improvements that are coming up (which shall be revealed in due time) in the upcoming releases.
Regarding the app store functionality, I've given it a thought and concluded that rolling out an entire app store is time consuming and largely unnecessary for the time being. Instead, we can launch an update functionality instead. The update functionality, unlike F-Droid or Obtainium, will adhere to the Android principles at the same time offering a level of privacy and security that will be suitable for a wide range of individuals (as always, in developing App Manager, I've always focused on offering a diversified threat model so that it can accommodate most users). You can find some information regarding the design at this link: https://github.com/MuntashirAkon/AppManager/issues/464. However, there are a few changes to the original design which will be revealed as I begin working on it.
That's all. Thanks for reading.
There hasn't been a release last month because there were no significant changes to the project that requires a new release. Last month, I along with IzzySoft have tried to make App Manager reproducible and has largely been successful. All the debug releases are now reproducible, and the stable releases too shall be reproducible from the next release (v4.0.5).
The highly anticipated "Finder" feature is nearing completion, and I think, I can launch it at the end of this month or the next. This feature required some thorough planning in order to make it future-proof and usable for most users (and much more usable for advanced users). Initially, only a handful of features will be enabled for the stable releases, and gradually all the anticipated features will be released. The reason for this kind of rolling release is because we no longer have the beta testing system that we used to have, yet a certain level of confidence is required in order to release a feature like this. Similar to profiles, the possibilities with this feature is endless, some of which may remain unknown for some time. There are also a few small but exciting improvements that are coming up (which shall be revealed in due time) in the upcoming releases.
Regarding the app store functionality, I've given it a thought and concluded that rolling out an entire app store is time consuming and largely unnecessary for the time being. Instead, we can launch an update functionality instead. The update functionality, unlike F-Droid or Obtainium, will adhere to the Android principles at the same time offering a level of privacy and security that will be suitable for a wide range of individuals (as always, in developing App Manager, I've always focused on offering a diversified threat model so that it can accommodate most users). You can find some information regarding the design at this link: https://github.com/MuntashirAkon/AppManager/issues/464. However, there are a few changes to the original design which will be revealed as I begin working on it.
That's all. Thanks for reading.
👍69❤30🔥20🎉5🥰2👏2🤯2❤🔥1⚡1👌1💔1