Skip to main content

Should I Pay for an App?

Image Source;
Should software developers or anyone working on similar fields pay for the "Apps" they use? Legally speaking, if the software is for a price, anyone who intends to use it must buy the software. Of course we all know this is never a common reality. I will not go into discussing  corporate  non sense and go into details of complicated licensing schemes being offered by , often times, greedy software companies. Let's focus into what they call,  the "Apps". These  simple yet entertaining and(sometimes)  useful software has kicked off to become a worldwide commodity, thanks to the ever expanding smart phone industry. Unlike big productivity suites offered by large money-sucking companies, most of these "apps" are startups trying to make a name in the industry. Of course we know some who went on and hit big time with a highly addictive app. Others were eventually bought by bigger companies. That's the idea of a food chain after all.  But then again, these are applications made perhaps on someone elses basement or a shitty small office by developers trying to earn some cash by doing what they do best. In reality, they are us, they work like us, they live like us, typical software developers. Like us, they deserve to be paid as well.

I dont mind spending a few dimes and nickels for a useful app. I have done it in iTunes before, buying a $15 iTunes gift card just to buy a $2.99 guitar app. Then, I went on buying some til I bolted out of iTunes and left a $7.99 fortune waitng to be spent. I also bought a few in the Play Store. I must admit, however, that I have not bought anything above 5$ mark. Sygic, is really tempting I must admit:-)
Going back to the question, I think out of respect to other software developers, we should pay for the apps that we think we need. That is why our clients continue to pay for the services and product we provide them, because the payment is due to us. The emergence of mobile applications has opened  the doors to a lot of developers. Mind you, most of these applications in the market don't earn that much. We can not blame them for the ugly advertisements that come with their masterpiece, especially if that is the only way they will cash in some money. So if the vast amount of free apps can't satisfy your need and only a paid app will do, be kind enough and pay. Just don't forget to evaluate first before buying.


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, …