Unless you’re just copying someone else’s design, UI design is not easy. Most would benefit from just copying.why do software programmers make bad design/UX? is it bad taste? carelessness? or complete idiocy?
I have seen website/apps that are pleasure to use and others that are complete horror. From a non-programmer POV I thought writing the code was the tough part.
As a developer, I typically make one of two kinds:why do software programmers make bad design/UX? is it bad taste? carelessness? or complete idiocy?
I have seen website/apps that are pleasure to use and others that are complete horror. From a non-programmer POV I thought writing the code was the tough part.
As with all kinds of design, there's a 3rd kind which is looks nice and is also easy to use, but that takes some thinking and good dose of inspiration.As a developer, I typically make one of two kinds:
1. The ugly but logical kind. Everything is where it "should" be, but it won't necessarily look pretty.
2. The kind where the marketing department has been involved. It probably looks nice, but good luck finding some of the features.
Unless you’re just copying someone else’s design, UI design is not easy. Most would benefit from just copying.
Aside from that much of the web is dead sites. Chances of response from an email through average business website is 50% in my experience.
In India, most businesses online presence is through WhatsApp!
As a developer, I typically make one of two kinds:
1. The ugly but logical kind. Everything is where it "should" be, but it won't necessarily look pretty.
2. The kind where the marketing department has been involved. It probably looks nice, but good luck finding some of the features.
In a country like India, almost everyone has a mobile phone and almost no one has a laptop/desktop. Just like how people set up shop on ebay/etsy, in India they do it on WhatsApp. Corporations create websites, but small businesses seldom have a web presence.I think there is a reason people still browse the web on desktop over their iphone.
In a country like India, almost everyone has a mobile phone and almost no one has a laptop/desktop. Just like how people set up shop on ebay/etsy, in India they do it on WhatsApp. Corporations create websites, but small businesses seldom have a web presence.
Some people. It's been a 50/50 split of mobile vs desktop (mobile includes tablets) for about 5-6 years or so.I think there is a reason people still browse the web on desktop over their iphone.
Thanks to the mobile first mantra. I hate that new style tsn. ca/nhl used to be my goto hockey website but since the re design I'm visiting it less and less.
Why not have one site optimized for a desktop and one for mobile? Like it used to be
@Boyd01, that's a great post detailing some of the real-world issues that could lead to what I consider to be "decreased function" in many of today's websites, apps, and operating systems.
Can you point to/share your site/app?
Revisiting this in the context of the post below it...You shouldn't have to build two sites anyway. The site shouldn't care one whit whether it's running on a desktop, a phone, a TV or a toaster. A browser is a browser. By all means, make things like menu bars "collapse" when there isn't enough horizontal space for them, but there's no need to redesign the entire site for different browsers.
Not sure that I follow how that makes a difference to building multiple versions? Just use dynamic styling with the same website to provide that experience. Whether it is an informational site or not makes any difference.Revisiting this in the context of the post below it...
The spanner in the works is when it's a "web app" rather than a "web site", and the line between the two can be very blurry. If the site is supposed to "emulate" a native (e.g. phone) app, then by all means make it look and behave like an iOS app on iOS and an Android app on Android, etc. My post was all around the context of "informational" sites, like the ones in the good old days 🙂
Thanks, I'll look for it.Thanks! I wanted to point out some of the things I considered in designing my own site, but I have to be mindful of the MacRumors policy on self-promotion, so I didn't post any links. You'll find one in my profile however.
Thanks I just did.You could start a thread about this in the forum feedback section if you want to call it to the attention of the staff.
![]()
Site and Forum Feedback
questions, suggestions, & comments about the site or forums; MacRumors announcementsforums.macrumors.com
We had proposed a hold-back to prevent lock-in at the platform level. Essentially, some percentage of the time, say 5% or 10%, the WEI attestation would intentionally be omitted, and would look the same as if the user opted-out of WEI or the device is not supported.
This is designed to prevent WEI from becoming “DRM for the web”. Any sites that attempted to restrict browser access based on WEI signals alone would have also restricted access to a significant enough proportion of attestable devices to disincentivize this behavior.
Those in the technical community who have expressed alarm about the proposal argue that the web should not be brought under a permission-based regime, where a third party renders judgment on the worthiness of users – without consultation, based on opaque criteria.
This grossly misunderstands what open source software is.The Web was always intended as an open platform. Google's proposal seems to be trying to authenticate that the browser hasn't been "tampered" with. How do you authenticate an open source piece of software? The end customer has the right to modify the browser as they see fit, and it should be none of the site's business whether the customer has done so.
"Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network." - Tim Berners-Lee
The Web was always intended as an open platform. Google's proposal seems to be trying to authenticate that the browser hasn't been "tampered" with. How do you authenticate an open source piece of software? The end customer has the right to modify the browser as they see fit, and it should be none of the site's business whether the customer has done so.
If you want a separate environment for certain tasks then that's fine, as long as it's a separate environment. The concern here is that the big IT companies are trying to mould the open Web into something it's not supposed to be.
Edit: Or, as The Register put it:
This grossly misunderstands what open source software is.
Signatures, developer signing and certificates are still a thing, regardless of if the app is open or closed source. You also do not retain the right to modify published open source software by default. You can contribute to the code base (this is the "open source" part of it), however the ability to modify the software legally falls under the publishing license. It has nothing to do with what open source is.