Thanks Thomas, very insightful!

>IMO the best response in the thread, as dependency on requirements is stressed and not (only) best features, functions and use cases of different tools.
>
>I'd add as requirement dimensions (probably already considered, only not written down)
>- customer types, ranges, install and support typical problems
>- own strength and weaknesses: backend OS/security, esp using tools like PHP needing configs for me
>- option and ease of exchange to use different DB backends
>- typing more on static or dynamic side, usually connected to interpreted/IL compiled characteristics
>- grade of off-line capability: as you already mention native mobile, this is more between local data option, PWA-"mostly record typical" and no offline scenarios, where "record typical" includes selection options involving lookup arrays/cursors/tables and has its own range ;-)
>
>In your shoes I'd tackle first DB independance in vfp if not already adressed, then as as next step try to port/enhance to FoxInCloud or with close sibling like Lianja or xSharp (Dotnet implementation of xBase creating vfp dialect at the moment, quite interesting if Xamarin for mobile native installs vs. glorified JS (aka PWA)is considered or needed).
>
>In this "next step" focus more on cleaning up warts in your current code and architecture when something shows up in porting - so that future effort works from a better/cleaner code base, not from something fitted perfectly for both scenarios, but full of "code warts and architecture compromises"
>
>Then you are in a much better position to estimate or implement to radically different platform like server-Java based Cuba or a framework. Do NOT plan to clean up when moving to new platform - do it up front when you are working in well-known surroundings. Works better - for me at least ;-)
>
>regards
>thomas
>>I am actually going through an exercise right now to re-write a VFP app that I have had going for 15 years or more.
>>My requirements for the replacement are:
>>1. It needs to run on Windows, Linux, Mac (it could be a web solution for these) and be native Android & iOS
>>2. Could be run as SaaS or onsite
>>3. The development tool/environment needs to have good support
>>4. Development should be quick (provide some sort of framework where I need to pretty much only provide business logic.
>>5. Should be able to handle different cultures/locales
>>6. Should be affordable (preferably free :0) )
>>
>>I have looked at Low Code or No Code tools and Like AppGyver.com (free and promising) so far but I need to dig into it more. There are others out there like Kony - Quantum, Cuba.platform, Aware IM, Quixy, Caspio and lots more.
>>
>>I have considered Vienna Advantage, Alpha Anywhere, Servoy, Lianja, DevExpress XAF that are all, broadly speaking, development frameworks. Lianja looks good (if somewhat dated, but I guess that should be able to be changed) although I find the licensing confusing.
>>
>>I have looked at more raw development languages like X#, Xamarin, Flutter & dart, React, Go. I like Flutter and it can create apps on all platforms.
>>
>>I have also considered that the fastest way to get my app "in the cloud" will be to use FoxInCloud which I may go with initially and then start to re-write it in whatever tool I decide on.
>>
>>So, I'm hoping this turns into an active thread so I can get more opinions and ideas. :)