The value of your opinion

I have published apps and games for Microsoft Windows Phone, and I update them in a regular basis. Most of the time is because a bug is found, sometimes is a new feature or just because I am trying something new. It helps to keep things moving and people thank you for that.

However, I never had to protect an app or a game from human stupidity. Until now.

Software developers learn  over time how to deal with the final user - in some measure - and I must admit is not easy; as programmers we are not trained to deal with them, is usually another person's job. But when it comes to phone/tablet apps, that individual is you, because as an 'indie' developer you are too close to the complete production line.

I classify the users like this:

  1. The happy mute
  2. The unhappy mute
  3. The fan
  4. The hater
  5. The stupid

The mute ones...

There are always people that either like or don't like your app or website, or tool, but they just don't say anything. This is good and bad, you don't get bad reviews, but that implies you are not getting feedback that is always good. But the worst part is the that the ones that like your app, but are too lazy to upvote it or comment about it, they just don't help either. 

The fan and the hater...

The fans and haters are a necessary part of anything that exist in the planet, but when it comes to technology, they go to the extreme, however they are easy to spot and you can easily bash them, as most of the time they arguments are pointless. Of course, they can hurt you  a bit, mainly because haters are more effusive and active than fans... but hey, there is no such thing as bad publicity right? (or so they say)

Now... the stupid.

This is the kind of user that is impossible to please, and is quite common in the mobile app business. Any app that you find in the Microsoft Store, Apple Store or Google Play, has negative reviews that are written by this type of users. People that downloaded an app, did not read the instructions or have no idea what the app is for but they go and trash the app.

I have seen many cool apps being trashed by this type of pseudo-users, like a torrent download app, that is downvoted because it does not play a song, or downloading an app that does not provide services in the country where the user is located. Even an apps like Flipboard, downvoted by a user that is trying to use it in a hacked phone that barely works, or simply because the user's phone is crashing by itself or  has no space left and is behaving slow.

There are restrictions on what is possible on the phones as in any platform, that's why many apps explicitly say on the description something like:

1) this app can not delete photos from your phone
2) this app can not add videos to your phone
3) this app can not play videos or photos from your SD card
4) this app can not control the Mars Rover

and so on..

Whenever we - the developers - hit a limitation in a platform, we either find a workaround or describe the limitation to the user. If we take the time to do so, we should be able to expect something reciprocal from the users.

The value of your opinion

I think that everybody has the right to give an opinion (even haters), however I am strongly convinced that the value of such opinion has to be taken into consideration. On the internet, there is little room for that. Although many web sites allow people to rate what others say. 

On  websites like MSN you can downvote/upvote a comment on an article - that's a start -and you can also answer to those guys. 

On 'The Code Project' you can answer back and rate with a value (1-5) any answer or comment, you are also forced to justify any score from 1-3. And the system weights the points taken based on the voter's reputation points. The system is not perfect, because some users have a million points just for spending time posting on every forum and making jokes all day, and no points for writing an article or publishing something. But still, better than the model used on the app stores.

On Amazon, people can vote and comment on other's reviews. That seems fair. And I think is simplistic enough to be used on the app stores, and we should definitely move into that direction.

You must earn the value of your opinion.

 (maybe that's why I don't vote in the Oscars)

Comments

Post a Comment

Popular posts from this blog

Get-ChildItem vs Dir in PowerShell

Image
Batch as usual Recently I was in the need of modifying a huge amount of files across a network share. After installing Serviio media streaming service I noticed that it will crash "randomly". After checking the logs it was clear that ffmpeg was crashing when trying to open subtitle files that were not in the encoding indicated by the Serviio console. I needed a quick way to update all subtitle files to a common encoding, so I decided to convert all files to UTF8. Since I use a windows environment I went directly to PowerShell and wrote this.  Get-ChildItem -path .\ -filter *.srt -file  | ForEach-Object { (get-content $_.FullName) | Out-File $_.FullName -encoding utf8 } This worked almost right except for files with "[" or "]" (among other symbols) on the name or path. To solve it, just added the "-LiteralPath" switch to tell powershell not to consider any wildcards on the path name and just use it exactly as it is.  Get-ChildIt
Read more

The case for a 4 week sprint

Image
Every time we talk about SCRUM, the length of the sprint is stated as a period of "two to four weeks", rarely, however, have I seen people going outside of the 2 weeks. This is not written on stone of course, and while 3 weeks might seems odd, there is a benefit to using a longer period for your sprints.  Image is taken from scrum.org Without any hard data to back that decision, the answer I get from asking about this decision seems to be related to "delivery speed", we assume that because we deliver value to the business every 2 weeks, we are in a more "agile" environment. Well, that might not be so true in every sense or for every project. Let's break some arguments: 1. Sprint length is not equal to the speed of delivery There is more to the speed of development and delivery than the timeframe of the delivery cycle, in a world with DevOps and full CI/CD implemented for your project, you could (should?) actually deliver features every single day all t
Read more

NODE.js fs.readFile and the BOM marker

Working on a ReactJS project, got a small glitch while trying to read a JSON file and parse it as a javascript object. getDataObject() { var dataString = fs.readFileSync("./json/data.json", "utf8"); return JSON.parse(dataString); } output:   SyntaxError: Unexpected token   After checking, double and triple checking again that the file was correct I went deeper and realized that "fs.readFileSync" was returning me the BOM for the UTF file at the beginning of the string. So we just need to strip it out. getDataObject() { var dataString = fs.readFileSync("./json/data.json", "utf8"); return JSON.parse(dataString.replace(/^\uFEFF/, "")); } I then checked and there are "packages" for this, however I don't think is proper to just import a new dependency just to fix something this small. The big issue here is why is this considered correct. The BOM is not
Read more