To be honest UI dev tools just plain suck, making everything move more slowly that it needs to. If I'm on the web it's the HTML + CSS clusterfuck, If I'm in C# I'm writing color converters for WPF, if it's Java I have to use the outdated looking Swing, if it's C++ it's QT which I need to doll out cash for. Additionally every smart phone OS has it's own groundbreaking GUI layout concepts and ideas too. Then you get th…
Where will UX Design be in 5 years?
181–190 of 190 posts
Re: Where will UX Design be in 5 years?
#182Re: Where will UX Design be in 5 years?
#183Earlier quoted context omitted.
What do UI dev tools have to do with UX design?
Designs have to be implemented in something. Currently UX designers are often like chefs who work by drawing pictures of food and writing down conceptual recipes. When they've created a beautiful menu this way, they're surprised to find out that their recipes can't actually be made using the cooking equipment available, and some of the ingredients don't even exist. You're not going to run a Michelin-rated restaurant…
Re: Where will UX Design be in 5 years?
#184Earlier quoted context omitted.
Where did you read that? All I'm seeing is more and more ads in win 10 as time goes on.
Next, Windows video ads you can't block that only appear when you have a projector connected, chosen by adtech which reads your PowerPoint presentations.
Re: Where will UX Design be in 5 years?
#185In my pov, my job is first and foremost to understand the "problem" that a client communicates. The stated problem may or may not correspond to the actual problem that needs to be solved. This is especially true of semi-privatized, previously national monopoly working in infrastructure (like SNCF or EDF in France, Deutsche Bahn in Germany...) or service industries, but is also true for smaller mid-size businesses.
The stated problem might be something vague like "more digitalization", "being more competitive with with newer, smaller actors" (eg. SNCF/DB vs. Trainline/Uber) or something specific, like "redesign our website so it's more modern", or "design a new iOS/Android app.
The real problem might be: aligning internal departments on a vision (seriously, getting the heads of Marketing and Engineering on the same page is VERY hard at that scale); making sure that good ideas at the company don't get diluted and killed going through middle management; promoting innovation within a company (which then is translated to a website, an application or even a change in strategy, management, structure).
Sometimes the real problem is that the company just hasn't spent enough time (or money) to understand what their users'/client's experience in relation to their product (in context of their normal lives). It could be something as simple as clients not really knowing how to use the product properly, being frustrated because they had to wait too long, not knowing which option to pick or pressing on "like" just to find a post later. It could be that clients absolutely love a small detail that wasn't meant to be very important. You learn a lot about just talking to people and asking questions.
So, depending on the type of project my job as UX Consultant is to:
— coordinate ethnographic interviews (mini-ethnographic maybe; the idea is to learn from real, in depth conversations) with either clients, potential clients or internal management
— organize ideation/innovation workshops (two goals: come up with new ideas AND get different departments and levels of management aligned on the same vision)
— map out customer journeys and create personae (with the client) so that we're able to empathise with real users (not always relevant; there's a risk of doing meaningless work if done because this it something that was sold, but when used properly can be really useful).
- translating these insights/findings into strategic recommendations or digital objects (app, websites)
- designing wireframes to concretize ideas and encourage discussion/debate
- working on high-fidelity interactive prototypes to pass on to developers (who might be working client-side)
- designing and organizing usability tests (and A/B tests) when relevant.
So that's how I see it.
Of course, there's also that part of UX which is to create addiction, increase "engagement" or encourage certain behavior (increase newsletter signup). That's not really my thing.
Re: Where will UX Design be in 5 years?
#186To be honest UI dev tools just plain suck, making everything move more slowly that it needs to. If I'm on the web it's the HTML + CSS clusterfuck, If I'm in C# I'm writing color converters for WPF, if it's Java I have to use the outdated looking Swing, if it's C++ it's QT which I need to doll out cash for. Additionally every smart phone OS has it's own groundbreaking GUI layout concepts and ideas too. Then you get th…
Sun NeWS should have been that GUI standard, thirty years ago: https://en.wikipedia.org/wiki/NeWS There was a simplicity and purity in its approach to front-end interactivity and rendering that completely eludes the HTML+CSS+JS stack we're now stuck with. As the Wikipedia article states... "NeWS was architecturally similar to what is now called AJAX, except that NeWS coherently: used PostScript code instead of JavaSc…
https://www.usenix.org/legacy/event/usenix2000/invitedtalks/...
Re: Where will UX Design be in 5 years?
#187Earlier quoted context omitted.
Yes. But this is far far far away from "designers must code." Except for a few unicorns, this just leads to people who are mediocre at both design and code. A designer who is bogged down in code will also produce bad designs, especially when they let their inability to think of how something will be coded (because they aren't advanced coders) limit them! Designers have their own tool chain to prototype UIs and user i…
I'm not advocating that designers should code -- far from it. I wish they had better tools for modeling user experiences. You mention that designers have their own toolchains for prototyping, but these has nothing to do with UI dev tools. I've often wondered why this would have to be so. Look at other advanced design fields like architecture and industrial design. It would be unthinkable today that professional archi…
> Why can't we have the same in software?
Because devs and designers have different needs.
Re: Where will UX Design be in 5 years?
#188If I could express a desire rather than a prediction, it's that "undiscoverable" UIs die. I hate having to swipe and tap and generally mess with the screen in the hope of triggering some secret feature. I don't know when it became trendy to get rid of UI chrome but I really wish it would come back. (I wouldn't mind if the hamburger menu died either.)
I doubt that mobile screens will get bigger. The resolution will increase, but that just means that the few over-designed details that are shown will be crisper.
Re: Where will UX Design be in 5 years?
#189To be honest UI dev tools just plain suck, making everything move more slowly that it needs to. If I'm on the web it's the HTML + CSS clusterfuck, If I'm in C# I'm writing color converters for WPF, if it's Java I have to use the outdated looking Swing, if it's C++ it's QT which I need to doll out cash for. Additionally every smart phone OS has it's own groundbreaking GUI layout concepts and ideas too. Then you get th…
As a designer I can tell you right now = solve this problem and make lots of money as an engineer. If you need help, PM me, I will list you all the clusterfucks Adobe has made trying to solve this problem.
Re: Where will UX Design be in 5 years?
#190Earlier quoted context omitted.
Out of interest, which platforms that Qt targets, cannot have dynamic linking?
Embedded devices, car infotainment systems, iOS (only dynamic frameworks from Apple are allowed).