4 ms·
Man. I immediately dropped what I was doing to see if I could send or receive an MMS from my laptop. The documentation and sample apps do not make it easy for
by jeffclark 14y ago
Man.
I immediately dropped what I was doing to see if I could send or receive an MMS from my laptop. The documentation and sample apps do not make it easy for someone to figure out how to actually do that.
- akalsey 14y agoAT&T does have some APIs for interacting with MMS. Those have actually been around for several months. The MMS API they offer at https://developer.att.com/developer/basicTemplate.jsp?passedItemId=13100102&api=MMS&version=2&method=&provider= https://developer.att.com/developer/basicTemplate.jsp?passed... is restricted to working with AT&T mobile numbers only, though.
- johntdyer 14y agoHey Jeff, Did you check out the sample applications, they have a pretty well documented example ( https://gist.github.com/3125729 https://gist.github.com/3125729 ) -John
- jeffclark 14y agoThanks for the reply, John. I did check out the gists of the apps, so I guess it's only fair to explain why I'm not a fan yet. In the "download sample apps" gists, you don't actually include all the files: where are the views? Where is the public directory? Clearly, someone could create these themselves, but when I click a link to download the sample app, I want to download the entire sample app and not just selected files. I don't want to spend time debugging what's missing. In the MMS sample app2, there are files for phone number lists and a "tokens" file. But you'd have to go directly to the github repository to find out what they're used for and how to use them. (I'm still not sure how/what "tokens" does.) I appreciate the amount of work it takes to release a public API (and one as robust as this), but it's just kinda .... AT&T-y at this point.