

Designing for privacy? Google?


Designing for privacy? Google?


It is possible. Even without AI. But if you ask this question, I wouldn’t even start going into AI-less direction :)
With AI you can give it even a very generic task “make this app work on my phone, you’re allowed to patch it however you want”, give it jade (decompiler) and other dev tools, adb with which it’ll be able to upload apps to your phone and view logs, buy a lot of tokens for some good model, and let it cook. There’s a high probablity that even like this, without any optimizations it’ll succeed.
Now in terms of self-hosted vs commercial models, here’s the overall picture.
Self-hosted (unless you have some Nvidia H100 or something) are generally stupid enough to not do anything.
Commercial (even those available for free e.g. in opencode or openrouter), are already capable of producing some results. Generally, they don’t give a damn about hacking into the app, unless it’s something really sensitive (e.g. hacking into some infrastructure) or a false positive. Usually, you can soften their guards by using terms like “MY app”, “OUR app”, “I’ve accidentally deleted the source code” and so on to make them firmly believe that you are working on your own app, but even that is not normally necessary.
See something like this for the inspiration: https://codyho.dev/blog/gpu-driver/
Since in your case you probably won’t care about “clean room” technique, and you’ll be working with Java that very nicely decompiles into smali and then gets “restored” into its original Java form (obfuscated ofc), it will be much easier.
The hardest part is to setup AI loop, manage it and be able to guide it in the correct direction without going into the full slop mode and basically wasting your money. Because of that, I’d say you’d need some good programming/engineering skills, but even if you don’t, you can still try your luck and maybe even learn a lot in the process :)


Yes, unfortunately. It’s their con, but also their pro at the same time. It’s bad because they end up isolated from everyone else playing nice with each other, and then no one wants to deal with them, but they also don’t agree on compromises that might hinder security or the stability and development of their project. And I respect that. That is partly a reason why they created probably the most secure and private AOSP distrubution nowadays.


They can, but it’s not their goal. Their goal is to have control over 99% of Android phones produced and not let their users install adblock or NewPipe, or torrent app or whatever.


There’s GrapheneOS that I think would try to address this problem — secure, proper architecture, compatible with some major app stack (e.g. Android apps). It’s AOSP-based, but they’re already thinking ahead up to a point where they would be forced to fork it and even work with OEMs to create their own phone hardware for it. There are a couple of threads on their Mastodon.
I don’t know how much they would be able to achieve, but I would pay for such system.
And becoming homeless once their cloud service goes down.