I know someone who uses FLTK for cross platform development. That one has a dated look too, and it's roots go back to that SGI Indigo Magic desktop I wrote about elsewhere in this discussion.

Sometimes it can be hard because people want to see the same GUI. And this is true even when it is input equal, I mean click to keystroke identical!

Most will say "modern" when they mean, "the one I drive daily."

And in many cases, those are one and the same. Modern simply is the daily driver, be it MacOS or Windows, or...

Doing that cross platform is hard!

With FLTK, a solo dev can write once, build for almost anything and it will work great. This is especially true for a C++ developer, which they are.

Over time, we have found building a modern GUI either takes a ton of time tweaking FLTK to look damn close, or it requires essentially different builds and dependencies, one set per platform supported, or...

Don't do it.

The thing is, we really value being able to bring the application to the user on their platform of choice. And today doing that is damn near free.

Basically, we just need to build FLTK on the target once, and the app will build with few to no problems. Easy peasy.

Users currently use Win 7 through 11 (yes, there are more of those out there than we may want to admit), Mac Intel and MX Apple Silicon, and a Linux user or two.

No Droid yet.

I wish it were different, but it isn't.

This tool seems high value because, like the other one mentioned here "dialog", which simply does the GUI in a terminal, command line tools are often the easiest, most portable build.

From there, one needs to adopt GUI foundation tools, which are specific to an OS, or like FLTK, look different.

Or, spend a ton more money, hire more devs and brute force cross platform tools.

I wish it were different. Is it?

Are we missing somethng?