At telesto.ai, we realized that we made a crucial mistake in organizing our workflow.
Up until now, we always started with the backend API when developing new features. Then, we added the UI.
You definitely shouldn't do that.
Let me explain why!
Up until now, we always started with the backend API when developing new features. Then, we added the UI.
You definitely shouldn't do that.
Let me explain why!
You always notice crucial flaws in the UI when seeing it for the first time.
It may be hard to use or straight-up lack functionality that you missed during planning.
However, changes require backend modifications as well. You have to do the work twice!
It may be hard to use or straight-up lack functionality that you missed during planning.
However, changes require backend modifications as well. You have to do the work twice!
So, our workflow is now the following.
1. Sketch the UI in Figma.
2. Walk through the user flow several times.
3. Spot flaws and correct the UI.
4. Repeat 1-3 at least once.
5. Move on to design and implement corresponding backend functionality.
1. Sketch the UI in Figma.
2. Walk through the user flow several times.
3. Spot flaws and correct the UI.
4. Repeat 1-3 at least once.
5. Move on to design and implement corresponding backend functionality.
As a backend/machine learning person myself, I grew to love and appreciate UI/UX design.
For us, the lesson is clear: UI first, API second.
For us, the lesson is clear: UI first, API second.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
