Skip to main content

Google Is Removing Ad-Blocking Apps in its Play Store - The Good and The Ugly.

Google  has started cleaning up their Play Store for ad-blocking applications.  This is an expected behavior from a company that earns from advertisements and commercials. Those affected by the "great purge" was properly informed through a letter similar to the one below.

This is a notification that your application, [Application name and package goes here], has been removed from the Google Play Store.
REASON FOR REMOVAL: Violation of section 4.4 of the Developer Distribution Agreement. 
After a regular review we have determined that your app interferes with or accesses another service or product in an unauthorized manner. This violates the provision of your agreement with Google referred to above. 
All violations are tracked. Serious or repeated violations of any nature will result in the termination of your developer account, and investigation and possible termination of related Google accounts. If your account is terminated, payments will cease and Google may recover the proceeds of any past sales and/or the cost of any associated fees (such as chargebacks and transaction fees) from you. 
If your developer account is still in good standing, you may revise and upload a new instance of the application that is compliant with the developer terms. Before uploading any new applications, please review the Developer Distribution Agreement and Content Policy. 
If you feel we have made this determination in error, you can visit this Google Play Help Center article for additional information regarding this removal. 
The Google Play Team
Section 4.4 of the Developer Distribution Agreement states that :
You agree that you will not engage in any activity with the Market, including the development or distribution of Products, that interferes with, disrupts, damages, or accesses in an unauthorized manner the devices, servers, networks, or other properties or services of any third party including, but not limited to, Android users, Google or any mobile network operator. You may not use customer information obtained from the Market to sell or distribute Products outside of the Market.

The Good

This is good news for developers who rely on ads for their craft to cash in some money. With the removal of ad-blocking apps, the possibility of earning more from ads is a good thing. If we will assume that this added revenue will motivate the developers more to create a more intuitive  and better designed app, then, this will be a plus to the users in the long run.

The Ugly

Need I say more? All users who despise this ads will be more furious. They will no longer find ad-blocking  tools in the official Google Play Store. However, they can still side load these apps using APKs' downloaded from the wild ( which is not 100% malware free). Which leads us to the developers specializing on ad-blocking technology, they will resort to other venues for selling their apps and that can be too risky.

I don't have any issues with Google on this move. Its their store and they have the right to implement rules which they think would make it better.  What worry me most is the fact that this move may release the evil of advertising even more to the smartphone users, particularly, us android users. But for now I am leaning towards the optimistic view that this move will bolster the desire of developers to innovate and be more creative knowing that they have now a better chance of earning.   How about you?


Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :


renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!

I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …