Prove It: Module 4 Check
A post-test on evaluating quality and privacy, plus what changed since the start of the module.
📈 Compare, Don’t Just Answer
One of these revisits the prediction you made at the start of the module, and one is a new question on privacy. See what’s different now that you’ve run the stranger test and thought through a real judgment call.
1. You look at an app and something feels 'off,' but you don't know a design term for what's wrong. What should you do?
You just did this in the last hands-on lesson, and it produced a real, working fix. Plain language was always enough.
2. Is it possible to evaluate whether an app is well-designed without knowing how to code it?
Four simple tests — 5-second, thumb, squint, silence — were enough to find and fix a real usability problem, no design background required.
3. Your app collects a user's email address. Before showing it to anyone, what's the right move?
Working and safe are two different questions. A confident-sounding answer about security deserves the same scrutiny as a confident-sounding bug fix.
🎉 Celebrate, Revisited
Go back to this module’s opening claim: you already had taste, you just needed permission to trust it. Look at the fix you directed last lesson — a real usability problem, found and solved, using nothing but your own instinct as a user. That instinct was never missing. It just hadn’t been asked for yet.
⏭️ Up Next
You’ve built, refined, debugged, and evaluated. Module 5 puts all four together in one original project — and this time, you ship it so someone else can actually use it.