Where the design community meets.
Front End Dev @ Booking.com Joined about 9 years ago
If I were building 1Password, one goal would definitely be that nobody could sit down at (or steal) another user's computer and easily get the user's data from the filesystem. Maybe that goes beyond the basic value prop, but when you're selling a security product, it should be built with security in mind from the bottom up. And no, suggesting that it's the user's fault for not password-protecting their filesystem is doesn't cut it when your product is for people who can't remember passwords.
As for the dropbox issue, it needs to be extremely clear to the user what's happening here, and they need to be given instructions to confirm that they are not making this data publicly accessible. An important population of the customer base are folks who have trouble remembering not only passwords, but details in general, and may not be fully computer literate. Plus, 1Password is heavily relying on a third party here, which should scare the pants off them.
Plus, ,last night my girlfriend was trying to use the unpaid version of 1Password to sync her data from her phone to a new laptop. To use icloud, the recommended (and presumably more secure) sync method, she would have had to pay $30, so she was forced to use the dropbox method instead.
The initial post was alarmist and not totally accurate, but there's definitely some work 1Password needs to do here to do right by the user.
Everybody's scared of serifs now. Thanks Google.
This logo seems to be heavily influenced by what I call the "tessellated" look -- overlapping angular shapes, often forming triangles -- as well as the colors of the season (Spotify green anyone?).
It's good to use trends to your advantage, but you have to be really careful when applying them to your logo. I lean towards integrating tends into the site design, while striving for a logo that can complement (rather than exemplify) trends as they come and go.
My money says this logo won't live particularly long.
and here's a rebuttal from a current employee.
As an American I find your comment highly offensive.
I've said it before, and I'll say it again: the part of my job that most prohibits me from being productive and agile is JIRA. However, I don't think that the tool's linearity is the issue, at least not in my workplace.
The interface is just really hard to use. I regularly lose tickets and have no idea how to find them, resorting to searching my email. The things I use most are usually hidden under an inconspicuous drop down. There are multiple ways to view a ticket, but you can only do certain operations on the ticket in certain views.
The other problem, which isn't unique to JIRA, is that (for devs, at least) time estimation isn't possible. The things that take up the vast majority of our time are when something isn't working the way we expected, and we have to troubleshoot. So in our estimates, we end up doing stuff like doubling how long it would take if everything goes the way we expect. The result is that my estimates are rarely accurate, yet I spend time every day updating them.
My girlfriend is like "what is wrong with you?!"
Within Booking.com, I work in BookingSuite, which is a new division consisting of a few acquired startups focused on building products for hoteliers. It's a great position to be in, and feels like a startup with the resources of a giant.
We're hiring pretty aggressively across the board - chances are if you're interested we have a spot for you.
This doesn't really let you make custom tags like Polymer or Angular. It lets you use different names for existing tags and then swaps them out.
One idea to make it useful would be to be able to define html partials that get substituted in, so for example,
<my-input label="Name"> becomes
<label for="my-input">Name</label><input id="my-input" type="text">
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Kudos for taking on the daunting task of publishing something near comprehensive on this topic. Now the real challenge begins - keeping it up to date :)