March 20, 2008 9:41 AM PDT

Just how open will Verizon's network be?

by Matt Asay
  • Font size
  • Print
  • Post a comment

Verizon made a big splash in 2007 by talking up its plans to open its network to third-party developers. "Any application, any device" was the mantra.

Several months later, however, more questions than answers remain as to just how open Verizon plans to be, and what it's going to charge for the privilege of openness, as BusinessWeek has highlighted.

Among the biggest concerns: Verizon did not divulge any details of the pricing plans customers would be offered to use such devices. Nor did it publish any specifications to help software developers create applications for the network. In fact, the company distributed materials to attendees online, stressing that the company "will not approve, test, or service third-party applications that customers load onto their Open Development Devices."

And despite numerous claims by Verizon executives that testing and certification for new devices could take as little as four weeks, many attendees are skeptical the process will be that easy.

Let's be clear: Verizon is breaking new ground here, for itself and for the industry. It's highly unlikely the company has a clear idea of where it wants to go with this open-access pledge. The only thing it likely knows is that the U.S. mobile market is fairly well-saturated, and opening up to experiment with new monetization and development models is likely worth a bet.

Personally, I think Verizon's pricing plans can wait. What it needs, more than anything else, is to spark the imagination and productivity of third-party application developers. It was criticized for focusing its launch on handset manufacturers, which is an important constituency but not the disruptive community it needs to crank out new financial opportunities on its network.

As Microsoft learned years ago on the desktop, there's a ton of money to be made with a platform that hosts a huge array of third-party applications. Verizon has that chance now, but needs to specify the details around its openness pledge so application developers can figure out how and when to get involved.

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay.
Recent posts from The Open Road
2010 the year of cloud-computing...M&A
Canonical shines its Ubuntu light on consumers
Open source became big business in 2009
Will we see an open-source IPO in 2010?
Could Apache keep Google's regulators at bay?
Red Hat's Q3 earnings defy gravity
Canonical's opportunity to simplify Ubuntu
Google--not necessarily 'more open than thou'
advertisement

15 sites that went kaput in 2009

Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.

Top 10 news stories of the decade

Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.

About The Open Road

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to the Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is general manager of the Americas division and vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.

Add this feed to your online news reader

The Open Road topics

advertisement
advertisement
Click Here

Inside CNET News

Scroll Left Scroll Right