The Android instant messaging tutorial has been updated to help developers build a better user experience when starting the Sinch service. In the old version, users were notified via a toast message if the Sinch client had not started by the time they opened a messaging conversation.
Unfortunately, users had no way of knowing if the client would start a few seconds later, or if it failed to start. Now, when first logging in to the app, users will see a progress dialog (loading spinner) until the Sinch client starts, and then notify the user if the client fails to start. This is achieved by sending a broadcast intent from the messaging service to the activity, and showing a progress dialog of “Please wait…” until a broadcast is received.
It is also worth noting that most of the time, the Sinch client is started by the time the activity is created, so the progress dialog rarely is ever even displayed.
Since 1957, when a five-year-old boy with perfect pitch first phreaked AT&T switches and invented phreaking, phones have been a target for different types of fraud that costs customers and phone companies billions of dollars. However, if you’re using the… read more
Verification serves as an effective method for securing your user base, reducing fraudulent or duplicate signups, and for two-factor authentication (requiring user to be in possession of the phone during signup). Sinch verification products can be integrated into your Android,… read more
We’ve given you some of the reasons verification is useful and becoming increasingly necessary, notably: Phone numbers serve as a username with longevity Reduce fraudulent or duplicate signups Two factor authentication (require user to be in possession of a phone… read more