Where the design community meets.
Ho Chi Minh City, Vietnam Chief Design Officer, Quoine Joined over 5 years ago
Well, what do we mean here when we say "banners are about" marketers or designers - or - designers/ marketers are "responsible" for banners?
The vagary in this set-up sounds like a source of the problem.
There should be a clear delineation of roles, responsibilities and deliverables when doing marketing design and collaborating with marketing stakeholders.
It sounds like the process is broken and designers have no say/ control in the process in some scenarios.
The first step to me is simple. It all starts with a brief that is written by a marketer, which is a subset/ tactic of a marketing strategy. Where does this banner deliverable fit into a campaign? What are the other contingent tasks? Rarely is a banner created that exists in lone isolation.
I don't know how many garbage marketing design briefs, say for banners, I've seen over the years. "Copy" that is a pile of "whimsy and clever" word soup and ill-respective of the limitations of the medium at hand. Image requests with no image acquisition budget. People playing arm-chair decorators with zero regard for brand and communication standards. No strategy for testing and scaling up or down the campaigns and so on.
Thus, you can continue to receive garbage briefs (if at all) or you can drive the process, educate and receive well done marketing design briefs and requirements that you can translate into designs.
If they can't write it clearly, how can they expect you to read tea leaves and "design it". So, get the requirements.
Finally, the actual feedback and iteration process is up to the designers to drive and educate marketing stakeholders in order to set them and everyone up for success. Create a "feedback process" - that is loyal to your brand and design system standards, which effectively neutralizes any deviations.
This update looks enticing. I tried ProtoPie back when, cool product. Learning a new interactive prototyping tool, implementing it into your processes, particularly with interactive prototyping - is no small task.
Thus, 30 days to try doesn't seem like a long time and I'm sure like many others - there's subscription fatigue. The feature restrictions between Individual and Team seem a bit arbitrary. "Interaction Recipes" would entice me to try as an individual and perhaps eventually upgrade, but it's not an option..
Perhaps individuals and smaller teams really aren't the audience for this product?
I'm not sure "good or bad ux" is the right way to frame it. This is a security issue first and foremost.
I think it's more about locking the account after 4 failed tries, and is this a good and effective security practice?
And if so, what industries and applications should embrace this approach, are there any possible affordances, and in what industries and applications is this overkill?
And, if not, what is a better or smarter approach for user authentication that is secure, more tolerant of user mistakes, and user friendly?
Further, it might depend on the platform. So, for example, there may be authentication methods that are better suited for mobile, which aren't possible on web and vice versa.
Thanks for putting this out. A main bit of feedback on the content, which might help.
It's important to me to have more information about the author. What is your background? What informed this point of view? etc., etc., Is this even your work or thesis?
Agreed with others, the formatting is brutal. My initial reflex is that it was very Dropbox with poor formatting.
Reminds me of when Uber began to facedown regulators and town halls, and went through a re-brand to become "more human".
Facebook must be putting on its game-face for regulators, and attempting to draft some halo-effect from Instagram for the Facebook brand.
Nice work and nice effort. The UX/ UI is - and should be - fairly straightforward. However, the main thing for me is that passwords are an extremely sensitive matter.
There is nothing here that commands trust, which is essential for me as a user to perform this type of task through a web application.
Love it and prefer it to HN. Only item - I wish there was a dark mode.
I use Dark Mode on DN now with Stylish. It's not too bad:
This is a great write up. Thanks for sharing.
I also embarked upon a similar path using a Midi-Controller and the BetterTypeTool. I tried it for awhile, but ultimately, the heuristics of using the controller didn't make sense for me. It was easier to simply execute these commands in Runner than to lift my hands off the keyboard and try and make sure I hit the right pre-loaded button.
I do think the hardware inputs for the design process are still in the dark ages. A mere keyboard and mouse seems primitive. I wish there were more hardware inputs akin to music production. I've seen some attempts, but they look cheap, flimsy and clunky.
Unfortunately, the hardware market, risk and demand for such a product probably doesn't align for the effort involved.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.