If you were starting from scratch and wanted to make a very privacy / security focused system, it may be a very good idea to do away with persistent permissions and to require user consent as needed. Android has most of those options, but apps prefer getting a permission once.
-
-
Yeah, it's really hard to implement some parts of it like the computer vision parts with OCR, detection of different object types, etc. The easy parts are either stubbing out actual server-based services or making real clients to them like microG does for GCM, etc.
-
Also there's the VR / AR stuff now and maybe that will end up being important to people in the future. A large amount of that is open source in AOSP but there's a lot of fancy stuff that isn't. Maybe AR will become a killer feature for people, who knows.
-
We think of a lot of the research / work that we do as simply figuring out how to do things properly for some saner future system... but app layer is probably going to be needed in practice for a long time to use existing apps. Fancy new microkernel is easy vs. new app ecosystem.
-
I don't think ux for integrating legacy apps is that hard. When installing give user simple control (2-3 choices) for "do you want it to integrate with other apps?"
-
For most apps the answer is just "no, not at all" and then you run it in a complete sandbox that looks like a fresh Android install with just one app.
-
Having isolated profiles/workspaces can work well for that, which is something Android has today and just doesn't make convenient enough for it to be widely used for more than multi-user and work profiles.
-
People can just install the app in the profile where they want to run it, and as long as profiles are easy enough to use it should work well. Too inconvenient right now for most people / use cases.
-
Apps can't communicate / share data across profiles unless they do it via the network, etc. It could be reinforced with a VM instead of just being on top of the same Linux kernel with SELinux (MLS is used as an extra layer for multi-user) + seccomp-bpf.
- 7 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.