Peter’s last blog spelled out some major problems with Apple “stifling innovation”. With the FCC now involved with the battle between Google and Apple over the rejection of the Google Voice Mobile app, it’s got me thinking…
As developers, we deal with technical limitations and licensing restrictions all the time. Commercial and open-source licenses clearly spell out what you can and can’t do (legally) within a platform or framework. This ensures that when we build applications that use an existing framework or integrate a 3rd party application, the copyright holder’s “program” is preserved and no laws are broken.
What if a platform’s restrictions weren’t disclosed entirely to developers? Or worse, what if the owner of the platform arbitrarily decided which applications were allowed or restricted regardless of whether they followed the guidelines provided? Wait, isn’t that what Apple’s doing?
Apple may finally be in over their heads after rejecting a perfectly legitimate app, Google Voice, and then lying about it!
There are a number of core iPhone apps that are powered by Google, such as Search, maps, YouTube, etc. Apparently, Apple feels that Google is taking over too much core functionality of the iPhone. Since the Google Voice app provides alternative functionality to the iPhone’s core phone application, perhaps Apple feared they would essentially be turned into a hardware manufacturer for a Google-dominated device.
You can read more about the insanity on techcrunch:
The Truth: What’s Really Going On With Apple, Google, AT&T And The FCC


Obviously, iPhone applications are the new craze. One billion (1,000,000,000!) apps have been downloaded in a very short period of time, and with the upcoming release of iPhone OS 3.0 this number is sure to skyrocket.
I’ll come right out and say it…IE6 is a dirty word around the office. I don’t want to bash Microsoft or any IE6 fans out there, but as web developers, there’s nothing more frustrating than having to comply with a nearly 10 year old browser. It’s been estimated that a staggering 20% of total web development time is spent catering to Internet Explorer 6. On top of that, there are a lot of amazing design and functionality ideas that are shot down because the potential for catastrophic failure in IE6 is imminent.
Looking at our production schedule for the next few months, it dawned on me that it consisted primarily of web services and online systems. We’ll always have a soft spot for standard web sites and content managment systems, but it’s exciting to see the innovative ideas flowing through bottlecap these days.
I recently starting using Xobni (pronounced ‘Zob-nee’), and I must say that I was blown away. Very rarely do I come across a plug-in or application that gets me excited enough to update my facebook status, but Xobni did the trick.
Here at bottlecap, we spend a lot of time building web forms for all kinds of projects. Personally, I don’t have anything against forms. The information architect in me enjoys the challenge of organizing and validating a user’s input in a way that makes sense to them, and ensuring that the information received is accurate. As an avid fan of digital services and generally impatient person, another part of me view forms a bit differently.