If you're after native and you don't necessarily care whether it's in FoxPro code, what's your hold up then?

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. If you need to interface to FoxPro you can build a service API that runs alongside the app and that can be built as a Web application.

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.

Then again I don't understand why anybody would want to shackle themselves with a mobile app that has to be delivered and updated through an app store, when you can control your own application life cycle with Web hosted apps. Using tools like Ionic or one of the native flavors of React and Angular (NativeScript, React Native) you can build mobile look and feel applications and still take advantage of the Web for delivery. The only fly in that ointment is bloody Apple with their effect limited support for a real PWA experience, but even with those limitations it's still a viable option.

+++ Rick ---

>>>...without claiming for perfection, provides a safe path to progressively move a VFP desktop app. to a responsive Web-based app. We've faced a lot of skepticism, sometimes aggressive denial, however we could continue expanding and securing FoxInCloud with a handful of clients who've understood the benefit they could get from our product.
>
>Hi Thierry, I know we've had this conversation before and I don't need to be sold on what you're doing which is remarkably capable. I'm afraid I'm still droning on about Native apps. Not traditional browser apps, though using the device's HTML5 GUI rendering is entirely sensible, just as FiC does. Yes I know there are difficultles as people who have created browser apps since Netscape days will understand, but the point is that it is possible, as you've demonstrated. and yes, I certainly agree that there would need to be dollars or Euros attached if there were to be any hope of connecting this to interest in native apps.
>
>While you correctly observed last time that browser apps are prevalent, time goes by and I notice that most devices have a form of C++ and so does VFP now. I also see that many large and small online companies offer cross-platform local apps in preference to web apps, even incentivizing people to move from the web app to the local app. And yet, cross platform local app development seems fragmented and dismayingly Rube Goldberg. Every so often somebody tells me there's a fabulous new offering that can paint the house and walk the dog on every platform, but disappointed so far.
>
>So, I'm thinking that a local app using something with only partial or very early equivalence to Fox- e.g. Fox2.6 with a primitive UI of its own but able to generate exciting Bootstrap or whatever to be displayed on the device's own GUI, and OK reporting and good data munging underneath- could be as exciting/revolutionary as Fox2 was back in the day.
>
>Does it need to be Fox? No, Except that I'm not the first person ever to have this idea and there was a time when Fox tried to do cross-platform, hampered by the need to replicate UI for every platform. Fast forward to 2020 and I think we know somebody who has a much better way to achieve this. ;-) Also: while VFP quickly became Windows-only, earlier versions could run on Mac or UNIX with reported UI issues- which wouldn't matter if we're licensing your HTML5 cleverness, correct? - as well as DOS or a DOS emulator.... hmm.