I said it was a great idea, and I had already implemented one. He could start using it today.
He promptly lost all interest in it.
(It turns out, on the complex plane the demand for native Java compilers is on the imaginary axis.)
From there, I can then start digging into what the real problem is. Maybe it was a desire for greater performance, or easier deployability. Maybe his concern was about protecting intellectual property, and he thought that binaries would be harder to reverse-engineer than bytecode.
All of those could be legitimate problems, and none of them would really be solved by a Java-to-native compiler.
Quite the contrary.
Excelsion JET, IBM, PTG, Aicas have supported native Java compilers since the early days.
Oracle added AOT compilation for Linux x64 to OpenJDK on Java 9, with the remaining platforms being supported later. The Java 10 fork, already has Windows and macOS support as well.
The Graal team recently announced the Polyglot VM, which is actually another AOT compiler for Java.
The demand for native Java compilers is going quite thanks to Fintech and embedded development.
Companies selling commercial native compilers for Java are still in business since the early days.
The trouble with a native compiler is dealing with dynamic class loading.
But that's all beside the point, which is people will often tell me what they want in a product, but don't actually want it.
There are/were a couple others, but the customer base is very... exclusive
Nitpicking, but that's not what OP said; they said she "wouldn't even consider looking at fontforge on her mac unless it behaved more like a mac application". That's different from affirming that she would be interested in it if it looked native.
Also friends are not reliable product testers. They might feel guilty saying "this sucks" or "there is better stuff than this". They just don't want to hurt you feelings. Even if it is someone you just met at a conference or even on the street if you talk with them long enough, you've already formed a rapport and they probably wouldn't want to upset you.
She was saying no and identified one easy to see thing she dislikes. There is no implication that it is only reason or that she has general interest in it. There is nothing to imply that she would even find the app/topic useful.
By anything measurable, the "I don't even look at apps that don't looks mac" have been absolutely honest and true. It did not however meant "the only reason I don't use it is UI look". That part was wishful thinking.
The account wasn't that his friend would use the software if. It was wouldn't use the software unless. Those responses imply different things.
This is a great example why user feedback needs to be taken in close proximity to a salt mine.
We, or at least most of us, being human, have a horrible job anticipating our future emotional state. So when his friend said that she'd be interested if FontForge was available on her Mac, she probably meant it, but her request didn't reflect the underlying reasons she held for not using the software.
Not out of dishonesty or malice, but because she probably didn't know herself. It's like all those times somebody swore they would love to have an app that frobnitzed the foobars, but when said app became available, it was met with a chorus of shrugs and mehs.
There's an excellent book on this topic -- The Mom Test -- that anybody building products should read.