Submitted:
08 May 2025
Posted:
09 May 2025
You are already at the latest version
Abstract
Keywords:
Introduction
- A.
- Access a complete, organized list of all installed applications,
- B.
- View essential details like permissions granted and installation dates,
- C.
- Instantly allow or deny data access through a toggle mechanism,
- D.
- Receive timely notifications about potentially intrusive permission requests,
- E.
- Analyze historical patterns of app usage and permission activity.
Literature Survey
- A.
- A centralized dashboard for app overview
- B.
- Toggle-based permission control
- C.
- Real-time alerts
- D.
- Usage analytics
- E.
- A non-rooted, system-friendly design
Proposed Work
- A.
- Objective
- B.
- FunctionalOverview
-
- a)
- Application Listing: Automatically fetch and display all the installed apps on the device.
- b)
- Permission View: Show the current permissions granted to each app, such as access to storage, camera, or internet.
- c)
- Toggle Control: Provide a toggle switch next to each app that enables or disables data access permissions as per user preference.
- d)
- Minimal Alerts: Notify users if an application seems to be requesting excessive or unnecessary permissions (in future versions).
- e)
- Clean Interface: Keep the user interface minimal and user-friendly to ensure its accessible even to less tech-savvy users.
- C.
- SystemArchitecture
-
- a)
- App Fetcher: Retrieves a list of all installed applications.
- b)
- Permissions Viewer: Gathers and displays all the permissions used by each app.
- c)
- Toggle Handler: Implements logic to enable or disable data access using the toggle.
- d)
- UI Renderer: Displays all the information in a simple and responsive layout.
Methodology
- A.
- Overview
-
- a)
- App Fetcher
- b)
- Permissions Viewer
- c)
- Toggle Handler
- d)
- User Interface Layer
- B.
-
Functional Components
- a)
-
App Fetcher: This module is responsible for:
- Scanning the user’s device to fetch a list of installed applications
- Extracting basic metadata: app name, icon, and package name
- It uses platform-specific APIs (e.g., package_info_plus in Flutter) to fetch this data.
- b)
-
Permissions Viewer: This component:
- Displays the current permissions granted to each application
- Lists commonly accessed permissions like storage, camera, contacts, and location
- Presents this data in a simple, readable list format
- c)
-
Toggle Handler: This is the core interaction layer that:
- Shows a toggle switch for each application
- Simulates permission control by storing toggle states in the local database (as actual runtime permission changes are not handled due to system limitations)
- Provides a sense of control to users by helping them track what access they intend to allow or block
- d)
-
User Interface: The app’s interface is:
- Built with Flutter widgets
- Lightweight and mobile-friendly
- Divided into screens like: Home screen with the list of apps, Toggle screen per app, Permission summary screen
- e)
-
Simplified Data Flow[Launch App]↓[App Fetcher → Gets Installed Apps]↓[Permissions Viewer → Lists App Permissions]↓[Toggle Handler → Saves Toggle State]↓[UI → Displays Changes to User]
- f)
-
Design Principles
- Minimalistic UI: Prioritizes clarity over complexity
- No Root Access: Operates within standard system permissions
- Local Storage Only: All toggle states are saved locally using shared preferences or SQLite
Results
- A.
- Yes – I would definitely use such an app.
- B.
- No – I do not need such an app.
- C.
- It’s Okay – I might use it, but it’s not essential.
- A.
- 65% of users responded with Yes.
- B.
- 15% responded with No.
- C.
- 20% responded with It’s Okay.
- A.
- Working professionals formed the majority of the Yes respondents, indicating their concern for privacy and work-related app control.
- B.
- Students also showed good interest, especially due to increasing awareness about data misuse.
- C.
- Retired individuals, while forming the smallest group, still showed some interest, although many responded with It’s Okay due to limited mobile app usage.
-
A pie chart displaying the percentage of total responses for Yes, No, and It’s Okay.

-
A bar graph comparing the responses across different demographics.

Discussion
Conclusions and Future Work
- A.
- Real Permission Control: In future versions, the app can directly control app permissions using system-level features, rather than just showing information.
- B.
- Improved Alerts: The app can be enhanced to send real-time notifications when any app accesses sensitive data or requests new permissions.
- C.
- User Tips and Suggestions: Future updates can include tips or recommendations based on permission usage, helping users make better decisions.
- D.
- Support for More Devices: The app can be made compatible with a wider range of devices and operating systems.
- E.
- Simple Analytics: A basic report feature showing which apps use the most permissions can be added to help users understand their app behaviors better.
References
- Ravichandran, A.; Ramesh, N.; Harini, M. AppLock: Permission Control and Privacy Protection in Android Applications. International Journal of Computer Applications 2014, 98, 12–18. [Google Scholar]
- Grace, M.; Zhou, Y.; Zhang, Q.; Zou, S.; Jiang, X. RiskRanker: Scalable and Accurate Zero-day Android Malware Detection. in Proceedings of the 10th International Conference on Mobile Systems, Applications, and Services (MobiSys), 2012, pp. 281–294.
- Google Play Protect. (n.d.). Google. [Online]. Available: https://www.google.com/android/play-protect/.
- Wijesekera, D.; Baokar, A.; Jia, L.; Nadkarni, A.; Egelman, S. Android Permissions Remystified: A Field Study on Contextual Integrity. in 24th USENIX Security Symposium, 2015, pp. 499–514.
- Zhou, L.; Zhou, B.; Chen, Y. Mobile Application Privacy Protection: A Survey. IEEE Access 2019, 7, 50548–50563. [Google Scholar]
- Zhang, X.; Luo, X.; Yang, H. PermissionWatcher: An Efficient Permission Monitoring System for Android. Journal of Information Security and Applications 2020, 54. [Google Scholar]
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2025 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (http://creativecommons.org/licenses/by/4.0/).