Where the design community meets.
Seattle Independent Product Designer Joined almost 9 years ago
Joe hasn't posted any stories yet.
Every single point in this article is a way that floating labels commonly fall short, but all of these potential problems can be accounted for and fixed.
hints could appear on field focus, then go away once the user starts typing, like hints normally would.
Make sure the text is large enough to be readable.
Make sure there is enough space for the labels to move into.
Keep animation to a minimum and ensure that it adds value, not just ornament.
Make sure they have enough contrast to be readable.
Style the input text differently than the placeholder label so it is clear that a field has been filled
For radio buttons, he makes a good point. bBt dropdowns could still have a placeholder label if you don't have a default pre-selected.
Keep label text short
That said, the primary benefit of placeholder labels is to reduce vertical height, and to make an unfilled form feel less complicated. Sometimes those things are not a huge concern.
In WA, but for health insurance, I have a high deductible plan through the state exchange. Its $200/mo and covers an annual visit and not much else, but it'll keep me from going bankrupt if something bad happens.
For the business, I use Hiscox, which is about $60/mo.
The whole concept is that 'dudes' need a special calendar because they are idiots. It is built around reinforcing gender stereotypes.
It isn't about girls wanting their own version. Why does this have to be gendered at all? What is the point of that other than saying "haha dudes can barely take care of themselves"
Slack has single-channel and multi-channel guests, where they can only see channels they are invited to. Not sure about basecamp though, havent used it in a long time.
Is the expectation that a candidate would download the app to be able to talk with a recruiter? Or does this send via sms?
If the candidate has to download an app to talk with a recruiter, I'd think it would lower the quality of candidates right from the start. I know that I would be pretty turned off if a recruiter sent me an email suggesting I download some new app so we could continue talking. Like, why not just keep using email? Is it really worth it to make it more difficult for me to talk with you?
Should writers code?
Yes, absolutely! (Sorry just noticed the reply notification from a month ago)
And if you're writing production quality code for a framer prototype, you're wasting your time. The whole point of prototyping is that it is much faster than actually building the thing. It should be hastily written code that is all copy/pasted and Frankensteined together.
In fact, I'm not even convinced Framer is the best tool most of the time. It certainly gives you a ton of power to create dynamic, complex prototypes, but something like Principle takes less than half the time and has 90% of the fidelity of a Framer prototype.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
I wouldn't like that either, but competition is good. I don't think Sketch would be updating as frequently as they are if they didn't feel the pressure from Figma. If Sketch bought Figma, the gap between XD and a combined Sketch/Figma would be so wide, it would kill any real competition, unless Adobe really stepped up their pace. If Adobe bought Figma, the gap between XD/Figma and Sketch would be narrowed, and there would be more of a threat to Sketch's dominance.
For many years, Adobe was the only real game in town for design software. Especially after they bought Macromedia. Because they didn't feel any real competition, they didn't make any dramatic moves. No major new apps, just new features. Its great that they are working on fixing that with XD, but it is only because of Sketch and Figma that they are doing it.