Earlier quoted context omitted.
What about going "back" INSIDE an application? Think for example reddit, you open a thread, how do you go back? You open the "reply window, now ho you ho back? Maybe close it directly? I Android this is all handled by the same function and is often ranked as the most frustrating design choice in IOS
There is a common way to go back (swipe from the left edge of the screen). Some apps just don't integrate well and ignore the platform patterns.
Microsoft hasn't had a coherent GUI strategy since Petzold
241–250 of 604 posts
Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#242Earlier quoted context omitted.
Being a 70's child, in computing since the mid 80s you made me almost spill my Monday coffee. What a laugh, do you want the examples on Apple's side?
The evergreen question of "how do you go back and/or close an app on IOS?"
This experience put a major dent in my perception of the "Apple has the most intuitive UI" narrative.
Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#243Earlier quoted context omitted.
Being a 70's child, in computing since the mid 80s you made me almost spill my Monday coffee. What a laugh, do you want the examples on Apple's side?
I mean Cocoa and SwiftUI are more consistent in the sense that a lot of stuff automatically adapts when Apple changes styling. And they certainly have less churn and more focus compared to Microsoft. Basically it's been Objective-C and Cocoa since around 2000, later on Swift and then also SwiftUI. That's not too bad for 25 years. And in contrast to MS, you didn't get abandoned when you were sticking to the official f…
The reboot of frameworks based in OpenGL with the Metal rewrite.
And many other things I am not bothering with since all those OS System N releases, A/UX UI framework, Teligent based documents,....
Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#244Earlier quoted context omitted.
The evergreen question of "how do you go back and/or close an app on IOS?"
I feel that some people are just too old to get used to the swipe based ui. I mean friends of mine who just keep buying the only phones with (screen based) back and home buttons.
It's not "getting used to", I feel like that gesture is less practical. It involves or using the "circle" to assist on how to use the gesture (creating a black void on the screen that you need to plan your use of the phone around) or having the swipe that 1) is not as reliable in my opinion and 2) can be triggered accidentally
For me is like claiming that touch screens on cars are the future and people are too old to get used to it.
Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#245Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#246Earlier quoted context omitted.
It goes back pretty far. Nowadays the controversy is electron vs native (where most windows devs would consider WPF/.NET a native option). But if you read books from the 2000s, there was much discussion about the performance overhead of a VM and garbage collected language; something like WinForms was considered the bloated lazy option. I’m sure in a few years computers will catch up (IMO they did a while ago actually…
What have you heard about SwiftUI being bloated?
Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#247Steven Sinofsky wrote this piece a couple of weeks ago about the same topic: https://x.com/stevesi/status/2036921223150440542
It's very amusing to see Sinofsky of all people all but dumping on .NET and (still?!) not understanding why developers so proactively jumped ship from Win32 & MFC hell to WinForms. Or why the HTML/JS app model in Win8 never really took off. I was in DevDiv during his great WinRT push and the overall feeling I remember was that the guys in Windows had zero clue as to what the devs actually wanted, but were hell bent o…
Yeah, he's talking about WinForms like it was a whole new thing, but it was a very transparent OO layer over Win32 and extremely similar both to VB and Borland Delphi. It was one of the reasons why .NET survived at all when Linux servers became the default option.
Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#248Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#249I never understood.NET's purpose. What problem it exactly went out to solve? Did Microsoft want developers to be able to run their applications everywhere too? Absolutely not.
Sidenote - MFC is the ugliest thing you'll see. Yet they didn't mention another piece of work called ATL. Active Template Library.
WinForms were really decent and that was enough. Keep Win32 API and a managed wrapper around it as WinForms and that would have been more than enough.
.
Re: Microsoft hasn't had a coherent GUI strategy since Petzold
#250Earlier quoted context omitted.
I mean Cocoa and SwiftUI are more consistent in the sense that a lot of stuff automatically adapts when Apple changes styling. And they certainly have less churn and more focus compared to Microsoft. Basically it's been Objective-C and Cocoa since around 2000, later on Swift and then also SwiftUI. That's not too bad for 25 years. And in contrast to MS, you didn't get abandoned when you were sticking to the official f…
Sure, if we ignore the stuff and bugs they still have, the missing features in SwiftUI and performance regressions, or the iPhonisms brought to macOS with Catalyst. The reboot of frameworks based in OpenGL with the Metal rewrite. And many other things I am not bothering with since all those OS System N releases, A/UX UI framework, Teligent based documents,....
There are just more people encountering them because the developers are concentrated on using one thing.
It’s not perfect, but a compared to Microsoft, calling Apple out for having bugs is a little rich isn't it?
I pose to you, if the Microsoft offerings are so compelling, why are the serious players using 3rd party wrappers like QT and Avalonia?
It’s because the first party offerings are not compelling. They’re a disaster dumpster fire. And buggy.