Developer-friendly guide to the Google "associated account ban" - advice to an iOS developer thinking about Android (misconceptions and alternatives for developers) Android Dev |
- Developer-friendly guide to the Google "associated account ban" - advice to an iOS developer thinking about Android (misconceptions and alternatives for developers)
- Admob Ad Placement Policy
- Programmatically dismiss ACTION_VIEW dialog once installation is complete
- iOS Developer looking for a reliable Android developer to join my company on contract basis
- How to Implement Text To Speech in Android Studio
- What is the best way to transfer big bitmap between two activities?
- How To Become A Software Developer in 2020
- Having a problem with WebView
- Most reliable Places API?
- my app Yula doesn't show up in google play search
Posted: 08 Dec 2019 09:11 AM PST I received a query from an iOS developer thinking about developing for Android - and his concerns about the notorious "associated account ban" practice (by Google). Since the exchange may be of wider use to new developers thinking about Android, I am providing it here - my reply and the comments others may post here should dispel some of the misconceptions about:
NOTE: I asked for permission from the iOS developer - which he granted - so that I could include his quoted text.
iOS developer's response:
Asked for permission to use his quotes:
FAQ - App Bans and Account Bans
When does a lifetime account ban occur ? A Google Play account ban can occur due to an "associated account ban" - when Google thinks you are associated with someone else, and that someone else was awarded a lifetime account ban. That person's ban percolates to his associated accounts - i.e. you. Thus if you become lifetime account banned by Google - you become a threat to your acquaintances, and to your company (and should not be put in charge of their Google Play account once you are lifetime account banned). If you are not associated with anyone by Google - then your lifetime account ban will occur usually due to an accumulation of app bans. A Google Play developer account ban IS a lifetime ban.
How many app bans are required to achieve a lifetime account ban ? The conventional wisdom some time ago was that 3 app bans were usually what triggered a lifetime account ban. But from anecdotal evidence from developers on androiddev, we now know:
As with most Google "rules" which suffer from the info asymmetry that makes for a "moral hazard" in Google vs partner dealings (app dev/Adsense/YouTubers):
Other observations about app bans and account bans
Can a developer remove an app if he fears it's future ban may imperil his account ? (similarities to slave labor) Google does not provide a way for an app developer to remove his app from Google Play. A dev can only delete his app from Google Play IF it has been downloaded by zero users. A dev CAN "unpublish" his app (from Pricing & Distribution section), however the app remains visible to existing users, and users who have paid for the app. However apps you "unpublish" remain liable to app ban - for example an app that is no longer being updated by a developer can fall out of compliance with new rules which Google introduces each year (for example Google no longer honors it's "old apps will always work on newer android versions" compact - every year now apps have to comply with new targetSdkVersion requirements - which means older apps will break and eventually fall out of compliance at a steady pace). Devs do occasionally neglect their apps (they may be a hobbyist, a scientists, or simply is swamped by new projects, or the old app may no longer be profitable for them to maintain). However such developers may find that Google is forcing them to update their apps which they have no incentive to update any more. Google uses the threat of a lifetime account ban to COMPEL these developers to keep updating their apps (even when devs want not to do so). This is a type of compulsion - reminiscent of slave labor - where work is demanded without promise of compensation, or advantage to the worker. Essentially a developer once published on Google Play, faces the prospect of lifetime obligation to Google. This is odd, given that Google has in the past portrayed itself as an intermediary between the developer and the user, and not as the actual seller of the app - if so it seems odd that Google feels responsible for enforcing a relationship between developer and user. Perhaps Google now does act as actual seller/provider of apps - given that it now also collects taxes directly for more territories (?) Recently there was a comment by a Googler (which was also carried by androidpolice) that unpublishing an app will not expose an app to app ban, but that such apps will eventually be "Removed" (as in our app above - see second link at top - ie Removed apps don't put account standing at risk). The androidpolice artice was based on the comment, while the Google commenter was himself at odds with Google docs and said he will get back with others at Google about the discrepancy: Here is the original reddit comment that whole androidpolice article is using as source:
What is an "associated account ban" ? Google's practice of lifetime bans for android developers - bans which percolate from acquaintance to acquaintance. In all likelihood a wife would face an immediate ban if her husband has already been banned - this association would survive divorce:
An lifetime account ban thus risks making a pariah out of a dev as any potential employer may fear tainting their company account and the accompanying hassle if they hire a tainted developer. Thus the early crimes of a dev could become a lifelong "Scarlet Letter".
Why is the Google appeal process flawed ? Android developers, once banned, are banned for life - and the only reliable way to get account reinstated is for developer to blog post on medium dot com and achieve virality. Then somehow Google is convinced that the developer's issue has been vetted (for free by the public!) and often restores the account. Even for restored accounts, developers often report that they never found out what led to the account ban in the first place. Essentially no human at Google can countermand a Google bot's decision - probably because it is a neural net or uses fuzzy rules to decide - which means it is not explainable in human terms. Google also uses secrecy argument - they need secrecy about why they did something to avoid being "gamed" - i.e. they are afraid their automated processes, once known would be easily exploited - as a loophole in an automated system could be used repeatedly, possibly without detection by Google. Google uses this secrecy argument for Adsense and it's other services as well - where Google partners can be banned without them knowing exactly why that happened. This developer has created a whole website to document the misbehavior of Google regarding his AdSense account: As with most Google "rules" which suffer from the info asymmetry that makes for a "moral hazard" in Google vs partner dealings (app dev/Adsense/YouTubers):
Can a lifetime account ban (developer) lead to a GENERAL Google account ban (Google Photos etc.) ? Lifetime account bans generally DO NOT lead to a ban on your Google account (i.e. will not affect your Google Photos etc.) - however, there have been cases with YouTube account bans which DID affect ALL the Google account content (including Google Photos): Markiplier's video asking Google that his followers's services still not restored: Androiddev post:
Threats to hobbyist devs and open source developers Right now the old advice to new devs to publish early with their test apps, and to do it with abandon is totally the wrong advice now. Generations of android tutorials are hopelessly out of tune with that old advice. The current conventional wisdom is to publish carefully, and sparingly with apps which can be supported by the new dev. If dev cannot commit to that, they should not post their hobbyists apps to Google Play. This is sound advice to the new hobbyist dev, and to the budding independent dev - if they value their lifetime cred with Google. It may surprise you but now even open source app developers are under threat - the other developers who copy and publish with their code are rendering the original app under threat.
[link] [comments] | ||
Posted: 08 Dec 2019 08:17 AM PST Hi everyone! There is something that confuses everyone. Everyone I ask answers differently. And this topic is not explicitly stated in Google policies.
(Scrollview into the *different IDs* with 4-5 banner ads can I add?)
Note: All questions apply to Google Admob Thanks in advance! [link] [comments] | ||
Programmatically dismiss ACTION_VIEW dialog once installation is complete Posted: 08 Dec 2019 11:33 AM PST
| ||
iOS Developer looking for a reliable Android developer to join my company on contract basis Posted: 08 Dec 2019 09:31 AM PST I'm an iOS developer, with a various jobs in the pipeline which require an Android version built as well as the iOS version. I'm looking for a reliable Android developer preferably in Europe to support me with the work I secure by managing the Android side of things. I have two lucrative jobs in negotiation which I'd look to you to lead on the Android side. If all goes well, we could collaborate longer term by sharing jobs equally. Let me know if you interested, and I can share a profile of my work so you can see the standard I'm expecting - and you can share yours. [link] [comments] | ||
How to Implement Text To Speech in Android Studio Posted: 08 Dec 2019 12:00 AM PST
| ||
What is the best way to transfer big bitmap between two activities? Posted: 08 Dec 2019 02:33 PM PST | ||
How To Become A Software Developer in 2020 Posted: 08 Dec 2019 01:23 PM PST
| ||
Posted: 08 Dec 2019 11:51 AM PST I am using WebView to display PDF files, the problem is that once you press the back button on the phone, and then try to go back into the WebView it will not load the pdf, it will just load a white blank page. I tried adding "webView.Destroy()" in the OnDestroyView(), but that didn't help. Any idea how I can fix this? I get this in the log: W/chromium: [WARNING:spdy_session.cc(3097)] Received HEADERS for invalid stream 7 W/chromium: [WARNING:spdy_session.cc(3097)] Received HEADERS for invalid stream 11 W/chromium: [WARNING:spdy_session.cc(3097)] Received HEADERS for invalid stream 13 W/chromium: [WARNING:spdy_session.cc(3097)] Received HEADERS for invalid stream 15 W/chromium: [WARNING:spdy_session.cc(3097)] Received HEADERS for invalid stream 17 W/chromium: [WARNING:spdy_session.cc(3097)] Received HEADERS for invalid stream 19 [link] [comments] | ||
Posted: 07 Dec 2019 04:03 PM PST My app requires finding POIs nearby the user (based on their lat/lon). I've tried both Mapbox Reverse Geocoding and TomTom Nearby Search and the POIs are unreliable - for example they show restaurants that closed 2 years ago. Google Places is too expensive for me - I'm looking at Foursquare so am curious if anyone has used that for nearby locations to the user - or any other API? [link] [comments] | ||
my app Yula doesn't show up in google play search Posted: 08 Dec 2019 03:20 AM PST It's been 3-4 days since I uploaded it to google play.but when I still search Yula => https://play.google.com/store/apps/details?id=ewy.studio.yula ,my application does not appear anywhere.this is a bit annoying.I mailed and learned that many people like me are sending mail However, the answer I get is to make the app name unique and use google ads.The application step is already unique and I learned from here that google ads do not have a benefit to the index. What should we do ? We are already working hard enough to write and design the code of these applications.but they won't let us when we want to finish and publish everything and they're gonna take it from us for $ 25 for nothing.when we mail them to solve this problem, they will make fun of us and suggest things that will not work.If there is a game store due to our applications, we are the ones who keep it alive.but they still don't respect us and listen to us.they have to listen to us and show respect.Because if they set up a game store, it's because of us. We must make our voices heard. [link] [comments] |
You are subscribed to email updates from Developing Android Apps. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States |
No comments:
Post a Comment