In reality, 60% of my time is spent on web design, but this effort is repackaged into two broader job descriptions: UX developer (requires heavy Javascript code) and web marketer (requires knowledge of analytics, SEO technique, conversion optimization, and a dozen other skills). Plus my frameworks pick up a lot of the lower level details of setting up and managing a web-page.
Not seeing a shortage of work in those two spaces....
1. TechCrunch 2. The New Yorker 3. BBC America 4. The Official Star Wars Blog 5. Variety 6. Sony Music 7. MTV News 8. Beyonce 9. ebay Inc 10. PlayStation.Blog 11. Best Buy 12. Xerox 13. Bata 14. Quartz 15. ESPN Product Blog 16. Nokia Conversations 17. Ford Social 18. Fortune 19. Time Inc. 20. Facebook Newsroom 21. The New York Times Company 22. Marks & Spencer for Business 23. Google Ventures 24. Harvard Business Review Blogs 25. Larry King Liveblog 26. The Official Rackspace Blog 27. Philips DirectLife Coach Blog 28. ExpressJet Airlines 29. Inside BlackBerry 30. Rotary Means Business – Rotary Club 31. The Rolling Stones 32. The Walking Dead – AMC 33. The Mozilla Blog 34. The Wall Street Journal Law Blog 35. Dallas Mavericks 36. Wil Wheaton 37. Snoop Dogg 38. SAP News Center 39. Wolverine Worldwide 40. Reuters Blogs
I'm also a software dev. I wouldn't say, when designing code, that "I make the code look nice" though, I'd hope that's at least part of it.
However... when someone is looking for a "designer," while it does include UI/UX (again, whatever that is ;) ) I've found they strictly only want someone who is good at making pretty things in Photoshop.
The process of making form follow function, maybe?
So, I guess "web designer" is very similar to "make it in Photoshop" and I should stop complaining ;)
It's reductive to conceive design as the design outcome, IMHO. If you have a guy doing all the UX work (alignment with business needs, research, gather data, analysis, IA, brand identity integration, etc.) and other guy which takes all this work and produces UI mock-ups in Photoshop, who did most design work?
The web was crafted by generalists. People who could think about both technology and design at the same time were hugely valuable builders, and leveraged to rapidly build up the content and tools of web from nothing.
Looking back, it was the wild west. We generalists were the rough and tumble pioneers that swung an axe and moved boulders, dug for gold, founded towns from dirt.
But now, it's built. There's no more frontier left to explore. The roads are cleared, railroads built, the land claims are well established, the towns have paved streets and public services.
10 years ago we web generalists were calling ourselves designers or developers but now we're engineers, product consultants. There's no longer a mad scramble to get a vision onto the screen with a designer, develop a new product from nothing. It's all about engineering to remove the flaws of the rough work done by pioneers, carefully looking at what's been established and tuning it so that it lasts.
I think some of us chronic generalists need to find a new frontier. This is just no longer our place..
http://blog.gardeviance.org/2015/03/on-pioneers-settlers-tow...
If you spot that new frontier do share - it's what attracted me to the web.
It'll either bomb or it'll be huge, the equivalent of the introduction of the smartphone or greater.
Maybe people just accept to meet inside the Matrix... http://hypescience.com/wp-content/uploads/2016/02/12719113_1...
Put it on your portfolio, and contact these companies and show how enthusiastic you are to enter the new VR frontier in your cover letter.
Unity doesn't require knowing how to program low level 3D graphics. You just need to understand how to import models (that you can find on their asset store), and some basics about 3D coordinate space and basic update/draw loops used in every game to move and rotate those objects over time.
You can go as deep as you want with it, but you could probably follow a tutorial on Unity and knock out something that proves you understand the basics in the span of a weekend.
Keep improving and adding new stuff onto your portfolio, maybe blog about what you've learned, and keep networking until someone wants to give you a shot.
That's basically how I broke into the game industry. It took time and passion, but I did it.
The part about Pioneers of the past being burned at the stake I'll hold on to. That's a truth that hangs on today, albeit with less fire and more firing
Perhaps I'm taking this the wrong way, but the tasks you listed there don't even begin to scratch the surface of existing design problems a UI designer will face on a daily basis.
EDIT: ex. Consider the design work that went into this product http://www.research.ibm.com/cognitive-computing/watson/watso...
One could certainly argue in either direction for all of those questions. The skills are all very similar, the technologies are mostly the same (foundationally).
I don't think work is drying up nor demand going down. I think designers are more important now more than ever, they just might not be traditional web designers.
http://www.webs9.com/wp-content/uploads/2012/10/Social_visit...
I've never head this referred to as a UI/UX engineer. You seem to have just described a web developer. If you're developing "large-scale apps" then you're definitely doing more than UI/UX, so why call it UI/UX engineering?
The JavaScript skills in question include the ability to write clean code, write unit tests and use client-side frameworks like Angular or React.
Having an eye for design and usability is a plus, but not the focus.
1. a frontend, which is a Single Page App, shipped as a blob of JS;
2. a backend, which is a big fat set of services in random languages.
The people who create the frontend are traditionally thought of as web developers, but "UI/UX engineer" is perhaps closer: they're engineering a program, yes, but it's ultimately a program entirely to serve the purpose of being a nice UI/UX in front of an API.
I think the most on-target name for this role would probably be "client-app developer." The client happens to be web-based, but that doesn't much matter. It's still a client that consumes your service.
I agree that there is nothing wrong with evolving the term "front end developer" into "UI/UX engineer". My problem is that the OP is talking about replacing "web developer" with "UI/UX" engineer. Web developer traditionaly includes backend engineers who aren't only working on UI.
Web developer is a broad term. UI/UX Engineer is a specific term. Yes many people specialize in frontend or backend, but both of them are still web developers. Calling both of them UI/UX Engineers is dumb.
I am proud to call myself a programmer or a web developer. Our work is hard, it's dynamic, and it has the potential to impact many lives. But we should be sensitive to the engineering community as lives depend on their work and calculations not falling apart.
On the whole engineering vs developing thing I think that dev is still in its infancy. Professional certs that are really meaningful and indicate some level of knowledge on various dev subjects would be a good baseline in the future, IMO. In Canada, to be a P.Eng. (https://en.wikipedia.org/wiki/Regulation_and_licensure_in_en...) one must, by law, be licensed.
From that link:
> The regulation and licensing of engineers are accomplished through a self-governing body that is given the power to license and discipline professional engineers, as well as regulate the practice of the professional engineers...
> A self-governing body's prime purpose is to protect the public.
Also, this discussion is a bit like asking why you can be a Data "Scientist" without a Ph.D. and without peer-reviewed publications. In reality, most people understand the difference between a scientist working in neurobiology or particle physics, and a data scientist working on ads (a competent data scientist working on a private non-profit in epidemiology might actually be harder to classify, though). So, same goes as to the difference between a civil engineer and a software engineer.
Edit: If anything, I know a few UX designers that reject the engineer label, but only because it makes the process sound more mechanical compared to designer (in my understanding, both are about discovering and satisfying constrains, but constrains are more strongly defined and more externally enforced in engineering than design, even for software).
> Is someone who makes electronic circuits, but is mostly self-taught, an engineer?
If he's accredited by that country's authority on the matter (e.g. the Engineering Council in the UK), then yes. If not, no.
Around here, you're only allowed to call yourself an engineer if you have a degree from a technical university.
Sure, the company can give you any title they want (I mean, if they're allowed to give obnoxious titles like Senior JavaScript Ninja or whatever, surely they can call someone an engineer, too), but from a legal standpoint, that's null, with all the consequences that follow (e.g. legal documents that require an engineer's signature have to be signed by someone that the state agrees is an engineer, regardless of what the company thinks).
Edit: FWIW, while I'm legally allowed to claim that glorious title (my diploma says "Instrumentation Engineering"), I tend to avoid it, too. My job has always been to program computers, and if I'll be able to do that until I retire, I will. Consequently, I see no reason to call myself anything other than a programmer. My employers disagree for paperwork reasons, so the paperwork they do says otherwise, but "programmer" is what I want everyone to call me. There is very little of true value to be found in a name; people who chase the title of engineer, rather than the engineering education, are missing the point.
When I think of "engineer", I think of P.Eng., and the licensing/accreditation that goes along with it has useful connotations to it. So I'd say while some of us devs might be doing engineering type of work, and may even be eligible for something like an P.Eng. license in their place of residence, they simply are not engineers, because they are not licensed.
On the other side of that coin, I don't believe there is ever such a hard-and-fast rule that is applied to the word "scientist". As such, I don't believe that Ph.D. or getting published is required - what's required is instead to be someone who practices science.
One day there will no doubt be real engineering accrediations, like peng for software, but we aren't there today.
I can't say I've ever seen dev jobs advertised as 'software engineer' positions here before. It's always 'software developer'.
Engineer simply means it's more code than Photoshop.
I prefer UI Developer.
The only thing you don't get for free with Drupal is a backend which you can speak to if you're deciding to go the SPA route later on.
Which, in my personal opinion, is a pretty stupid trend anyway. SPAs tend to grow to Java Enterprise levels of complexity very very fast, and things break All. The. Time. Not to mention you're putting huge amounts of work to the frontend, where you virtually cannot account for cross-browser behavior, people with multiple-year-old browsers... and people with devices older than two years!
Leave a Drupal project idle and unmaintained for a year, and you'll be able to pick up where you left it. Good luck doing the same with an AngularJS SPA - you might get away if you used npm shrinkwrap when you left, but the first npm update WILL kill your code with a billion possible places to fix.
Drupal is mature, and maturity is something that the entire Javascript development and tooling community is missing unless you stick to plain jQuery.
Stability and reliability IS a thing, especially in enterprise.
Go the hipster way when your target audience is hipsters, go the proven, old-school way when your target audience is enterprise.
edit: ad maturity of Drupal and support... D6 got released in 2008-Q1 and support ended in 2016-Q1. That's EIGHT YEARS of continuous support and security fixes, and I expect similar if not better support timeframes for D7.
Good luck finding a Backbone.js or Ember.js (and maybe even AngularJS) developer in four years from now; not to mention that during the entire D6/7 lifetime backwards-compatibility-breaking changes were a rarity in Drupal when all of the mentioned JS frameworks have had more than their fair share of clusterfucks stemming from bad design. Or just the tooling environment, breaking changes everywhere and (gut feeling) every month there's a new tool to learn or best practices revamped.
Wonder why PHP, server-side rendering and SQL is so prevalent? You can rely on buying a solution and having support and developers even in multiple years from now. Enterprise doesn't want ever-changing piles of crap layered in more piles of crap, enterprise wants stability and maintainability. And enterprise is where the money is, not some SV startup only surviving on VC or with 90% of its customers startups only surviving on VC.
If you want to ever have a safe upgrade path that doesn't involve months of testing then you absolutely need a type system, IMO. The only framework I've felt completely safe doing major upgrades on is Wicket - which, not coincidentally, is the only framework I've ever known to make extensive use of final classes and final methods (Java), to enforce that it's only possible to use it in supported ways.
Maybe I just have bad luck.
People see JS and throw their JQuery & some CSS developers at it. Or they use their backend PHP devs who've never written code that runs for longer than one request.
Either way you end up with code written by people who don't understand some of the fundamentals of UI programming.
Angular gets the worst of it because it's the most popular framework. It's exacerbated by the fact that Angular doesn't offer suggestions for a lot of common problems.
Proper error handling, sane state management, and keeping the codepaths short and easily grok'd is very difficult with Angular -- especially for larger applications. This results in blackholes where users find themselves in strange spots that are inescapable other than a full page refresh.
These are either developers dipping their toe into the front end after living in the back end of things their whole career, jQuery dudes hastily breaking into SPA development to stay afloat in an environment the submitted article exactly mentions, or simply lazy developers that couldn't be bothered due to tight deadlines/budget/whatever.
But if proper error handling, sane state management, and keeping codepaths short are actually "very difficult with Angular," maybe it's not the comprehension powers of the developers using it that are falling short.
A framework should be actively making those things easy.
React/JSX and TypeScript are a response to this and it's fair bit more pleasant when either of them are involved.
You are free to use jQuery in your theme (aka frontend code), or D3 for visualization, or any other JS stuff you may need. On a private project, I'm using a current jQuery, D3, and SCSS and it works quite fine for me.
The only thing in D7 that can be a major PITA is proper multi-language support, because it's a bit sparsely documented.
It might be a buggy insecure platform, but for non-tech savvy users it's brilliant. It doesn't make financial sense anymore to develop custom themes and designs from scratch. Large corps with their own branding is a different kettle of fish, but have fun trying to get on their preferred supplier list when you are a four person design agency.
Developing a one off, responsive, standards compliant website, that lookd good too, is expensive and clients don't want to pay for it.
We have a large content team and use WordPress across our company (several dozen websites) because it gets the job done for that content team. Our sites are ultimately just landing pages for ads and feed into our sales team as leads.
With our small 3-4 person devteam, we make our own themes and build into our WordPress sites all of the features that you'd want to host a site that's just content and a pipeline into our CRM (lots of handrolled plugins, custom functionality). We use modern ops practices (shoutouts to Pantheon for being a forward-looking PHP host) and write great code on a platform that's honestly not used to it. Some of the most interesting work that I've ever done.
As our team grows and our tools get more robust, we may explore using Wordpress to generate static pages for better performance. We also use other tools (Laravel, Rails, Node) when it makes sense to. Seriously though with good ops practices and developers who aren't lazy running the show, Wordpress can be a fantastic platform. This is absolutely some of the most interesting work that I've ever done.
WordPress runs 1/4 of the internet and not because 1/4 of the internet is cheap (though WordPress and PHP in general have fit that niche for a long time) - it's because training content authors to use custom/other tools costs money.
When someone is bemoaning the lack of work available I suspect the real problem is their inflexibility or technical stagnation. This is especially apparent when a novice roped in from the mail room can out-compete them and eat their lunch. The problem is the designer's skillset, not the industry trend.
The following anecdote is from my perspective as a Sr. Programmer. I've worked with many great designers over the last 10 years and this is an example of my worst experience working with a 'pure' one.
About 4 years ago I once worked with a designer who refused to break up a 60 meg psd file into separate elements I could use for buttons/background etc. I don't even have Photoshop. Her argument was she didn't know which layers/elements should be separated. She gave this to me the day before I had to have the site in prod. So I fired up gimp saw that it had 500 layers and just exported it to a jpg and used javascript imagemaps for the buttons just to get it out in time. This is after a week of work on another site they changed their mind on. I ultimately didn't get paid for any of my work and it was the last time I freelanced.
Primadonnas who do not put in any effort into learning basic technical skills to maximize their effectiveness can take a hike.
I've worked with great designers who were excited about the technical aspects of their craft. They understood that knowing what's possible makes them a better designer. Even when their graphic design degree did not provide them with any CSS training they quickly adapted because nobody has time to pass something back and forth moving elements around a few pixels at a time. I've seen more than one end up as great front end programmers and UX/UI designers. Even the ones who never quite got JS but embraced CSS were a great resource to have and made our sites look great. These are the kinds of people who make projects fun.
If jobs for people who consider CSS "beneath them" are drying up I say good riddance. Nobody has time for the overhead entailed from having programmers move elements around back and forth a few pixels at a time to please the designer who can't be bothered to learn valuable skills of their own trade.
The rule in technology has always been "Adapt or Perish" nobody bemoans the loss of COBOL jobs today for the same reasons people don't know what a "Printer's devil" is.
The article was about a move to in-house design instead of agency/freelancer work.
So when someone is bemoaning the lack of work available I suspect the real problem is their inflexibility or technical stagnation. This is especially apparent when a novice roped in from the mail room can out-compete them and eat their lunch. The problem is the designer's skillset, not the industry trend.
Of course, I’ve worked with many incredible web designers as well, and it’s definitely worth it for major brands to have a good design team. But that whole middle-lower-end market is probably just disappearing.
And we still see people trying to 'fix' the expected behavior of things like the scrollbar. Stuff like that is a huge waste of time on something that actually hurts the user experience and almost always breaks mobile or cross browser compatibility.
Many of these people have the wrong goal entirely because they think visually standing out is the most important thing. In print that makes sense, because you're trying to capture their attention while they desperately try to ignore your advertisement. On a website you already have their attention because they came to your website. And here's the Key, they came to your website to accomplish something, the designer ought to be trying to help the user reach that goal as effortlessly as possible. It's a bad idea for login links and fields to be anywhere but the top right. You put the cash registers near the exit of your store, Hiding them is a bad idea. Other funny analogies:
Why put those boring gender signs on the bathrooms doesn't everyone do that? It clutters up the doors and doesn't fit with our minimalist design language. Also, if we do that then they won't look like any of the other doors in our store.
We want our customers to feel like they can share everything with us so we removed all the bathroom doors and partitions between toilets. It'll even save you material costs!
Wheelchair access ramps are ugly, we don't need them.
I think an escalator should speed up and slow down depending on how fast someone is walking up. (scrollbar overrides)
I think having signs that announce the products in a particular isle makes the store too cluttered and busy, If we make them wander around aimlessly for the product they are looking for they will see more of our store and end up buying things they otherwise wouldn't have.
Just to clarify, I think standing out is great but not when it comes at the cost of usability.
This is partly true. Design problems have been solved for isolated cases. You still require designers to choose the right combination of solutions that work for particular use cases. And in my experience, all too often those "solutions" start conflicting with each other, resulting in new design problems!
Commoditization is definitely happening in design, but the design problems are not going away anytime soon.
Disclaimer/plug: I work on Squarespace design templates - http://www.square-mart.com
E.g. on a mature architectural design market, the need for design projects of small scale buildings almost vanishes. It's common that the design project is offered by developers trying to get the building contract. Only on large scale buildings still persiat the need for specialist design. In web design the same trends seem to apply:
designers -> builders
generalists -> specialists
Yes, there's a shift. But could it also be that, at the same time, work is also drying up? You speak of frameworks. Until recently we needed engineers to build the functionality of those frameworks; these engineers are not needed there anymore, but is there sufficient work left elsewhere? That is the important question, imho.
Software just get more complex and expands in scope when we can build on top of new abstractions.
I think there's plenty of work left in UI/UX but the "balance of power" with regards to base design has shifted towards software developers. I'm not very good at designing things and not too long ago I was almost ready to give up before getting started because I knew stuff would look ugly and I'd need a designer (wasn't easy to find good ones easily). These days you use bootstrap and a plethora of other tools and get pretty good results and then you can hire a designer to polish.
That's what I thought too until I tried to get the homepage of a web site designed. I'm using a popular "run a design contest" site with a higher bracket prize to try to attract good designers. Unfortunately, some of the crap the designers are turning in should be embarrassing for anyone calling themselves a designer :-(
Do you have a book / resource / something where this information is distilled?
Can you point me to a document for this?
Thank you.
https://www.nngroup.com/articles/overuse-of-overlays/
Then ux.stackexchange.com will undoubtedly have some useful pointers as well....
Although some tailored google searches will also help.
Back in my UX-only days, I used NN Group a lot in supplementing my own A/B testing - it was a bittersweet relationship, as they provide a suite of analytics-based trackers on many of the websites I visit.
https://www.smashingmagazine.com/2009/05/modal-windows-in-mo...
- A "web designer" or "web developer" used to be a generalist who wrote HTML, CSS, and some jQuery. Now there's a demand for specialization: a UI/UX designer who can prototype, iterate quickly, and use real data if possible, and a UI/UX engineer who can develop large-scale apps with an eye towards security, performance, reusability, and maintainability.
- The need for the generalist web designer/developer seems supplanted by tools like Squarespace and Bootstrap, which make it easy to get acceptable results with fewer skills. It's the "commoditization of design".
- The need for specialized designers/engineers is spurred by a realization that good design can command a premium/competitive advantage (and that good design means iterating quickly and having a deep understanding of what makes fundamentally good UI and UX), and that the front-end benefits from sound engineering practices as much as the back-end, especially if you're building SPAs or large-scale apps with complex UXes.
- A lot of the design problems have been solved already. Questions such as when modals are appropriate, how to design forms effectively, what makes a good call-to-action, and how to structure IA effectively have been answered. Companies no longer need teams of people to work out answers to these questions, just one or two good leaders to evangelize the answers that are already established, and a team of UI engineers that can execute them well.