6 ms·

> (4/25) We needed to support working offline should the user go out of range of wi-fi. > (8/25) When offline, any actions that require a GET to the server res

by tl 12y ago

> (4/25) We needed to support working offline should the user go out of range of wi-fi. > (8/25) When offline, any actions that require a GET to the server results in an error message to the user. I would argue right there that you failed to deliver a product that met the user's requirements, and this sort of limitation is why I have to write native code when writing a web app would be much easier. > (21/25) Development team consisted of 5 developers, 1 business analyst, 1 tester, and 1 project manager (times 2 years for development time) > (21/25) Production code is 20K LOC of Java, 10K javascript. I'm not sure on what planet that is considered a reasonable level of output, but it must be nice there.

dangoor 12y ago
We don't know what the user's requirements were. It's possible that they minimized the required GET actions but that some actions required GETs because the data needed to be real time accurate. In-memory and offline storage are possible in web apps.
HolyHaddock 12y ago
Output should be measured by saving costs or new revenue, not lines of code written.
forgotAgain 12y ago
And it's a lot cheaper to over specify a cheap wifi network then it is to try to solve the problem with software in applications.
blatherard 12y ago
Regarding the need to do a GET when not connected: How would a native app solve this problem any better? Presumably, there's live data that sometimes needs to be fetched. If you're not connected you're not going to get that data whether you're in a browser or an app.
- robterrell 12y ago
  My favorite solution for this periodic offline/online access is CouchDB for mobile or PouchDB for html. But it's use would require another device between the back end CouchDB and their Oracle server.
prof_hobart 12y ago
Certainly better than a planet where effectiveness is measured in terms of number of LOC produced.
Cthulhu_ 12y ago
I wonder what quantity of code / time was spent on building their custom jquery-based application framework. Or maintaining it.

by tl 12y ago

dangoor 12y ago

We don't know what the user's requirements were. It's possible that they minimized the required GET actions but that some actions required GETs because the data needed to be real time accurate. In-memory and offline storage are possible in web apps.

HolyHaddock 12y ago

Output should be measured by saving costs or new revenue, not lines of code written.

forgotAgain 12y ago

And it's a lot cheaper to over specify a cheap wifi network then it is to try to solve the problem with software in applications.

blatherard 12y ago

Regarding the need to do a GET when not connected: How would a native app solve this problem any better? Presumably, there's live data that sometimes needs to be fetched. If you're not connected you're not going to get that data whether you're in a browser or an app.

robterrell 12y ago
My favorite solution for this periodic offline/online access is CouchDB for mobile or PouchDB for html. But it's use would require another device between the back end CouchDB and their Oracle server.

prof_hobart 12y ago

Certainly better than a planet where effectiveness is measured in terms of number of LOC produced.

Cthulhu_ 12y ago

I wonder what quantity of code / time was spent on building their custom jquery-based application framework. Or maintaining it.