Comment by hn92726819
10 days ago
One interesting aspect of this is that when using a personal Android with a work profile, developer options and ADB is (or at least can be) disabled. BYOD will then imply you can't sideload at all.
10 days ago
One interesting aspect of this is that when using a personal Android with a work profile, developer options and ADB is (or at least can be) disabled. BYOD will then imply you can't sideload at all.
And nothing of value was lost. BYOD means Corporate can push whatever spyware they want onto your personal phone. I tell any employer I work for, if you really need me to be reachable by phone via an app, you can supply me a work phone. Otherwise I'll do without. I keep a bright-line distinction between personal devices and work devices, and never mix the two. My boss knows this explicitly.
That's great for you, but not everyone has the ability to do that. Android has a massive markershare. What are the odds that all of them can force their employer to get them a new phone?
Maybe that's something employers shouldn't do, but that doesn't change the fact that it's a reality and google is overstepping with this change.
Please. This is an event up there with Sony taking Other OS away: tinkering nerds and pirates most affected, the vast majority of consumers won't even notice. I don't think it reaches that level of impact. And I think most Android devs working professionally already have developer accounts, or their employers have one, and are already verified.
That's what this really is about. If you want to distribute Android apps, be a professional or at least act like one. Take accountability for what you produce, under your real government name.