this post was submitted on 31 Aug 2025
1399 points (98.7% liked)
Technology
74692 readers
2756 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How does this affect "second-party" apps (i.e. apps you have created yourself)? Are you still allowed to go to Android studio, make an APK, transfer it to your own phone, and install that app? If no, this spells the death of experimental indie developers on Android.
yes. from what I understand, you will get a developer key from Google, and then you will sign your APK with your key.
you'll still be able to sideload apps that have been signed with developer keys. the main point here is that Google is forcing the developer to identify themselves.
You don't need to sign anything just turn off play protect with 1 adb command:
Not a solution to our problem, but this is a crumb in our favor.
I know why you included both, but saying "1 adb command" and then posting two is funny to me.
One gets the current value to verify it and another actually sets a new value. It's the way these commands are usually shared.
Does this work with any app or just second party ones? Can you re-enable it?
Yes it modifies the phone not the app and you can re-enable it anytime with 1 instead of -1