Yes, and no. It is a much simpler application. Two screens and three or four tables. I scaled back my ambitions a bit.
The soap box I'm on is that "mobile apps" make sense only to the extent that they allow an organization to move, not duplicate, certain functions away from the stationary desktop into a mobile environment. If the same task can be done either way, it's probably not cost-effective to "webify" it, or move it to the cloud, just for the sake of being in the cloud. If the task can be done better, more efficiently, or just plain uniquely, in the mobile environment, then the investment is worthwhile.
The example I used is a shopping list. I got the idea, in part, from the local grocery where I shop. I see employees with phones in their hands, walking around filling customer orders from a list on the phone. Customers order online, their orders are exposed in the phone app employees use, and the customers pick up the completed order when they get a text it is ready. I figured, I can do that too. Hence the PA Shopping List. To justify it, though, functionally, it would have to replace or reduce work I would normally do on the desktop. in Access. It does that, marginally, but it does illustrate the point. I moved the data input from my desk in my office to the phone, walking around putting things in my shopping cart in the store. When I get home, Access has the completed list displayed in a form. If I were not already tracking expenditures that way, it would be pointless, of course.
At some point, I hope to be able to incorporate the camera and get scans of product codes to do the lookup of brands, etc. No more typing on a tiny phone screen. Now that, would be awesome reduction of data entry.
