• CONTACT
  • REQUEST A PRODUCT REVIEW

TheTechnologist.TV

  • the column
Home

Content about Technology

Monday, April 12, 2010 - 14:59
@War: Apple 3.3.1 to escalate losses for Silicon Valley VCs, Storm Ventures takes biggest hit

UPDATE: While I personally think that Apple has fast become the embodiment of closed. I respect CEOs who take risks. Plenty of CEOs (in fact all the ones I know) would never even think of insulting a past present or future vendor partner. For each CEO I Respect I can think of a moment that they were dead wrong.

Bill Gates said Linux would never be secure because people working for free in their spare time don't do good work. Then came the age where the would could not operate without the security that Linux provides.

Michael Dell once held a press conference where he said "people are going to access the internet on their phones? This little screen? Never."

Steve Jobs said that bloggers were a fad and that they would never be respected the way journalists are. Soon after that, we entered the era of The Huffington Post, Perez Hilton and blogs on almost every site.

I'm accustomed to seeing the big personalities have their dooseys over time. That said, I've never seen this and don't know what to do with it: Monitoring Adobe's Development of the Flash Compiler for iPhone, waiting for them to have spent time and money on getting it to work and work well, then switching the SDK license just before launch costing them time, energy, money and face with the industry. It is demoralizing and asinine at best and shouldn't make any company who depends on Apple's API's feel safe.

It is irresponsible of any API provider not to proactively inform a developer that they would never approve what they were building. It is the antithesis of the 3rd party API experience to have spent millions on a project and be informed by TOS update days before launch that everything you have worked on with your team is never going to reach the market. On top of that, they knew, and deliberately waited for it to be as expensive as possible.

That was not cool. The fiduciary responsibility of an executive or director is to maximize the return on investment for the shareholder by competition for the consumer and the consumer must be allowed to choose the winners. If that behavior is allowed to stand then all we have worked for in Web 2.0 is greatly diminished by the precedent. That you can bait and switch a developer into huge losses by manipulating your TOS.

Apple seems to think it is ok to offer an API, lure as many companies as possible to develop for it, keep one specific developer at arms length until they have spent a fortune, then deny that team their launch, and toss their project in the boneyard. The material efficiency of the entire industry drops when money is wasted. Everyone suffers. A simple email when they knew would have saved heartache and capital loss. This is no way to compete for market share and it undermines Apple's credibility in ways more costly than letting Adobe make slow apps. The developers don't hold press conferences and will never tell Apple that was evil. They will bide their time and hedge their bets.

My own opinion aside, I received an email from the CEO of Appcelerator which, like Phone Gap's assertions from a few weeks ago, explains that they are not the target of 3.3.1 and claims that they will be an exception because they claim to be better developers than Adobe and have more attention to detail.

It's a dark time in the valley when emails like this have to be written. The spirit of the iPhone platform is shifting from announcements like "Great news! Look how cool we are!" to "Great News! We probably won't be in the carnage you just saw!"

Here's the message in it's entirety:

Sid Gabriel:

I wanted to provide everyone an update on the issues related to the iPhone 4.0 Terms of Service. While we have yet to receive any formal word from Apple as it relates to Titanium, this morning, Steve Jobs posted some thoughts on why Apple is banning Flash on the iPhone/iPad. The focus of the article is on making two important arguments: how to ensure a high-quality iPhone experience and the importance of using open technologies. Based on his piece, we have a few followup points as this news relates to Appcelerator Titanium.

- If there was any doubt, Apple's specific target is Adobe Flash.

- At the crux of every one of Jobs' points is a single overriding theme: ensuring application quality. More specifically, Apple wants to make sure that applications written for the iPhone/iPad are developed using all the great features in the iPhone SDK and that they should not be developed using a lowest common denominator approach. We couldn't agree more. Split views, popovers, cover flow views, native table views, native maps, native tab bars… There are over 2,000 methods and properties available to Titanium developers to customize their applications with almost every native Apple UI or feature imaginable. And if something isn't in there that you need, it's easy to extend the platform by building a native Titanium module. This extensible, native architecture is probably the reason you chose Titanium in the first place. One of the most common statements we hear about Titanium is: "You built *that app* in Javascript. Wow!".

- As it relates to adoption of new iPhone capabilities, we rev our product very quickly. In fact, next week, we'll introduce support for iPhone 4.0 application development with Titanium 1.3.0. And we'll continue to add new APIs as Apple finalizes the 4.0 OS. This has always been the case with our stance on updates to the underlying operating systems that we support. In all cases, we are working with Apple APIs under NDA before they're finally available to the public and we'll continue to do that as normal.

- Apple has a clear preference for open technologies, specifically HTML5, CSS, and Javascript. Here too, we are in alignment. Titanium developers code in Javascript as executed by the Webkit engine (eg: the kind that Apple prefers in its ToS), and web content can easily be displayed using HTML5 and CSS through a web view. We're big supporters in these technologies and ourselves have contributed to WebKit (Martin Robinson, one of our desktop engineers, is a WebKit committer).

- We've had over 50 applications approved for the App Store over the past 3 weeks under the new terms (which every developer now needs to agree to). Not a single one has been rejected for being built on Titanium. We even updated our own test app, Snapost, after accepting the new terms.

In summary, Apple is targeting Flash (mission accomplished) and Apple wants to push their platform forward by having only high-quality, native applications in the App Store. We couldn't agree more. Native application development with open technologies is in our DNA and our continued vision for Appcelerator.

Sincerely,
Jeff Haynie
CEO

4.1 Million invested in Appcelerator may evaporate if it is no longer able to publish iPhone Apps
http://www.crunchbase.com/company/appcelerator

This was an investment of Larry Augustin and Storm Venttures
http://www.crunchbase.com/person/larry-augustin
http://www.crunchbase.com/financial-organization/storm-ventures

This effects it's Principals: Ben Choi among others.
http://www.crunchbase.com/person/ben-choi

This in turn weakens the strategic positioning of Book Renter and Mobile Iron
http://www.crunchbase.com/company/bookrenter-com
http://www.crunchbase.com/company/mobileiron

Wednesday, March 31, 2010 - 05:59
The ARDevMob Spring Open Developer Challenge

The #ARSpringOpen

On April 24th and 25th ARDevMob will hold an augmented hackathon event
at The PariSoma Innovation Loft in San Francisco California.
Developers will form teams and compete to create the best Mobile and
Web Applications. To qualify applications must contain a "mixed
reality" or "alternative interface" which utilizes a web or cellphone
camera. This is a trial run for a larger global event we are holding
in June.

From March 24th to April 24th The ARDevMob will be touring local user
groups, clubs and meetups promoting the ARSpringOpen and presenting
tutorials for Flash, iPhone, Android and more. These sessions will
prepare you to join a team in our trial run on April 24th and 25th.
Look for the ARDevMob Spring Training logo at your local development
group. There will be prizes at each Spring Training event. The grand
prize at the trials on the 24th is a SpringDesign Alex ebook reader,
or Nexus One. More prizes to be announced.

Registration for the ARSpringOpen begins soon. Follow @ARDevMob on
twitter or sign up at ARDevMob.com for updates.

Posted via email from ARDevMob

Saturday, March 27, 2010 - 18:51
Wavesitting. Commentary on Using Google Wave for Projects

It was suggested that I use Google Wave for a recent project. It had been six months since the GTUG Campout at Google's Campus where I participated in a 3 day hackathon event focused on Wave. I figured it was worth another look. Back then it was simply to slow to use and people were awkward with it. We began the wave and started work on the project. 

One week in, I feel a sense of disconnect from my team that I have not felt since leading teams in high school: The feeling that everyone is on board and no one knows what we're doing. For a man who makes a career of organizing, analyzing and rallying people in the support of human life, it's hard to accept, but my current project has lost the critical thread of leadership. The element I am most responsible for. 

Before I go and wrangle each and every member and thread back into a manageable and productive form, I feel it is my duty to share with my readers the critical fault in using Google Wave for open development or community research projects: these are projects where no one is paid to perform a specific role the project and each member has a varying degree of attachment to the outcome of the project. They are the most common type of human project and occur most often in families and community groups. 

The Critical Fault: Illusions of Unanimity

This particular case included members coming onto the team one by one and being given the task of "coming up to speed" by reading the wave. "It's in the wave" or "I'll put it in the wave" became intuitive receptacles for information. As the information flow increased, and as targets for the information became more obscure, members natural ability to see where they belong in the project and where they could contribute diminished greatly, but their feelings of "being a part of something" increased as a result of an illusion of unanimity. As of this moment, after bringing in 8 people, I have lost one and still do not have the critical elements of sub-project "owners" and criteria by which to delegate tasks to them. As the leader and only point of contact that touches the others directly, I'm the only one that knows how fractured our team structure is. As it stands we have very quickly and efficiently become factions in the service of multiple and ambiguously similar goals and only I can see it. This is a powder keg I have to go and fix. I'm writing because I could easily have overlooked this, or thought that it was a feature unique to this team. The cost would have been not only the project but the team and the opportunity we gathered around.

It's appropriate that "GroupThink" is trending on Twitter today. The cost of encouraging any member of a team, culture or society not to maintain their own independent voice and critical perspective is clear: http://twitter.com/#search?q=Groupthink 

I'll look at wave again in another 6 months. Allowing a team's momentum and motivation to accelerate with multiple forms of content and realtime activity is interesting science. For now, my commentary is that it's fun to play with, but if you have anything at stake or any stakeholders: Wave at your own risk. Until someone makes the Gantt Chart wave gadget of the future (with meritocracy based micro-currency embedded), it lacks the impetus for upstream leadership to emerge. 

Posted via email from The Sid Gabriel Post

Saturday, March 20, 2010 - 08:02
Joshua Topolsky Is Wrong - Only Android Can Save Palm Now [rant]

Joshua Topolsky saved Engadget years ago, I love his writing and his
penetrating focus on detail. Sometimes he's stuck in "the box" though
and his article on Palm advises them to "go faster" doing more of the
same. While he is right that the ads suck I don't remember him being
at all the developer events I've covered. He didn't see the look in
the eyes of the iPhone developers who came to the mojo launch to find
we didn't have access to the accelerometer in the 1st sdk. They gave
us screen rotation. That was it for them. We came out on a weekend and
we love it yes, but no Augmented reality and no games with motion?
Then they hit us with another SDK later. 2? lameness beyond the pale.
All their developers, that they forced to learn a new platform in the
middle of the iPhone heyday and Android Genesis jumped ship at the
second sdk.

They can not right that in this cycle and can never right it with WebOS.

It's clear to the developer world that Palm will not survive the next
wave of Androids unless they spit out a Treo device running Android
and drop the proprietary webos bulls$%t. Beautiful idea, execution
:fail, we love you still, now move on before Elevation goes ape5h1t
about their 400+Million Dollars evaporating.

Android on Palm Hardware. Consumers just need to hear it once to want
it. A resurgence of the street-smart original Newton-killer Palm with
a re-surging Treo brand equipped with the unimaginable power of
Android 2.1 with Flash10 and 15 years of hardware expertise unloading
onto an unsuspecting industry a F$%k-load of [I don't care what I
look like, I put power in the hands of my users no matter what
(PERIOD) ]

I remember the WindowsMobile Treo shocking the hell out of me in 2002.
I remember Steve Jobs' "Hell Froze Over" slide when he officially
decimated all hope the zune ever had by releasing iTunes for Windows.
Disruptors disrupt because no one expects them. Stop playing everyone
elses game and play the game everyone else is playing.

Palm, you make hardware. Your Folio idea was tight. You botched the
OS. It would be awesome with Android. You could sell those for use
with other manufacturers Android phones. Palm was floundering when it
picked up Handspring landing it with the first smartphone. My first
cellphone was a backpack for a Visor Edge. Get over the damn brand
identity trap. Whoever is in charge over at Palm just tell everyone
that you are making the worlds best Android device for release in 4
months. No questions just do it. Put whatever you have to on hold but
get an Android into the market that shows them all how to make a
Smartphone.

Let the name bring up memories of past "darkest hour" victories. Call
it The Palm Edge

If Palm doesn't do this it is likely that in 6-8 months they will
openly discuss collapse as hundreds of thousands of independent flash
developers and design firms rush the mobile world outnumbering
out-designing and out-classing the iPhone App store on an open screen
that Palm developers can't get on without defecting. I have no
endorsement of a proprietary palm failure lasting one day longer when
they can treat their wounded bottom line and produce a great device
with help from the worlds most advanced mobile ecosystem. The OS that
will not be owned and is here to stay. Android.

Here's Engadget's list of suggestions though they pull the punches on
a bleak future:
http://www.engadget.com/2010/03/19/palm-this-is-your-survival-guide/

Posted via email from The Sid Gabriel Post

Friday, March 5, 2010 - 04:21
"Open" Mates Apple's Zero Sum

For our readers that study Game Theory the title of this post is all that has to be said. Speaking only from this discipline, Apple has already lost in any theater of war it opens in the service of maintaining an iPhone-only world. While it is not impossible to arrive at a future without Android, it is more possible to arrive at a future with market equilibrium. This is both true and paradoxical. This is because an analyst has to model competitive advantage with the value of material efficiency greater than market force to see this, but from a perspective that expects the entire market to be optimized and not simply one carrier and device, you can clearly see that not only is it atypical for a single device to contain 100% market share, the loss for such an imbalance belongs to the consumers and it is a win that Apple got this far.

Apple contends that for them to win the others have to loose. This is a textbook Zero Sum Game. Google, HTC, and the open handset alliance are competing in a Constant Sum game where each is incentivized to cooperate in a practice where each player's victory incrementally benefits all players by expanding the field of play, and no player has incentive to risk critical loss. Though Apple is not "playing their game" they are upon their field entirely without the advantage of a market position within. Apple doesn't sell phones beyond AT&T, nor do they sell phones that are carrier independent such as Google's Nexus. Apple definitely doesn't sell on Sprint and they don't allow developer culture outside their own interface dogma which is expressed in it's AppStore approval process. Apple simply doesn't operate in HTC's market. Apple operates it's own market and only in the service of AT&T- a carrier that had a track record of selling touch-screen HTC devices (under the name iPaq) for 5 years before the iPhone arrived in 2007.

Apple has filed suit against HTC, a robust and fortified, mature company in good standing with many organizations which give it the protection of thousands of patents. It is far more likely that the patents contained within these organizations are infringed upon by the iPhone. While Apple has what they believe to be a zero sum advantage, in 10 patents they believe they can assert against AT&T. They have a constant sum defeat that has already come to pass. As the survival of HTC benefits every manufacturer. The patent cross license agreements, covering the alliances, organizations and groups et al. which Apple is not a part of, now have all of their patents extending over HTC. The arena Apple just opened, with a predictable and clumsy move is one where their 10 patents will be examined against the backdrop of an entire industry united in the support of "open". Which mathematicians will likely refer to in the future, as the mother of all bear traps, which bound a 900 pound Gorilla on it's own dime. If you run the numbers you can see Apple will eventually compete as an equal and submit it's victories in a way that helps industry.

This article covers the unique meaning of "open" that generated the Android phenomenon, some quirks about intellectual property, and a little film noir. We set the stage with math, but we need
to go to Casablanca to understand Android.

Casablanca

Global economic conditions have depressed sales in every column of
consumer electronics. Every column except smartphones which,
curiously, are booming in a recession. Inside this boom there are
moving parts at work that confound intellectual property analysts and
set the stage for what is emerging as one of the most fantastical yet
factual stories that have ever come out of Silicon Valey. The story of
two platforms, Android, and the iPhone and one of these platforms has
a curiously lucky feeling.

Many in the industry are surprised when they learn that Android is not
Anti-Apple and does not belong to Google. It is a virtual machine
similar to SUN's JVM called Dalvik that runs on Linux and has a layer
of libraries that developers can use to make apps via a software
development kit or SDK. It's not much different than Ubuntu Linux.

What is different is the strategic positioning of Dalvik and a
something known by intellectual property professionals as multiple
infringer conditions. Conditions under which a patent is violated by a
product user and not an individual manufacturer. There must be a
single infringer to enforce a patent upon. When the single infringer
is part of the Open Handset Alliance, there is another interesting
feature. The Open Handset Alliance has a built in patent cross
license. This means that they claim the benefit of the patents of all
Open Handset Alliance members. Which at this point is every mobile
manufacturer except Apple. Android is Open Source Software released
under the Apache Software License Version 2 which allows unhindered
commercial use and it's Linux underpinnings were lucky enough to have
multi touch functionality added by way of the Linux Kernel months ago.
Take all of those entities into consideration, and you have quite a
problem determining who is responsible for a feature on an Android
Device.

Googles nurturing of the open source project and the community of
developers within, along with consumer confidence in Google's brand
and the battle tested promise of open source and the linux kernel have
created a honeypot for device manufacturers and app developers looking
for freedom to operate in an industry stifled by intellectual property
claims.

As the only booming sector of consumer electronics, the mobile
industry is a battlefield and Android has become mobile's Casablanca.

To developers around the world, the indicators of a viable platform
are largely accessibility and reach. The common app developer has the
wherewithal to work in 2 perhaps 3 platforms. The iPhone App Store and
the multiple Android markets are the only platforms where developers
anywhere in the world can make products and sell direct to the
American consumer at scale. Android and iPhone developers are in
comparable demand but with tablets, media players, phones and
net-books already flooding the market, development trends clearly
favor Android.

The promise of "open" attracted much of the out-of-work laid-off
technical talent pool. With free training and education available if
you have a computer and an internet connection, the Android open
source project has minted capable mobile developers out of run of the
mill web developers and Computer Science PhD's alike. Comparing the
hundreds of iPhone app developers at Silicon Valley's 3rd annual
iPhoneDevCamp to the hundreds of monthly attendees of the Silicon
Valley Android Developers Meetup, you see a lot of crossover. In
Silicon Valley the developer is king and there was no boundary
suggesting otherwise, until Apple banned the word Android from it's
App store and asked the finalists and winners of the Android Developer
Challenge to remove the award winning ribbon from the iPhone versions
of their apps. Imagine what you would think if you were a
hand-to-mouth developer surviving a recession and Apple limited your sales by
forbidding you from including awards your app has won on the pages consumers use to decide which app to buy.

This promise of "open" has attracted almost every handset manufacturer
on the planet and has generated startups as well. Though the most
interesting potential in our story lies with the black sheep. If Palm
stays true to form we will see them launch a handset running Android
before they risk loosing their cult. They did this during the rise of
Windows Mobile, a move which many analysts believe saved the company.
There is a sense of certainty amongst insiders that further declines
in sales would push Palm into the Android arena where Palm's 15 years
of experience manufacturing handhelds and loyal user base would give
the company a significant advantage against foreign manufacturers in
competing for market share.

While industry insiders still balk at the idea, RIM's Blackberry
Platform could also directly compete for market share by producing an
Android powered Blackberry. One might think that apps written for
Blackberry would be incompatible, but in Casablanca, no one is foreign
and the core applications of the blackberry user experience do not
contain functionality beyond the scope of the Android software stack.
Since Blackberry apps are written in Java, and though it would be no
small feat, creating a Blackberry app "wrapper" for Android that
adjusts differences in app framework architecture at download is more
than possible, it's within strategic reach if they see any sharp
decline in sales. Android's open architecture ensures the same is true
for Palm WebOS apps as well.

Applications that run from translated code would not loose performance
compared to apps written using the Android SDK because of a curious
feature of the Android software stack: every app is converted from
it's language of origin to Dalvik byte code at runtime. Casablanca has
no native tongue.

The final piece to account for in the Blackberry stack is made
possible by the Android Native Development Kit or (NDK) which contains
the elements necessary to implement Blackberry's Enterprise Security
layer natively on Android handsets.

Whether Palm and RIM know it or not, Casablanca has them covered.

The platforms out in the cold are Apple and Oracle. Oracle, which
purchased SUN Microsystems cannot assert ownership over the use of
Java as a language on the device as the SUN Java model has been to
charge per virtual machine (JVM) and have the tools for compiling
applications available for free. Making a claim to the operation of
Dalvik would fail because the handler that converts Java
to Dalvik byte code does not infringe upon the function of a Java
Virtual Machine. Developers are working every day to extend the reach
of Dalvik far beyond the handset. The JVM is not the most likely java
interpreter to land on a tablet or net-book. By removing costs and
distributing responsibility Android makes "open" work.

Though I don't believe it is possible, when I examine the
ramifications of a victory for Apple, I see a cold and bitter wind
rolling across hundreds of startups as they let go of their dreams and
yield to the company that only uses one network and forces everyone to
sync their contacts with a jukebox.

When I examine the ramifications of a successful defense of HTC, I see
a young industry on the move, where hundreds of startups mentioned
earlier are inventing things you would not believe.

Law and capital aside, I believe in R Buckminster Fuller's systemic world view. There is no zero sum, there just isn't. As we begin to
awaken to the truth that we live on a planet, a closed system where
there is no action that does not effect the whole, our factional tribes will
learn to work in the service of sustainable culture where the ongoing
pursuit of doing more with less will be the challenge of industry and
the success of one means success for us all. Where the stage has been
set for everyone to enhance the material efficiency of life with every
consecutive generation of hearts and minds which experience it. That's
a user interface worth protecting.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • next ›
  • last »

News

TheLightStalkingLibrary
2 weeks 3 days ago

The Front Page

The 3 Day Google Tech User Group Campout at The Googleplex Kicks Off Today!
3 weeks 5 days ago
Volkswagen Beetle converted to run on methane headed for the UK streets
4 weeks 6 days ago
Arqera and The Promise of Open
15 weeks 1 day ago
@WAR: Apple's New Age of Expansion
16 weeks 6 days ago
@WAR: The Age of Apple Expansion (PDF)
16 weeks 6 days ago
more

Active Topics

  • Technology
  • Google
  • Android
  • iPhone
  • Entertainment

@tttv

  • Apple & Microsoft assertions about HTML5 & Flash are only credible if Quicktime, Windows Media & Silverlight are also being abandoned. — 18 weeks 2 days ago
  • I'm in Pensacola Florida. The oil slick hits it <16 hours. I know we (engineers and developers) can find a way to fix this. We have to try. — 18 weeks 3 days ago
  • Apple, to care for human interface, you must first care for human life and, our well-being is directly linked to feeling a freedom of choice — 18 weeks 3 days ago
  • Something must be done about Apple They are destroying the competitive fabric of Silicon Valley. LaLa.com was the music service in Chrome OS — 18 weeks 3 days ago
  • @captproton one more thing: http://www.youtube.com/watch?v=X2TdLmxc_oo this is your exact code @ardevmob it rocked — 18 weeks 4 days ago
  • @captproton Yes. Though I'm in Memphis TN eating a rib dinner. I left two ARDev stations w/projectors back in SF. Lets coordinate via email — 18 weeks 4 days ago
  • I admit it. I'm in love with processing.org processing.js & openprocessing.org: Rapid prototyping in such a molten state-nothing's tied down — 18 weeks 4 days ago
  • @captproton yes. The projection comes from behind. I'm making a video of your app from ardevmob running on it. Will tweet when it's up. — 18 weeks 5 days ago
  • Overheard: "yes, it became between us all indeed." — 18 weeks 5 days ago
  • I finished this last night, recording the Awetastic demo tonight. Now is the time on Sprockets when we dance! http://tweetphoto.com/20280596 — 19 weeks 16 hours ago
  • Android just got some love from Mozilla. This link will install the Fennec alpha on your Android: http://bit.ly/fennec-android — 19 weeks 21 hours ago
  • I can't believe it. How lucky. Found a giant piece of frosted glass. ARDevMob knows what Im going to do it this http://tweetphoto.com/****** — 19 weeks 1 day ago
  •  
  • 1 of 22
  • ››
more
  • the column