Earlier quoted context omitted.
Good excuse for me to explain what the app is all about. In user experience design (UXD or UX design) or interaction design, or however you like to call it, the user interface (UI) is the whole thing that the user interfaces with. Developed and with the final design. A wireframe is a step towards that user interface. Low-fi, meaning low fidelity, meaning with low details to just focus on the big picture stuff, helps…
Why wouldn't someone just position buttons in photoshop or some image editor? Or just layout the actual program and take a screenshot? It doesn't really take much time to declare a user interface.
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.