Key point
One screen, one job
A good screen makes one job obvious. The user should know where they are, what matters most, and what to do next.
Before you polish colours or fonts, decide the screen’s primary action. Everything else should support it or move lower.
Start with a 5-second read
Open one screen from your project. Show it to a friend for 5 seconds. Then hide it and ask: what is this screen for, and what would you tap first?
If they cannot answer, the screen has a hierarchy problem. This is common in hackathon apps because teams add features fast and give every element equal weight.