Just my little thoughts on Android…
Currently, I’m reading “Fragments” class document. I found out that it was pretty hard to follow, because the terminology Android developers ( not application developers, but the framework developers ) chose didn’t help to make it “self documented code”.
If someone insists me to compare how bad Android APIs are compared to Win32, I would say this.
When I put my hands on ToolBox API and Win32 API about 20+ years ago, I thought Win32 was designed very poorly compared to ToolBox.How bad Android is compared to Cocoa is much worse than how bad Win32 was compared to ToolBox.
Because Google people elected many not-sound-natural terminology and method / class names, it prevents from writing self-documented code.
Why haven’t Android app developers pointed those out?
Probably aren’t they interested in framework and API design itself? They are just busy to spit out Android apps?
Compared how it was about 20 years ago, it’s pretty hard to find any technical article on S/W architecture design for platforms popular in the market nowadays. ( Well.. nowadays tech. writing is done by journalists not S/W engineers… )
On April, 17, 2013, at AllThings D conference, MS head of Windows phone said,
“With Android … it’s kind of a mess,”
Well, he said iPhone is boring. But.. anyway I think he is right about Android. ( and I also agree with him about iPhone. )
Some people would say to Terry Myerson, the head of Windows phone, “Do your own business” or “How dare! Your Windows phone is not as successful as iPhone or Android phone!”.
But whether his Windows phone is successful or not, ( so thus whether he deserves to say that or not ) I think he pointed out the critical point of Android ( and iOS )
Nowadays S/W business is driven more by marketing and business, not by technology. So, whether a platform is bad or not, if it gathers some popularity in the market, people tend to rush into it.
I’m really sorry about it.