I think it partly depends on the process you’re using and the tools.
For example, we layout our proposed UI in Moqups (we used to us Balsamiq) which is a wireframing tool. It doesn’t give you defined units of size to have to stick to, but it lets us play with how best to represent the data to the user and helps us plan interactions, etc.
From there, well build the interface using our app’s design system which already has components and sizing all figured out which takes a lot of the issues you’re talking about away.
You could, however, use a more concrete tool like Sketch or Indesign, both of which are more geared towards creating ‘pixel-perfect’ representations of the end interface.
However you approach it, I think you’ve got to start with the aim of getting something close to what you want and then having a certain amount of acceptance that you’ll need to hone it during the actual build.
Enthusiastic Web Developer, a decent artist and a bread loving duck 🦆♥️, trying to provide the community with help and resources. (Also I am addicted to web dev)
I think it partly depends on the process you’re using and the tools.
For example, we layout our proposed UI in Moqups (we used to us Balsamiq) which is a wireframing tool. It doesn’t give you defined units of size to have to stick to, but it lets us play with how best to represent the data to the user and helps us plan interactions, etc.
From there, well build the interface using our app’s design system which already has components and sizing all figured out which takes a lot of the issues you’re talking about away.
You could, however, use a more concrete tool like Sketch or Indesign, both of which are more geared towards creating ‘pixel-perfect’ representations of the end interface.
However you approach it, I think you’ve got to start with the aim of getting something close to what you want and then having a certain amount of acceptance that you’ll need to hone it during the actual build.
Thanks for the helpful words!
😁