| New ideas for MMwappush |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through November 04, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Lars Nielsen, MobileNation ApS - Denmark Frequent Contributor Username: Larsmservice Post Number: 286 Registered: 10-2003 |
i been spending a lot of time getting the most out of MMwp. As i use it it is a great tool for mobile marketing. But the days of WML are pretty much over and also the Iphone is here. Therefor i have a couple of suggestions that i hope you will read... #1 - The Iphone. The Iphone is here and with Iphone 3G the whole world will be Iphoning. But it does not handle wappush. When you send a MMwp it is in the shape of a wappush message. I suggest the there will be a GET-param that decides if the message should be wappush or sms. Example: "&MMmsg=wp" or "&MMmsg=sms", or true/false, whatever works best for you. The sms will contain the same content as wappush. From and the URL til the WML-file. I am quite sure that Iphone does not read WML which opens up for suggestion #2. #2 - The WML. I have written about this before. The file nowsms generates i a WML file. This should be changed to a Xhtml file instead. Or even better to whatever we tell it to be. Like: "&MMWaptemplate=bryce.xhtml" or: "&MMWaptemplate=bryce.php". The same rules should apply where nowsms requires certain strings to be present wrapped in "@@@@", like "@@from@@". That way we could bring MMwp up to modern standards. Thats about it. For now ;-)... I hope you take this seriously. Sometimes I think that i am the only one that has seen the great possibilities with MMwp. Hopefully others will follow ;-) All the best Lars [at] mobilenation.dk | |||
| Lars Nielsen, MobileNation ApS - Denmark Frequent Contributor Username: Larsmservice Post Number: 287 Registered: 10-2003 |
Suggestion # 3 which is VERY important... Please send yourself a MMwp. Look at the URL to the WMLfile. It should look something like: HTTP://yourserver.com:8080/20083930239/10/DA04877E.WML?ID=4500000000 Let break that apart... The important stuff comes last which is the GET params addaed o the WMLfile. ?ID=4500000000. Its the mobilenumber of the recipient. That is fine. Actually it is great. But... What if i wanted my own GET-param there? In order to bind the message with something in my database, i would like to add the ID- from my database. The params would then look at little like this: ?ID=4500000000&myID=45312 That way i could, when the user enters the page, read that and bind data to a unique ID in my database. I would then be able to deliver important relevant data to my customers. You could do cool stuff like read the useragent, etc, etc. and bind it to my ID in my DB. That would be cool wouldn't it? ;)Lars | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7624 Registered: 10-2002 |
Hi Lars, It is sad that the iPhone does not support WAP Push. This would be so easy for them to add. They will be adding a push notification service later this year, which should be very interesting, but you'd need to have a client piece of software installed on the iPhone to register for these notifications. We will have to wait to see how all that plays out. But I do agree it is a very important device. But that is off-topic. We did add the ability for the MMWapTemplate to be a content type other than WML. We base the "Content-type:" header that we return based upon the file extension of the MMWapTemplate. However, I have no idea when we did this. It isn't mentioned in the changes logs anywhere. But I just checked, and it is in there. It must have been added in response to your discussion in the following thread: http://support.nowsms.com/discus/messages/485/23597.html All this said, I do like the idea of the default template being able to dynamically decide between WML and XHTML. We already do this in the operator MMSC implementation when we are sending MMS to recipients whose phones do not support MMS (such as the iPhone). The message display page for the MMS message content dynamically detects whether to display WML or XHTML. Indeed, it would be a very good idea to do this for MMWAPPush. (We could probably do this for custom templates too ... allow them to have a block for WML and a block for XHTML.) I also like the idea of a parameter to send MMWAPPush as an SMS with a web link. This is an issue not just for the iPhone, but just about all content in the USA, where WAP Push support is far from ubiquitous. I don't know why we haven't done this already, but better support of the iPhone sounds like a good reason. For #3 ... that requires more thought. Your application won't necessarily see the opening of this URL. But what if we allowed you to include a notification URL in the MMWapPush request, so that when the user opened the content, we triggered your notification URL? | |||
| Lars Nielsen, MobileNation ApS - Denmark Frequent Contributor Username: Larsmservice Post Number: 288 Registered: 10-2003 |
Thanx for your reply Bryce. I am happy that you aggree with me on most issues. The Iphone 3G has launched now in many countries. I am guessing that it will rule ;-). From where i sit it is very important to be able to support the Iphone the best we can. The easiest way to do it, at least for me ;-), is to be able to send MMWP as sms, and to upgrade the MMWAPPUSH-Message so that it supports other outputs than WML. To me it sounds like some easy jobs to upgrade Nowsms to these changes, but again i do not know your code ;-). But i am guessing you guys could do it pretty fast. As for suggestion #3, your suggestion sounds fine. Hope to hear from you soon regarding these issues. The Iphone 3G has launched in my country, and many of my customers are asking me for solutions. I will be waiting to see if Nowsms can help ;-) All the best Lars | |||
| Lars Nielsen, MobileNation ApS - Denmark Frequent Contributor Username: Larsmservice Post Number: 289 Registered: 10-2003 |
I got me an Iphone now and have been testing a lot on it. Also i have tried to add a mmwptemplate in xhtml code with a fileextension in .xhtml. Nowsms v 5.51m generates xhtml code, but the fileextension is .WML which my Nokia N82 + N95, plus lots of Sonyericsson do not like. They all come with an error. As if they were expecting wml code due to the fileextension. So that does not work. However i do have a license for the 2007 of nowsms. It is still on our testing server and not on our live-server which i am using for these Iphone tests. So i am testing on v 5.51m. I will strongly suggest that you will do something about this problem. If my template is a .xhtml file, i suggest that you make the fileextension also in .xhtml, etc. etc. + return the right mime-type to the client phone. Next thing is the Iphone. The push they added to the new Iphone 3G has nothing to do with WapPush. So the Iphone still does not support Wappush or MMS. Clever or not, you decide. All i know is my customers are calling me asking what to do. So far i have recommended to move away from Wappush and send a sms with a link. The link should be as small as possible. Something like http://tinyurl.com/. Most phones today changes this link from the sms to a clickable link that opens the phones browser. My suggestions are based on being able to support the Iphone and at the same time make changes to nowsms users as easy as possible. Suggestion #1 Change the mmwaptemplate to support xhtml, html or other based on the template fileextension. Suggestion #2 When sending wappush(not that nescesarry) and MMwappush add a get-parameter to decide if send as wappush or plain sms. That's it. Nowsms is the best product in the market. Iphone is taking the world by storm. Let's make Nowsms support it as good as possible without making the nowsms-users change too much. The sooner the better ;-) All the best Lars S. Nielsen Mobilenation[dot]dk | |||
| Lars Nielsen, MobileNation ApS - Denmark Frequent Contributor Username: Larsmservice Post Number: 290 Registered: 10-2003 |
I know you guys are busy. But could we perhaps continue this thread? I think it's very important. Not just to me. ;)Lars | |||
