PalmGear enables HTTP Post; kills developer fulfillment

PalmGear/Motricity has finally pulled the plug on developer fulfillment(aka developer sends code to customer per email) and the accompanying, much-ridiculed algorithm tax. Instead, Motricity now supports HTTP Post – a real-time process where a script on a developer’s web server is used to generate the reg code and dispatches it to customers.

This allows developers to keep their algorithms secret, but reduces customer’s wait times (and customer support efforts) significantly. HTTP Post has worked very well for me in the past, and I look forward to using it with PalmGear’s in the future!

Last but not least, here is the original announcement:

Greetings from Motricity

I trust that you are well and that 2007 has been a profitable year thus far. Many of our partners in the past have requested support for HTTP Post Fulfillment as a useable fulfillment method at PalmGear. We are pleased to announce that this method is now an option effective immediately! HTTP Post allows you to host fulfillment methods on your end exclusively while still providing Motricity customers with real-time fulfillment at the time of purchase.

Satisfying customer orders immediately is important in today’s marketplace. Moving forward, PalmGear will only support fulfillment methods that are real-time in nature. These supported methods include:

File (Full Version)
Static Key
Code Pool (List of Keys)
Dynamic (jCode)
HTTP Post Fulfillment

If you presently have listings that utilize a method other than those listed above, you will need to update your existing listings to accommodate the supported fulfillment types. This should be addressed immediately to avoid any gaps in support for your listings.

We have established a documentation area to assist you with setting up your HTTP Post Fulfillment should you elect to utilize it as a method. You may access it through your developer account, or directly through:

http://palmgear.com/index.cfm?fuseaction=developers.httppostdocumentation

(…)

Tim Tyndall
Manager, Developer Relations

Related posts:

1. Why MobiHand wants to discontinue developer fulfillment
2. Why I now use automatic fulfillment
3. PalmGear horror – there’s no way to part us from your app
4. PalmGear – the can of worms is open
5. Stiffed by Handango / PalmGear? Gang up!