1) What is the relaitionship between:
https://devconnect-api.att.com/ and the Developer Dashboard.
I know that they are different, but It seems that they are two different places to begin the process of developing an app.
Response
Developer Dashboard is for a different service offering from a different platform using ParlayX SOAP API interface. That too it is only operates and shows your applications in the sandbox envirnonment. Once you have developed your application there is no automated promotion of your applicaiton to production environment. There is separate offline process for on-boarding your application to production enviroment. Moreover the endpoints that you would use to consume the services in the Sandbox env is different from the actual Production enviroment.
Whereas the https://devconnect-api.att.com is a new API platform that was launched recently which offers self-onboarding of your application into sandbox and self promotion of your applicatoin with just a button click. This enviroment offers simple and easy HTTP based REST services instead of ParlayX style SOAP interface. The endpoints that you would use to consume the services in the Sandbox realm and production realm are the same, you wont need to change your application code except for using the production API key, secret and shortcode that was assigned to your production instance of the application. By default when you create your application it would be in sandbox realm for your development purposes.
2) Issue with different phones.
After configuring a sample app1 (ruby) on my computer, I was able to send MMS messages using the api_key, secret_key, regristration_id and all that good stuff. I did get the MMS messages to 4 different phones (all ATT phones). However, the video only played on one phone. The phone on which the MMS worked is an iPhone 3GS. The phones on which the video failed to play are: Samsung Galaxy S, iPhone 4, Samsung Impression and a BlackBerry 8900.
Any reason why this could be?
Response
The reason is the MMS client applications in some of the newest smartphones are not properly handling the problems in the MIME attachments in your request. To ensure that your MMS is rendered properly in all handsets, we would recommend you frame your MMS requests using SMIL formatting. In our next release of the platform in some time mid of the year, we are planning to implement a feature in the platform gateway which would automatically do the SMIL wrapping if your application is not sending the request in that manner. But till then your application should plan to do that. We could help you in providing examples and also could provide assistance in doing that. I would request you to create a support ticket for that by clicking the Help button in the menu bar of https://devconnect-api.att.com site. Even in future on any questions or issues we would recommend you to create and submit a support ticket for quicker response and assistance instead of posting these questions in the Forum.
3) I only whitelisted one phone under the Deverloper Dashboard and it is not the one that works above. Am I still in the Sandbox? If I am why is it that I am able to send messages to apparently any phone?
Response
As I explained earlier, you are mixing up two different applications in two different environments. The whitelist is only applicable for the other older platform sandbox environment using SOAP interface so that you could send messages only to that phone. In the newer API platform, the sandbox doesn't restrict you to have any whitelist.
4) Even though I did about 20 requests I don't see any information on https://devconnect-api.att.com/MyApps. Shouldn't I see something?
Response
There is a delay to a maximum of 24 hours before you traffic would show up on the analytics/myapps page. The data is collected and aggregrated for a day and is periodically uploaded in 24hr interval.
