Last month, Microsoft took bookseller Barnes & Noble, the company responsible for the Nook and Nook Color, to court over some patents infringed because B&N used the Android operating system in the Nook and Nook Color. This is definitely nothing new in the world of mobile devices. It happens all the time, especially with companies like Apple and Microsoft trying to take complete dominance of every arena they enter. That's not the big story here. Read More
Update: Linux devs are not happy about this.
Update #2: And just like that, only a few hours after this article, HTC released the Thunderbolt kernel source.
If you've been following the "drama" around Android kernel source release timelines and device manufacturers (such as HTC), you should be already aware of 2 forces pushing in opposite directions:
- On one side, we have the Android community, which maintains that according to GPLv2, Android kernel sources need to be published together with a given device release.
An interesting little tidbit came across to us in an otherwise ordinary posting on Amazon's app developers' blog. While developers will have the option to use DRM or not in their apps, those that do use the digital licensing service may present problems for those users who are temporarily without an internet connection.
Comparing it to the way Amazon currently handles the storing of Kindle books, the curious part of the post reads:
"Any app that has Amazon DRM applied to it will require users to have installed and signed-in to the Amazon Appstore client to access the app.
Have you ever seen one of those annoying comments on the Android Market promising the riches and all the Android apps in the world for a low-low monthly price of $10? Sites like that pirate paid games and apps off the Market and then distribute them illegally, pocketing all the revenue. That's modern day warez at its finest.
Whether it was because of Android's openness or Google's notoriously poor focus on the Market, no DRM or licensing protection was available in the SDK for developers to utilize; so unless you rolled your own licensing scheme from within the app (which had a side effect of circumventing Google's payment system and therefore netted developers a whole lot more than 70% rev share), your app was easily "piratable". Read More