Group items tagged

Excellent legal piece explaining the options and methods of how software programs use licensed and copyrighted third party libraries through an API. Finally, some clear thinking about Google Android and the Oracle Java Law Suit.
excerpt: Another option for a developer is to do what Google did when it created Android, and create replacement code libraries that are compatible with the existing code libraries, but which are new copyrighted works. Being "compatible" in this context means that the new libraries are called in the same way that the old libraries are--that is, using the same APIs. But the actual copyrighted code that is being called is a new work. As long as the new developer didn't actually copy code from the original libraries, the new libraries are not infringing. It does not infringe on the copyright of a piece of software to create a new piece of software that works the same way; copyright protects the actual expression (lines of code) but not the functionality of a program. The functionality of a program is protected by patent, or not at all.
In the Oracle/Google case, no one is arguing that code libraries themselves are not copyrightable. Of course they are and this is why the Google/Oracle dispute has no bearing on the enforceability of the GPL. Instead, the argument is about whether the method of using a code library, the APIs, is subject to a copyright that is independent of the copyright of the code itself. If the argument that APIs are not copyrightable prevails, programs that are created by statically-linking GPL'd code libraries will still be considered derivative works of the code libraries and will still have to be released under the GPL.
Though irrelevant to the enforceability of the GPL, the Oracle/Google dispute is still interesting. Oracle is claiming that Google, by creating compatible, replacement code libraries that are "called" in the same way as Oracle's code libraries (that is, using the same APIs), infringed

Vaporware, but interesting. More info on the developers' website at .  Basic idea is a computer on a stick that can be plugged into either other computers or into an HDMI flatscreen TV. In the latter scenario, Bluetooth connectivity for keyboard/mouse combo, provided by e.g., a smartphone. The USB connection is v. 2.0, but I'll guess that USB 3.0 would soon be an option in newer models.  According to the specs it can run either Android or Ubunutu. If you check the developer's website, they definitely have their eyes on the growth in the numbers of HDMI-equipped TVs. Note that if delivered as described, this breaks boundaries of mobile devices, tending toward a convergence of TV monitors and mobile devices in an unexpected way. 

Perhaps the best article about Google that I've ever read. The author describes the many insidious methods and requirements that Google uses to dominate and totally control the Android Open Source Project, and the incredible Android ecosystem that has grown up around that oss project. This is a must read! Intro: "Six years ago, in November 2007, the Android Open Source Project (AOSP) was announced. The original iPhone came out just a few months earlier, capturing people's imaginations and ushering in the modern smartphone era. While Google was an app partner for the original iPhone, it could see what a future of unchecked iPhone competition would be like. Vic Gundotra, recalling Andy Rubin's initial pitch for Android, stated: He argued that if Google did not act, we faced a Draconian future, a future where one man, one company, one device, one carrier would be our only choice. Google was terrified that Apple would end up ruling the mobile space. So, to help in the fight against the iPhone at a time when Google had no mobile foothold whatsoever, Android was launched as an open source project. In that era, Google had nothing, so any adoption-any shred of market share-was welcome. Google decided to give Android away for free and use it as a trojan horse for Google services. The thinking went that if Google Search was one day locked out of the iPhone, people would stop using Google Search on the desktop. Android was the "moat" around the Google Search "castle"-it would exist to protect Google's online properties in the mobile world."

The more interesting issue to me is the accusation that Google violates antitrust law by boosting its comparison shopping search results in its search results, unfairly disadvantaging competing shopping services and not delivering best results to users. What's interesting to me is that the Commission is attempting to portray general search as a separate market from comparison shopping search, accusing Google of attempting to leverage its general search monopoly into the separate comoparison shopping search market. At first blush, Iim not convinced that these are or should be regarded as separable markets. But the ramifications are enormous. If that is a separate market, then arguably so is Google's book search, its Google Scholar search, its definition search, its site search, etc. It isn't clear to me how one might draw a defensible line taht does not also sweep in every new search feature  as a separate market.   

Excellent chart comparing the iPhone 4 to current Android 2.1 releases for Verizon, Sprint and T-Mobile.  Evo 4G wins big.  Check TipB.com for future comparisons. it always helps to have a datasheet on each phone and network's devices.  Luckily, TiPb.com has already put a comprehensive list together of the smartphones and their features:

Great stats and charts!  Here comes the Android. excerpt: Google's Android operating system has plenty to celebrate this holiday season -- and now, a new trio of studies suggests the platform is poised for even more success in 2010. There's no question Android's been enjoying plenty of time in the spotlight since the launch of Motorola's Droid smartphone. But with dozens of new Android devices expected to debut in the coming months -- possibly even including the omnipotent "Google Phone" (have you seen the things that phone can do?) -- the biggest burst may still be ahead.

ARCELONA - This year at the Mobile World Congress is the year of Android. Google's operating system debuted here two years ago. Last year we expected a slew of handsets, and saw just a trickle. This year, Android is everywhere, on handsets from HTC, Motorola, Sony Ericsson, and even Garmin-Asus. If this were the world of computers, Android would be in a similar position to Windows: Pretty much every manufacturer puts it on its machines. This is great news for us, the consumer. Android is stable, powerful and now it even runs Flash (I got a sneak peek of Flash running on a Motorola handset here at the show. It crashed). It's even better for the manufacturers, as - unlike Windows Mobile - Android is free. It's also open, so the phone makers can tweak it and trick it out as much as they like. And they do like. Most of the Android phones here at Mobile World Congress are running custom versions of Android, which differentiates them and, in theory at least, makes them easier to use, hiding the complexities of a proper multitasking OS from the user.

Right now, we're all worrying about Apple's patent claims against HTC, but Android may face a similar attack from Microsoft. It's not terribly well known that Microsoft claims that it owns significant intellectual property used in Linux, the operating system at the heart of Android. Starting in 2006, Microsoft began reaching licensing deals with a number of companies that use the open source OS, among them Novell,  I-O Data, Samsung, LG Electronics and most recently, Amazon. All these deals are similar, but as an example, Amazon has agreed to pay Microsoft licensing fees to use Linux on Amazon.com and on the Kindle. Read that again and let it sink in. Many have voiced skepticism that Microsoft could successfully defend their claims, but so far, companies have rolled over and complied rather than take the question to court.

Nice article from Matt Asay, who is now the COO at Canonical, the company behind Linux Ubuntu and Google's Chrome OS. excerpt:  As ZDNet's Dana Blankenhorn remarks, "Just as the Internet takes friction out of the distribution and development process, open source for Google removes friction from the business process." In Android land, this means making it easy for device manufacturers and wireless telecoms to evaluate, develop on, and ship Android-based devices. And ship them they are, to the tune of 60,000 Android devices per day. As Wired noted after the recent Mobile World Congress: This year at the Mobile World Congress is the year of Android. Google's operating system debuted here two years ago....This year, Android is everywhere, on handsets from HTC, Motorola, Sony Ericsson, and even Garmin-Asus. If this were the world of computers, Android would be in a similar position to Windows: Pretty much every manufacturer puts it on its machines. There is one key distinction, though: Android is open source. It makes all the difference.

Excellent guidelines for developing crossplatform smartphone apps in HTML5-CSS-JavaScript.  Covers Appcellerator, Sencha, jQuery, and Drupal.  Great resource!

Google's Honeycomb operating system is specifically optimized for large-screened tablets, but the first bits of the new platform are starting to now filter down into Android smartphones. The Android Developer Blog notes the release of an "Android Compatibility Package" that includes a new Fragments API for developers building software for Android 1.6 and up. Fragments are a key element for Honeycomb tablets such as Motorola's Xoom, as they allow for multiple windows of activity on the device display, which can greatly increase the usability of an app.

Android device owners have one less reason to drive to the bank now that PayPal has added check scanning to its software. PayPal today released an update to its mobile app for Google's platform that brings the feature: Users can snap a picture of a check with their Android 2.1 or better phone and have the amount automatically deposited to their PayPal account. The newest version of the mobile app, version 2.8, also allows the software to be stored on a handset's memory card, which can free up internal storage on the device. iPhone owners have had the check scanning feature since October of last year and they don't seem shy about using it. In a blog post today, Shimone Samuel, the Product Experience Manager for PayPal Mobile, says that iOS device owners have been scanning about a million dollars per month using the image capture feature with checks. I noticed some lengthy terms of service upon installation of the new PayPal app; notably that users are limited to $1,000 per day and $3,000 per month for check scans. After accepting the terms, I ran through a quick test by writing myself a quick check for $5; note that you can't write checks to "Cash" using the software.

SDK - OpenGL Developer tool for crossplatform development of iOS and Android Apps.  Much better performance than Flash.  Check out the KWiK add-ons for Adobe Photoshop for writing visually immersive books and magazines.  Corona is a must watch technology. excerpts: High-performance graphics. Corona was built from the ground up for blazing-fast performance. Built on top of OpenGL, OpenAL, and Lua, Corona uses the same industry-standard architecture as top-selling mobile games from Tapulous, Electronic Arts, and ngmoco. Develop across platforms. Corona has the only complete solution for developing across platforms, OS versions, and screen sizes. You can write once and build to iOS or Android at the touch of a button, and Corona will automatically scale your content from phones to tablets.