It's the same idea, yes - you need a user input event to unmute audio. However the difference is Construct automatically unmutes audio for you at the first opportunity. So you might not need a "click to start" preloader, unless you want to avoid sounds being cut off prior to the first input.
NW.js won't ever implement this - they've already turned off user input requirements, e.g. you can request fullscreen at any time in NW.js, whereas the browser requires an input event.