I completely agree with you, my app functionality should be built inside the OS because of better integration, privacy reasons, etc.
I just wanted to add that because of this permissions my app needs in order to work, I will never add the internet permission to Quick Cursor. I took this decission 5 years ago when I started the app because I understood the privacy risk, and my app will never have internet access permission.
In order for an app to have access to internet, it needs to have the android.permission.INTERNET added to its manifest, otherwise it won't work. This can be checked easily, there are some apps that shows you this info about your installed apps, or by manually looking at the AndroidManifest in the .APK of the app.
I am using GrapheneOS, and I think this OS actually also allows you to explicitly toggle the Network permission off for apps that require it, but I did notice that it wasn't even present on the list to begin with :). I also like to disable Network for things like keyboard apps.
I completely agree. Just imagine how good this can be implemented at system level. I had to do a lot of "hacks" to make it work that good as a simple accessibility app.
I've got feedback from multiple users with disabilities that this app is helping them use their phone easier with one hand. It also helps users without disabilities like me, I use it every day and I can't use an Android phone without it anymore.
I would love to see something like this implemented in both iOS and Android by Apple and Google.
I appreciate you applied all those hacks to make it work though! Even though I do not have any disabilities I will definitely be using this. I do have an Android tablet and it will definitely be useful on that size!
Hopefully it gets picked up by both of them and they hire you to make it without any hacks :)
I also created an interactive tile based on my vanilla-tilt.js library for my app: https://webtiles.kicya.net/#625,3875