Commentary

Details Emerge About Verizon's Any Apps, Any Device Initiative

Verizon Wireless is hosting developers at an event in New York City this week where it is sharing details on its Any Apps, Any Device program. It's promising quick turnaround for device certifications and should have the program up and running in the second half of the year. Will this really usher in new user freedoms?

Verizon Wireless is hosting developers at an event in New York City this week where it is sharing details on its Any Apps, Any Device program. It's promising quick turnaround for device certifications and should have the program up and running in the second half of the year. Will this really usher in new user freedoms?I question Verizon's true intent here. From the way Verizon is presenting the process to developers at the conference, you'd think there are hundreds of anonymous gadget makers out there just itching to build a better version of the cell phone. I have my doubts about that, but let's shelve them for now.

Here's how it is going to work.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Developers build their devices and send them to Verizon. Verizon promises it will take no more than 4 weeks to test the device, and of course there is a fee for testing. It will be returned with a pass/fail stamp. There's no in-between. Verizon didn't say if it will offer pointers to developers to let them know where the weaknesses are. If the device passes, the developer needs to register it and it will be given a serial number. Sounds straightforward so far.

If the developer wants to sell the device, he/she has a couple of different avenues. The developer can retail it on their own, with all the related expenses their burden to bear. The developer also is responsible for any tech support related to the phone. The developer also can choose to become a mini-MVNO by buying minutes at wholesale prices from Verizon and then selling the minutes (and device) to you. Verizon also is working on a custom model for accommodating custom wholesaler businesses.

At this point, if a consumer buys one of these approved devices, they will need to activate it online. Here is where you will be guaranteed a working device. You will have to enter the serial number registered to the device. If the serial number isn't registered with Verizon, the device won't receive network access. If the device is bought via the wholesale model, the seller will be responsible for activating the device, just as it would be in any regular Verizon Wireless retail shop.

Once everything is activated, customers will presumably be able to download whichever applications they choose and also can select the extent of the relationship they desire to have with Verizon. That means there are no contracts, and no early termination fees.

How soon will all this happen? The certification process will be up and running by the end of this month, and the entire shebang should be operational in the second half of the year.

OK, this is great. But how many developers are going to jump at the opportunity to make devices to access Verizon's network and then sell them? Is it going to be worth it for the developers? And what about the user? Yes, they get access to Verizon's network on a device they (presumably) really want to use, but what quality assurances do they have? How far will the mobile ecosystem really go to support these nonofficial devices and applications?

For the moment, all we can do is wait and see.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links