|
Kevin Drzycimski wrote: Not everybody is a mobile app developer!
Right. And for devloping large Software Solutions, we use sometimes data services. If you have to include News-Feeds (e.g. for Update Messages), actual currency conversion and so on, external data services are a big advantage.
Author of Primary ROleplaying SysTem
How do I take my coffee? Black as midnight on a moonless night.
War doesn't determine who's right. War determines who's left.
|
|
|
|
|
Apps that use external data services can also be (and often start out as) desktop apps. Two examples: WeatherMate[^] and TakeStock[^].
/ravi
|
|
|
|
|
And not everybody is limited to using grunts and words with only one syllable
Sent from my BatComputer via HAL 9000 and M5
|
|
|
|
|
When it comes to externalize data we need to be willing to trust the source and in the special cases where it fails, that special case that screws everything, you have to have a fall-back.
Don't ever, ever!, trust 100% a data provider... always prepare, at least, one fall-back.
I already had issues, mainly with maps (all of them).
One of the applications I worked on had a module that depended on geo-location and at the end we had to support multiple providers to ensure 99% of coverage. 100% was impossible.
We knew this in advance, only didn't expect that it was going to be such a problem.
Cheers!
|
|
|
|