What is the question? Is there a risk on relying on third party web services? Sure. However if your app requires such a service then you need to rely on it.
Relying on Web services always has a level of risk. No matter how reliable the service is. If the device has no net connection then the service won't work.
In my experience a bad or no net connection is the killer. I think a bad connection is actually more of a problem than no connection as it's far more frustrating for the user. Not sure if it's even possible to measure 3G/4G QOS on Android. If it is it would be a great facility to have in B4A.
There are APIs out there that are web based only, yes, they depend on internet connectivity but it's the developer's responsibility to incorporate an error control routine into the library to notify the user about any communication issue.
There' s no risk using an online API, the only thing to keep in mind is that the provider should be a reputable source to assure that the API won't suddenly disappear.
There are APIs out there that are web based only, yes, they depend on internet connectivity but it's the developer's responsibility to incorporate an error control routine into the library to notify the user about any communication issue.
There' s no risk using an online API, the only thing to keep in mind is that the provider should be a reputable source to assure that the API won't suddenly disappear.