Whether or not I'm using the right terminology, why should I take time to learn and then re-build and present something that would just basically be representative of interfaces that used to work awfully well ~7 years ago?
When you strip out all of the unrequired bumf from that sentence, you're left with a far more simple question. Which is just "Why should I learn?". And the answer to that is, you should always learn. Especially when the other option is shouting at clouds.
Actually it is not that silly;Sorry, your logic is so silly and just incorrect. If I’ve had great success with a local dry cleaner for 10 years and the owner decided to completely revamp the cleaning system to something wildly different and supposedly more efficient but resulting in a much worse cleaned product to me, I certainly don’t need to study how to dry clean in order to recognize and voice complaints about a noticeable degrade in resulting function for the services I’d gotten used to. it’s OK, you can joke about the clouds, it’s cute and may come across that way sometime to a person who disagrees with my sensibility and taste towards today’s interfaces vs., say, those before flat design and certain other arbitrary interface redos, but I’m hardly the only person out there voicing dissatisfaction over a few specific things that once worked up pretty darn nicely, whereas Jony never got his heavy-handed minimalist mitts on clouds. Why should he? They are already white and a really simple, there’s not much more for him to flatten, and he certainly couldn’t hide them behind a hamburger, gear, or ellipsis icon.
Actually it is not that silly;
You can objectively measure whether your clothing is cleaner using the new process or not. Just like you can objectively measure whether the new style applications are compliant with accessibility and responsive design standards or not.
What you seem to be arguing for is a subjective analysis where even if your clothes were measurably cleaner, you still argue that they are not due to the different way. It is a personal preference to do things a certain way, not an objective measurement of whether they are better or not. As long as that distinction is recognised, which I still don't get the feeling you do then all is good. ?
That just demonstrates to me that you don't understand what is really behind this. I never said to objectively measure this through like counting web hits. I specifically referred to compliance and standards. Counting 'web hits' provides an indication of how large the target market is, it does not provide an objective measurement as to whether the application developed targetting such a market is any good.Sorry, incorrecto. Sticking to objective measurements only like counting web hits from certain devices is exactly what got us into this mess of a compromised interface for those of us not working hours on a mobile device often. And sure, maybe said suit looks the same to you objectively, but you are not wearing it and unable to see maybe how noticeably abrasive/stiff and less comfortable it is than before, and even more worn and damaged at the inside seams you will never see as my usage profile for a suit may be vastly different than yours.
I just keep hoping this slow return to function over form keeps going!
Other than specific use cases I can not see a return to desktop only. But either way, there is an easy solution to all of this; don't use what you don't like!!
Pot calling kettle there palI’ve never, ever said I prefer and wish a desktop only interface across devices. If you don’t choose to read my posts fully then we can just keep playing ping pong or actually not.
Pot calling kettle there pal
As we've explained numerous times, there are standard and even regulatory compliance why mobile websites are the way they are. It is to ensure inclusiveness and access by all. As suggested by others you may want to look up and educate yourself on these topics as you still don't seem to acknowledge them.
A few years ago after iOS7 arrived I actually did look up Apple’s rewritten interface guidelines and almost threw up in my mouth at some of the things I read. if I weren’t reading it, I wouldn’t believe it. Honest to God I did look it up. The specific things that caught my eye had to do with focusing on something looking a certain way that just didn’t seem to be very intuitive at all.
Since you obviously know where such requirements are, I will kindly ask if you can point me to any inclusiveness or accessibility requirements for the following
There is your answer in bold1. Where is it required that a website must have a large hero image or video animation, where after The first or second time a user experienced an artsy hero image/video, it just feels like bloat and wasted space?
Again subjective2. Where is it required that differentiation between zones or information areas must be kept to a absolute minimum, we are, at its very worst, decreases the ability for intuitive recognition of the content? I.e., faint gray lines, if anything, between information areas such as iOS‘s contact or calendar apps, or instagram’s main feed, such that they are so faint (if there at all) they may will as well not even be there.
Now we are getting somewhere, but considering you still don't use the correct terminology despite several on this thread having explained it to your over and over and over again it is clear that you haven't educated yourself on this topic to understand the science behind it.3. Where is it said that thin, light gray or light tan font on a bright white background instead of black is a requirement which, at its worst, results in a much reduced function from being awfully hard to read for eyes older than 25 years, especially outdoors?
Any (all?) research regarding accessibility disagrees with you. But as per 3 we've gone over that so many times.4. Where is it required that an actionable item it must be limited to a word/text such that it can hardly be discernible from similar text on the page that is not actionable which, at its very worst, results and sometimes overlooking and available function that was hiding in plain site?
Again totally subjective. It is a branding exercise coupled with accessibility checks, you may not like it but the combination is proven to work.5. Where is it required that a website, app, or page should be arbitrarily reworked to white, light blue, medium blue, gray, and medium gray for the Best function and overall experience?
As you say, in your opinion. I'd love to know who those many are that a slowly reversing back to your stamp of approval for function-first.Not all websites or apps follow these poor, now-clichéd IMHO actions. But the worst ones do still, where few did before 2013. Luckily many are slowly reversing back towards function-first and away from blindly following a certain aesthetic-first. notice I’m not picking on responsive design. Responsive design, when not handicapped to be above minimalist clichés, can work well.
As you say, in your opinion. I'd love to know who those many are that a slowly reversing back to your stamp of approval for function-first.
Any (all?) research regarding accessibility disagrees with you. But as per 3 we've gone over that so many times.
It is not lawful actually. However, there are 2 things that are more important than the web design - the functionality and the usability. For that reason many prefer to buy templates and then to customize them.
Rant Over
Well summarised.Hardly a rant. Just truth being spoken.
I have been waiting for 7 years to hear or read one concrete example of why (and I'll generalize) "reducing the obviousness" of interface cues that previously promoted intuitive and almost instantaneous understanding/recognition was for an improvement in function and not just a change in appearance. Nobody can provide a solid answer because the changes are not better as a whole when considering the functional trade-offs. They were just to look different, catering to a crowd that needed something new and a few minimalist design "experts" willing to oblige. The proof in the reduction of function manifests itself in accumulated micro-pauses due to uncertainty as well as having to tap/click 2-3x to enact something that used to take 1 click. Those micro-pauses just start to add up to accumulated frustration from those of us who can't help but notice.
Flat design vagueness, small tap area text-as-buttons, low contrast light grey text on a sea of white, burying/hiding functions off-screen, vertical-heavy scroll fiestas just to take in what a given screen is providing...how are any of those functionally better than "before?" Nobody can answer.
Stay safe everyone.
Well summarised.
And another (not mine)
"How is it easier to navigate in a uniform, snowy landscape than one with a variety of colours and depth ?"
this is a old thread guys.
wonder where they come from?
Visited Lidl today (supermarket) - and parts were a bit like navigating a minimalist website.
So many shelves were empty (virus if anyone looks back and wonders ....) it was harder to find stuff.
Long runs of white shelves - with small black text on the shelf edge - a bit like navigating the snowy landscape.
Absent colour from packages or content, one had to get close and take time to examine shelf labels - instead of a quick visual scan for familiar colours and shapes.
Lidl has an own brand called "Simply".
Plain white labels - with the contents either in red or blue text.
Where it was the only product left on the shelf, close examination was required to identify it.
When shelves are full, one know what the Simply product is - by the colourful package alongside.
Who do minimalist web-designers think they are helping ?
Short answer: because it's double the work.
I have a feeling I’m in for a big disappointment, but I hope I am wrong. As an avid YouTube user, there’s not much to complain about at the moment. If things just wind up looking different and with a “cleaner interface” requiring more work to access what used to be right out in front, me not gonna be happy.