Where the design community meets.
Valencia, Spain UX Designer Joined about 9 years ago
Ben hasn't posted any stories yet.
I don't know if this is the same for anyone else, but I'm finding it impossible to complete my profile due to the location field.
It asks where I am, doesn't accept a general place and asks for a full address in the validation error. Even with a real address in, it won't let me continue. This is in Safari and Chrome on OS X.
Aside from the fact it is broken*, why in the hell would you need my full address? I don't live where I work, and I don't want you to have my address. It seems a real barrier to entry for people looking to register.
Looks good though.
* I'm guessing it is something related to your Google Map API keys, given the warnings in the web inspector.
Everything we do is taken from the chapter on integrating Lean UX into Agile in the book Lean UX, as that was the inspiration for how we work.
As a designer/team of designers, the single biggest area of friction is the 'why' of your work; what are you trying to achieve with your designs, why is this element here, etc etc. It is imperative to work side-by-side with the people who will be developing the feature to ensure they have buy in and empathy for what you as a team are trying to achieve, as then they will work harder to produce what has been envisioned.
Work in cross-functional teams, with all of the dev/QA and design roles present throughout the lifetime of a feature (for us it's 1 UX and 1 UI designer per team of 5 devs, normally). Have a feature kick-off where all the ideas and assumptions you have are brain farted out. When you test assumptions with users always have at least one other member of the team with you to understand the constraints we face or mistaken assumptions you've made. As you iterate through MVPs review them and comment on them as a team.
The biggest change for us was regarding job titles as competencies, not roles; I'm not the only person who can interview a user or draw a box, and similarly I can code to a prototype level quite comfortably. Being less precious about who does what really helped the team grow as a team rather than a group of people doing different stuff.
Seriously, the Lean UX book changed my life. I'd highly recommend it.
I don't know - there is still the problem of hiding options behind a dropdown, and the fact that dropdown cope less well with long labels/values/sentences.
There is little a drop down can do that a well written group of radio buttons and labels can't, while also bring much more 'discoverability' to the form.
I've already tweeted them about the fact that there is almost no way to tell if you are uploading a bunch of files or not - before a nice big overlay appeared with progress on a per file basis. Now, a just tiny icon in the top right. Almost as bad is the unreadable text, the even less meaningful icons, the hidden share buttons, less context as to what tab I am on and the awful pink add button, (which changes mode based on the tab and only encourages you to drag and drop, a behaviour which a user can and will adopt without using the button very quickly).
The whole thing reeks of gratuitous redesign for the sake of it, and while the performance is better not much else is - it epitomises a lot of what Eli Schiff has been talking about lately in terms of lack of rationale and a desire to be fashionable and on trend. As a paying customer who has encouraged my entire organisation to use InVision, I'm hugely disappointed to see that this is where they chose to dedicate their resources.
Have you considered iCloud Drive? Apple haven;t got the track record but the OS X integration is good and it also gives you storage in the new Photos.app.
I switched to it from Dropbox when Photos.app was released, and it's been grand for me.
Part time Visual Designer at Spektrix. In-house only.
I'm in the process of redesigning a huge piece of software that, while not responsive, presents a lot of the similar challenges you're facing. For me, a methodology like Brad Frost's atomic design is priceless.
Given that I've already sketched out wireframes on paper or a more coarse tool like Omnigraffle, I split my Sketch file into separate pages, one each for 'patterns', 'templates' and 'pages'.
The 'pages' are where I rough out the visuals of the entire screens - how the header, footer and different layouts all play together. I then abstract this out into templates with a separate artboard for each. As I build these, I abstract out the patterns into the constituent atoms, molecules and organisms that Brad describes in the Patterns page with an dartboard for each type.
By starting holistically soon the patterns begin to build the templates and you find you are designing fewer templates/pages - I actually have moved back to Omnigraffle for them as I can churn out wireframes much quicker there, while everyone knows what each control or pattern should look like.
For me its about getting just enough into Sketch to inform the design so it can be built as soon as possible - my goal is for the HTML to be the canonical design, with only unknown stuff being done in Sketch - don't worry about your design files getting out of date, just throw them away and start again with the new features or pages.
I must be missing something - is there a way to pump saved colours back into applications like Sketch or OmniGraffle?
I'm just getting started with it, but http://beseku.vsco.co
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
An ex-colleague of mine who happened to be very good at his job had a great solution to this. He charged 180% of market rate, but then offered a 50% discount on that price if paid within 14 days. So if he got paid on time, he would be charging essentially 90% of market rate.
All I will say is that the late payers more than made up for the 10% shortfall from prompt payment.