If you can’t tell the difference it doesn’t matter and I wouldn’t worry about it.
Electron apps typically don’t work for me because they don’t integrate with the rest of the system cleanly, and so once you stray off the designers’ happy path it becomes clumsy to use the app. This isn’t an esthetic or ideological argument; simply for my usage an electron app can rarely be as convenient as a native app on the Mac. Things like input integration, system service integration, selection, and responsiveness are much harder to do when you are fighting the electron abstraction, so no wonder devs leave those things out.
Just because a user can't tell the difference doesn't mean we shouldn't call out the fact that it is. Electron apps use way too many system resources. For lower powered devices, this becomes an issue.
Generally a massive bundle size, and/or inspecting the bundled frameworks themselves (right click on app -> show package -> browse folders for frameworks).
Poke around the application bundle or its supporting files directories. On macOS, the Electron.framework folder will typically be somewhere inside of the .app bundle.
