That's true but by the same logic the Mac is a Free BSD device. That's a technically correct description but in terms of understanding the market it's not that useful.
The issue with the Fire is that it's forked, that there may be future compatibility issues, that it will never officially become an ICS device and that those things may hold Android back in may ways (for instance app developers always having to work to a low baseline to access the Fire users as a potential market).
So yes it's an Android tablet but it's one that may be a mixed blessing for Android and deserves some subtlety in the distinction.
It remains to be seen, but I think Amazon will shoot itself in the foot if they won't keep up with the latest versions, simply because some developers will ignore the Kindle Fire because of this (while some will do as you say).
I'm seeing this "fork" more like that of Debian and Ubuntu: different software bundled by default, different repository, different philosophies and policies, different management, overlapping user-base, but for practical purposes, they aren't that different.
One breakdown I saw suggested that of the 39%, 24% was Kindle and Nook (that's an absolute 24%, not 24% of the 39%). That's a massive percentage of the market to ignore as a developer.
That was for tablets, right? I'm not surprised considering how shitty the Android tablets have been.
But developers are targeting the phones first, tablets second, because a phone is always in your pocket, always online and everybody needs a phone. In December Google reported 700,000 activations per day. In 2010 alone there were 67 millions of Android devices sold, with the total number of mobile phones sold being measured in the hundreds of millions.
So Kindle Fire does great as far as tablets go, but it can't compete in numbers with Android phones and Android phones are targeted first, unless you're talking about stuff like interactive eBooks that really need the bigger screen.
I'm also seeing this happening on iPhones and iPads. Unless an app really needs the bigger screen, then the iPad is a second class citizen to the iPhone.
That's a good point about phones leading the way. I'm guessing that in large part that's because the number of phones (iPhones and Android) dwarfs the number of tablets. I'm always slightly surprised at the number of apps that don't work well on the iPad but it makes sense that you wouldn't put your energy there, at least not in the first instance.
But for those applications that do want to develop a tablet app, it's still a big call to exclude the single biggest selling Android tablet out there (which is probably the Fire).
While it is possible, given that Google has released ICS, I'd be very surprised if the Kindle Fire didn't get ICS in an update the same way the Nook Color got Froyo and Gingerbread in updates. Why?
1. Amazon and B&N are in a dogfight over eBooks, eReaders and (now) "reading tablets". It would be stupid for either of them to skip all of the new functionality and internal improvements Google has released.
2. Plenty of apps Amazon wants in their Appstore are also going to support (and want to use features from) ICS. While Amazon could make them jump through unnecessary hoops, that just makes their Appstore (and, by extension, the Kindle Fire) weaker.
3. Amazon itself is going to be developing applications that support ICS (e.g. Kindle, Amazon MP3, Amazon Mobile, Price Check, ...) and those apps will, in some cases, need to use ICS-specific features to be competitive. They could fork their own internal applications, I suppose, but why would they? Would they really want to risk a situation where an ICS version of an app is better than the Kindle Fire's version of the same app?
The issue with the Fire is that it's forked, that there may be future compatibility issues, that it will never officially become an ICS device and that those things may hold Android back in may ways (for instance app developers always having to work to a low baseline to access the Fire users as a potential market).
So yes it's an Android tablet but it's one that may be a mixed blessing for Android and deserves some subtlety in the distinction.