This is the same sort of application churn that was underway before the bulk of the PC market largely settled on MS-DOS and then on Windows, or the morass that

This is the same sort of application churn that was underway before the bulk of the PC market largely settled on MS-DOS and then on Windows, or the morass that was the then-current and then-far-more-fragmented Unix market, which led many vendors to support multiple then-current platforms. With the associated costs. Split your application into its core pieces (written in something reasonably portable, and kept modular where you can) and partition the rest into the platform-specific frameworks and calls, assuming that you can't find an analog to what was once called a "4GL" that meets your requirements and your budget. And from the last time that the third-party 4GL schemes and their sales-critters were prowling the areas I was then working in, it was easy to end up looking at Morton's fork choice. More than a few folks saw their "portable" applications locked into the 4GL frameworks and its continued development plans. Which wasn't a whole lot better than getting tied to the platform, if/when the 4GL vaporized, or raised its rates, or otherwise became less desirable. All common-sense stuff, of course.