Be nice. Or else.
Wasn't familiar with Whimsical. Looks good.
How do you find keeping Storybook aligned with what's documented in Confluence (and vice versa)?
Abstract is great. Central to our workflow now. Lingo is a solid tool but it does something which I would expect Sketch to already do, which is shared layer and text styles as part of a library. Before Sketch libraries we also used Lingo to share our UI components.
It didn't make any money, and I wasn't confident that it could (without a lot more work). Had a decent amount of users and attractive domain name. Sold it with Flippa.
This is cool, and a great way to experiment, exercise your design skills and learn new technologies (Vue.js in this case).
I made a similar "yet another todo app" a few years ago (https://flask.io) to learn some Rails and jQuery. Ended up getting some (just a little) traction which enabled me to use it for experimenting with analytics tools. I ended up selling it a few years later.
So even though this has been done before, great work shipping a functional product.
Hey Mattan, I agree. This isn't truly agile or truly waterfall, but somewhere in the middle.
Due to our current process (where we focus on several big features per release) there is a lot of iteration at the design and discovery phase which involves engineering leads. Sometimes this will include coded prototypes to validate things work as intended.
Once we move into the "develop" phase, you're right we continue to learn more and have to make changes, but we have hopefully massively decreased the risk of big changes at this point. Often during development, depending on the project, we'll have several micro design iterations.
Thanks! I find it helps provide some context for when sharing our reports. Helps those reading the report visualize who was testing it. Also helps me when I'm looking back at previous reports, seeing a photo can help me remember the user and what we chatted about.
Good question. Since the report is in our Wiki, we use inline commenting to have discussions around each issue and pull in the relevant PM, lead developer or lead designer. Out of that we either modify our designs and prototypes, if it's something we're working on, or if it has already been built create an issue for developers to look at (we use Jira). If it's something major then we'll pull in relevant team members and discuss over a whiteboard.
Also worth noting we tag our usability test reports in a way that they are pulled in to product requirement wikis, so hopefully they are always referenced even in future projects.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.