This is very interesting article.
Android fragmentation predicted to squeeze out independent developers
Well, I’m currently working on an iOS program, which was originally implemented by some people in an outsource company. One major problem is that they didn’t understand the philosophy of Cocoa framework and Objecitve-C. So, there are maany wrongly written piece of code as well as wrong memory management, wrong view management, etc.
So, to fix some problems asked is very irritating because I have to fix those things hidden to end users as well as visible problems to people here at….
Then, unnecessary “fragmentation” occurs even on this beautiful and clean iOS platform. Often, I have to work around the wrongly written code, because people in my company didn’t understand why it coudl take longer time than they expect, because to them, the “surface” problems look small. For better management of projects, I fix fundamental problems in architecture, coding etc if that is to give me hard time. ( to work around studid code is not feasable sometimes. ) Anyway, because I have to find a way to work around some problems which are better not to solve at this moment, there must be some code which can be odd.
Then, if a platform has its inheretant fragmentation, how much headache it can give?
So, I don’t expect Android developers test their projects on every Android platform. They would choose only the major devices they think. The “circle” of the major devices can be different among people. So, Google found out that they needed “reference devices”, but they don’t look to be consistent for themselves.
So.. yes.. I expected this kind of news, which says that fragmentation expel indepedent developers. Actually it’s not only those small developers who are affected by the problem. In companies, where they have S/W dept. managers who don’t understand S/W development, would raise question to his/her S/W engineers request to buy more Android devices to test for. Then, the frustrated developers would just give up testing on more major devices, they would say, “Ok. Nowadays Sammy Galaxy 3 is hot. So, it’s OK if my program runs on it Ok.”. This will cause them to miss non-negligiby large target audiences.
However, thanks to the success of iPhone, native programming is still strong.
Yeah… probably, Goole wants people to be frustrated by the fragmentation of Android. Many people will think that even iOS has that fragmentation and would not try at all.
It makes sens from one point of view, but not at all from different angle.
I hate it.