Be nice. Or else.
COO at Studio Projectie Joined over 2 years ago
Having no coding experience whatsoever as a designer is like writing a piece of music without being able to play it yourself. You don't have to play it yourself because there are better musicians for specific instruments but it helps when you understand 'how' the piece is going to be played.
One example is font rendering. Every time I work with an external designer with little to no coding experience they will use one of the 900 font weights in their designs. Edge / FireFox and Chrome each have their own way of handling 'bold' styles and in most cases the difference between font-weight 300 or 400 is barely visible.
This week we said to one of our interns: "Click on the floppy" She asked: "What's a floppy?"
I agree it's time to retire this icon.
Great read. I agree with almost every point you raised.
Some things that I would add to the list: - On-boarding process (put a on-boarding process in place for new employees) - Never offer discounts in your first offer - Don't do free work - Always get a signed contract before you do anything!
I'm quite a fan of XD but never used the set-up you propose. I mainly use XD to create a high-fidelity prototype and animations and such aren't added until production.
How is Lottie/Bodymovin these days? I remember trying it last year but finding it a bit cumbersome. Some AE functions are supported. others aren't so it got kinda complicated to figure out what would work. Compared to say a GSAP or AnimeJS solution the bar to get started was also fairly high. You need to be both an expert in AI, AE as well as in the basic concepts of SVG animation.
thanks for the advice. Good to hear you're not seeing what I'm seeing directly. At the office we're about 50/50 on this. Which I think is a bit too risky.
The risk with this is that some clients will mess it up even with a good design. It's not worth the risk in most cases I think. I remember cases when we worked our asses off including holidays to build something amazing. Only to watch our client botch up every marketing effort.
It ultimately depends on how much risk you want to take on.
Furthermore working without a contract also allows your client to walk away at any given time with everything you've created. They could walk a day before delivery even if you've already given them 99% of your work and not pay a single dime.
You can only do this if you a wide variety of references and with certain clients. If you give a speech to say a big banking firm and ask them: "What was this worth to you?" after you've visited their competitor. They will cough up a huge sum not to look cheap.
If you tell the local restaurant: "How much are you willing to pay?" they will say $1 for the effort.
I tried this once with a pitch because we had spend a lot of unpaid time preparing an excellent concept. They asked us for a quote on our concept and the full project. I told them, if you pick us for the full project, the concept comes free. If you don't want to go ahead with us, you can decide the price of the concept based on what you think it is worth. They didn't understand this at all, were offended that we would ask money for 'just' a concept while still in negotiation. When things settled down I explained to them that really any price would've been OK. They could have brought some beers to our office to make our designers feel appreciated for their work. Alas, in the end we got 0.
So unless you are famous or in high-demand at top companies I wouldn't risk it. I would pursue value based pricing instead. I've been implementing that and it works like a charm and beats charging by the hour any day of the week.
It would be a nice A/B test I think and I can already guess the outcome. Another visual cue makes people more likely to click. Especially in the era of flat design when a 'button' is often just a rectangle with a color. cursor:pointer also covers for designers that forget to implement clear hover states.
Great stuff, thanks for sharing. Was just looking for a way to fix some rubber banding issues on iOS
Experience matters but in different ways than most other professions. I think that if you learn the right problem solving skills it doesn't matter if you build a website in Divi, Webflow, Dreamweaver or code everything by yourself. It will be a good website regardless of the tools you use.
However, you need to spend some time to actually learn the tools and the process and improve your skills. Most of the sense of 'overwhelming' comes from folks who think that they can just learn how to build a website in 2 hours or turn their Sketch design into a perfectly implemented website within a day.
It takes time and people seem less and less willing to spend time to learn and/or build things. About 5 years ago when I started doing this professionally I spend hours and days debugging for Internet Explorer 8. Something that seems to have disappeared completely (thank god). As a front-end dev I think things have gotten way easier.
I also think at times we get too caught up in the process and tools and don't think enough about the end result. I mean, stuff like Sass or Less is not necessary and a static HTML page has little use for React or Vue. Just because the tools are there doesn't mean you need to use them.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.