>>There are **lots** of good low barrier of entry solutions to building mobile apps these days with all sorts of options for any type of development.

Great- can you name one? Wanting a 4GL without Rube Goldberg complexity, assume not 100% connectivity, capable of munging data locally.

>>You can't possibly be thinking about running a fully self contained application with data locally on a mobile device? What's the point of that these days? All that means it that at somepoint you have to sync back to some central server meaning you still need to have a connection either way to run or initially get the data to run. Except for very rare use cases that model just seems a non-starter for mobile applications.

And yet I think I have a reason- though certainly I agree that if you've an answer to earlier question, I'll review carefully since it's coming from you.

/edit/ as an aside: don't suppose you have a Samsung phone? Mine comes with a health app that monitors 24/7 if configured, and optionally uploads results for aggregation and comparison. In my case, until I figured out how to stop the uploading it was comparing my performance to millions of men with similar health profiles. The monitoring has to work whether there's wifi/4G or not, and it does. When Samsung suggested that some of the monitoring would stop this month (apparently because one of the newer models lacks one of the sensors, so they thought they'd cover that off by stopping it on all phones) there was an outcry, which could suggest that this sort of thing isn't so oddball. I know how Samsung produced it, but it's strictly and purposely for their own phone which is not what I'm after.