But I do agree on making sure standard hot keys work. Ctrl/Cmd+C better be copy and Ctrl/Cmd+V paste!
And there you run into issues because the Mac has 3 modifiers - Windows has 2 
( at least I cant think of any app that might use the Windows key for anything IN the app - are there any ?)
Cmd, Opt & Shift on macOS
On Windows there are Alt & Shift
You should have seen the spreadsheet I had to make to set up the shortcut editor in the Xojo IDE
Had 3 major sections (Mac Windows Linux)
And each had multiple columns for the modifiers & short cut key
And then listed out every command that was attached to a menu
It took while to get things all set up, try REALLY hard not to use some System wide short cuts, and keep them consistent, and sensible
1 Like
And Ctrl and Win key
I don’t associate this with coding skills so much as with computer literacy. Neither “software developer” nor “power user” really captures it. I think Norm is right, muscle memory counts for something and it would be relied on for productivity by, yes, devs and power users but by anyone who does a lot of keyboarding throughout the day.
It may be that as time goes on people will expect things to be consistent with the dominant browsers of the era even on device OSes, but until then I think it is platform specific.
I will say however that I have (sort of) managed to get used to switching between Ctrl-C and Cmd-C by virtue of doing most of my work on Windows Server via RDP but then running the client on macOS. So if I want to copy something from the work computer to my personal machine I must Ctrl-C, switch to my local desktop, and then jarringly, Cmd-V. This forces me on a minute to minute basis to constantly ask myself, which machine am I controlling? But in some future world where I quit or retire from work, I will release that cognitive load and then will take great umbrage to any macOS app that uses Crtl-C / Ctrl-V no matter what the rationalization.
1 Like
Right
Mac cmd ctrl option shift
WIndows ctrl alt shift
Cant say I have ever seen an app use Win key
Doesnt mean they dont exist I just cant recall any
Really the upshot is some people, not just devs, expect apps to behave consistently with their experience on the platform. They expect the same short cuts and operations in similar kinds of objects to work the same. text Fields on macOS should use the same kinds of word forward, end of line, etc as other apps that also edit text.
Some expect them to look the same - dark mode on macOS for instance should obey my system wide preferences.
And some want “the same app everywhere”
Being able to accommodate either is nice
It was a Type, thanks for this. I corrected it.
I know that phaenomena from exactly the other side: while Software behaves on all platforms the same customers said that it makes it less complex to use it on the different platforms. Also the IT-Guys of the customers loving it: while it has always the exactly same behavior the support is less complex. They said.Before I get hanged on the next Treeview .
I used to have native look and feel as a requirement, which is why I went with Xojo. But then there were web apps on the desktop (Electron), web intermingled with native, and then multiple generations of native UI toolkits (especially on windows). Users can hardly tell what native is anymore, nor do they seem to care (unoess they are a reviewer, apparently). I think the main place it matters is in expected native things like file dialogs and key features like the menu bar on the Mac. Beyond that, functionality for the user and clean looks. There is something to be said for consistency across platforms as more users like myself use both Mac and Windows.
Different requirements for different customers
Its what keep life interesting
2 Likes
I acknowledge that my perspective is probably a little dated. I’ve been in the bowels of one company for 15 years, doing back end work, and haven’t dealt directly with end users in that time. Things probably are changing as you describe.
any more thoughts / experiences now MAUI is a little more older?
Not from me … still busy doing command line stuff so haven’t had to do a deep dive. Bit of reading. I mentioned the open source Avalon framework as another possibility in a different thread here.
Frankly I am confused about the direction MSFT is going with MAUI vs Blazor … I’m not even sure the word “vs” is relevant … Blazor is the claim they are staking in the WASM space so strictly speaking it’s probably more of interest to large corporate development efforts, not commercial stuff so much. WIth MAUI you are doing something like what Xojo claimed to be working towards; with Blazor you can do more of an Electron-style approach … with Avalon you can have a more opinionated pixel-exact sameness on all platforms rather than use native controls like MAUI. That is the 30,000 foot overview as I understand it.
1 Like
I was writing just a small app with it. Not so successful but I guess I have to work through a few more tutorials. I am not so deep inside of portent and so…hard work