I tested the sample, really it's very SIMPLE to use (unlike WCF after using for two years I still prefer good old socket) - but it charges "USD59 for 1000 credits" (I am still trying to clarify and confirm if one credit = one message)
But I want to ask, anyone has a better recommendation?
Firs of all - WCF, Socket are nothing related to WhatsApp-Api.
They used simple http post for communicating through the gateway.
This approach is very common and widely used for all SMS Service Provider. The reason is to give ease to developer to use HTTP Post rather than web service, WCF and others.
Second, credit doesn't mean number of sms. As SMS are sending worldwide, charges are different for each carrier. One sms can charge .4 or .5 or .8 whatever it is but in credits.
Last question, is selecting service provider. This thing you can google to get the best.
Don't always go for chaeaper SMS Provider. No guarantee in delivery. Better to choose well known SP. I use clickatell for many years and they seems to have good delivery. http://www.clickatell.com/[^]
This is Leor Zahavi. I want to learn mobile application development. I am just a beginner and having a very little knowledge about mobile application development. So please suggest me some tutorial and other sources from where, I can learn about UIT and SDK platforms.
We desperately need some help. We're having some terrible problems with a touch icon for Android. Everything works perfectly on an iPhone but we've been battling with Android for over a week and it absolutely refuses to work. The touch icon created on one Android appears pixelated and on another it appears very small.
Following Apple's guidelines we created the following touch icons - I've given the full URLs for the files so that you can see them - they're publicly available on a live web server:
We're aware that some versions of Android require the full URL to be specified so we've done that. We're also aware that some versions of iPhone and Android can't read the sizes attribute so we tried a default apple-touch-icon-precomposed.png file at both 144x144 and 57x57 but neither worked.
We suspect that Android might have some incorrect caching behavior because nothing we do can make Android change the favicon it is using (clearing the browser cache doesn't help). Even changing to a completely different image in the png file on the server it appears to be impossible to make Android change the image it uses - deleting the webpage link on the home screen, deleting the browser favorite, clearing the browser cache and re-creating the home screen link it still uses the same icon regardless of the icon file on the server.
The application has a favicon and we suspect that Android may be incorrectly using that instead of one of the touch icon files.
What makes the situation worse is that when we first tried this we didn't follow Apple's naming conventions and it worked on an iPhone and one out of two Androids. We changed to comply with Apple's recommendations in the hope of getting it to work on both Android devices. The above works on the iPhone but neither of the Android phones (on one the icon ix pixelated and on the other it is very small).
Hi,i'm a computer science student in just foundation, i'm absolutely new and still learning programming C#. I wish to program for ios, android, and WP8 asap as the market is growing competitive so can should i do in order to ensure i can developing great app??
As I said, you first need to decide which platform to start with and learn all about it. You can either follow the link I gave you and read some of the articles here on CodeProject, or use Google to find other relevant development sites, such as developer.android.com[^] for example.
One of these days I'm going to think of a really clever signature.
Unfortunately, all of the mobile platforms run apps in different languages, so you're really going to have to learn a great deal of things to cover that span. I have seen some people offer HTML5 (and other new web technologies) as a solution to the problem, I do remember seeing a video article here talking about using web technologies to present users with a good, consistent cross platform experience.
In my experience, it's always going to be an ongoing issue...
Last Visit: 31-Dec-99 18:00 Last Update: 26-Jun-16 3:52