How relevant is "random connection" script support?

Question

While smart customers were touted as a solution for “occasionally connected” terms of use, tools like Google Gears grew for the same reason. It seems to me that constant, reliable Internet access is becoming more common (even in places like commercial aircraft), so my question for the community is this: how relevant are solutions with offline support in the future?

I come closer to this in terms of a data intensive application like CRM.

Answer 1

Over the past 3 years, I have built 2 separate connected smart clients.

I found that adding "from time to time" multiplies application complexity (and development time) by about 3 or 4 times. So this is a very expensive feature to add.

But there are serious business cases for these applications, as I am sure that for many systems there are. One of them was for engineers on the road, who often visit client sites, where (for some reason, security is sometimes one of the reasons) their wireless connection does not work. The user still wants to continue to use the system the same way they were connected, and then effortlessly (for their part) synchronize themselves when the connection becomes available.

, , .

, " ", , , .

→ → .. , -.

, , , , . , - .

Answer 2

, . , , , . , , . , 3g , , .

Answer 3

Well, reliable Internet access is not as widespread as you think if you think globally. Even locally, Wi-Fi is not even so reliable, especially if you are moving from place to place. Building a time-related script provides more options for the user; I don’t think it was always required, but it’s pretty good. :)