{"id":390,"date":"2008-09-20T12:10:22","date_gmt":"2008-09-20T19:10:22","guid":{"rendered":"http:\/\/wapreview.com\/?p=390"},"modified":"2020-09-28T20:39:20","modified_gmt":"2020-09-29T03:39:20","slug":"t-mobiles-devpartner-program-live","status":"publish","type":"post","link":"https:\/\/wapreview.com\/390\/","title":{"rendered":"T-Mobile’s DevPartner Program Live!"},"content":{"rendered":"
To be sure, the new process is a big improvement over the elaborate dance that developers and publishers have had to do with carriers to get their games and applications on-deck. T-Mobile promises that the program, which features a click through online business agreement and application submission form, will reduce time to market from months to days. Although Dev Partner supports free applications I don’t think it will be very attractive to non-commercial developers for the following:<\/p>\n For paid applications the pricing model looks like it might be OK for at least some types of programs. Baseline revenue split is 50% to the publisher but can go to as high as 70% if the following criteria are met.<\/p>\n So while DevPartner is probably better than previous US carrier partnership deals it’s a far cry from Apple’s iPhone program which costs $99\/year including all testing and certification and gives back a flat 70% of revenue to the publisher. The DevPartner program currently seems to be focused on Java ME development only. On the “Getting Started” web page it does say you can submit Java or .cab (Windows Mobile) files, but in the detailed “Mobile Application Handbook” their is a requirement that all applications must be Java ME MIDP2.<\/p>\n The DevPartner program also does not cover Android applications. Android will have it’s own T-Mobile App Store and probably a separate developer program. I wonder if T-Mobile will try to enforce signing and certification requirements for Android apps? Google has been quite clear that Android security will not be based on application signing. That was reiterated at yesterday’s Mobilize conference in San Francisco, where Rich Miner from the Android team mentioned<\/a> the difficulties of the app signing model posses for small developers and consumers as one of the problems Android would solve. Rich called the current model “fundamentally broken” and said that device testing and signing was a problem even for Google, specifically mentioning how it was impossible to give Google Maps address book integration using Java ME on most phones.<\/p>\n It will be interesting to see what impact Android has on T-Mobile’s attitude toward signing and certification for non-Android applications. Will they perpetuate a dual standard, loosen up Java requirements or enforce signing on Android developer contrary to the Google party line?<\/p>\n","protected":false},"excerpt":{"rendered":" It looks like T-Mobile USA has flipped the switch on their DevParner Community. The program is designed to streamline the process of getting a mobile application approved and available on the carrier’s soon to launched App Store. You will need to register as a developer to be able to see the the program’s documents which include detailed requirements for testing and certification and a rate schedule. Registration is free but if you are a hobbyist or Open Source developer … Continue reading
\nIt looks like T-Mobile USA has flipped the switch on their DevParner Community<\/a>. The program is designed to streamline the process of getting a mobile application approved and available on the carrier’s soon to launched App Store. You will need to register as a developer to be able to see the the program’s documents which include detailed requirements for testing and certification and a rate schedule. Registration is free but if you are a hobbyist or Open Source developer looking to distribute a free application or game through T-Mobile I’m not so sure it’s even worth signing up<\/strong>.<\/p>\n\n
\n