>>>>>Why rewrite and port to a platform (be it Lianja or anything similar) that is a niche platform? For that matter, why rewrite at all? Your goals seem to be for a more modern interface, not a rewrite of your entire app. With something like FoxInCloud you can convert your VFP to HTML/JS/CSS and still maintain the ability to develop in VFP or HTML/JS.
>>>>>
>>>>actually having locally installed apps on tablets for medical is one of the larger markets IMO.
>>>>You don't want to be dependant on WLAN and Browser speeds when making rounds,
>>>>replicated and often synched local data sound MUCH better.
>>>>
>>>>> The only long term major not going anywhere platform right now is HTML/JS.
>>>>
>>>>Which Lianja conviniently supports as well. Coding the GUI in JS in Lianja might be the wisest way to stay "installed" and/or "browsered".
>>>>If vfp was still developed, FoxInCloud might be more of an option, but as vfp cannot reach ARM devices natively...
>>>
>>>
>>>
>>>"If vfp was still developed,..."
>>>
>>>Probably Lianja won't be in a few years either. They are a pretty small company, after all.
>>>
>>>The safest bet is to go big: like Microsoft or Google OR go Open Source. Small proprietary software tool companies that try to do it all are sooo last century.
>>
>>Uhmmm...we did "go big" with *Microsoft* Visual FoxPro and look what happened to it :)
>
>At least there was a product with good support for over a decade.
>
>The last VFP savior was what... eTechnologia?

All that I was saying is that "going big" does not imply "safest bet". Then again, in time, everything gets old :)