4 ms·
Good question: If you are doing things by yourself, this can be the way the go. But even then I think it helps to first think about the big picture. Reasons t
by juliushuijnk 4y ago
Good question:
If you are doing things by yourself, this can be the way the go. But even then I think it helps to first think about the big picture.
Reasons to first do low-fi wireframing:
- It's the quickest way to find out if you understand the requirements of the task.
- It takes more time to do the details, in that time you could have gotten your first feedback. Like from the developer who says there is a component already built that looks like your wireframe, but somwhat different. Then you get to talk about that. Perhaps you can say "Yes, use that component" and your job is done.
- You might get the wrong feedback, like; why did you not use our company color blue for that button? Why is the tablet version looking so bad? Why didn't you consult with legal department about those texts? etc.
- Trying to design the whole thing at once might kill creativity in your team. Designers get sad if they only have to 'paint by number'. They probably have some good ideas you can incorporate. Same for the dev.
Having worked for decades in digital media (sites, apps, games, etc), I've seen projects waste many many hours by developing or designing things that the client simply didn't want. Just because there was a misunderstanding about requirements.
There are many more reasons, but again, if you are working for yourself, and you have a process that works for you, then that's great.
- CyberDildonics 4y agoIt's the quickest way to find out if you understand the requirements of the task. It takes more time to do the details, in that time you could have gotten your first feedback. These are claims, but not explanations about how this is better. The rest of what you are saying are benefits of working incrementally, but it doesn't seem to have anything to do with what you made. low-fi wireframing I still don't get this. Isn't it just using a different style of outline around buttons? What is lo-fi about it? Wouldn't lo-fi be something that was much lower memory and much faster to draw, like solid color boxes?
- juliushuijnk 4y ago> I still don't get this. Isn't it just using a different style of outline around buttons? What is lo-fi about it? Wouldn't lo-fi be something that was much lower memory and much faster to draw, like solid color boxes? Low-fidelity is jargon. It's a word used in the UX Design community for high level, low detail design artifacts. Perhaps you are thinking of low-fi audio and try to match that to wire-frames. https://www.invisionapp.com/inside-design/low-fi-vs-hi-fi-prototyping/ https://www.invisionapp.com/inside-design/low-fi-vs-hi-fi-pr... https://balsamiq.com/wireframes/ https://balsamiq.com/wireframes/ "Balsamiq Wireframes is a rapid low-fidelity UI wireframing tool that reproduces the experience of sketching on a notepad or whiteboard, but using a computer. It really forces you to focus on structure and content, avoiding lengthy discussions about colors and details that should come later in the process. Wireframes is FAST: you will generate more ideas, so you can throw out the bad ones and discover the best solutions." > ..but it doesn't seem to have anything to do with what you made. The thing I made allows you to do this on your mobile phone, so anywhere, anytime. That's the unique part. As far as I know, there are also no great tools to do a little bit of front-end development on your phone either. So perhaps a cool niche for someone to jump into.
- juliushuijnk 4y agoBtw, this type of clearing up confusement is one of the most important (and hard) parts about UX Design. The wireframing is quite easy if you finally really understand all the requirements and stakeholder goals you need to balance. So in the future the app will include features to facilitate this process too.