See how research, screens, visual design, and testing fit together.
What you will learn.
Explain what research, UX, UI, shared rules, and a prototype each contribute to one product idea.
Before you begin.
Finish Start here first. Open C27 Academy — [your name] and a familiar app, or use the music-app teaching example. This is a written mapping exercise, not a connected-screen build.
Learn the concept.
The course has a teaching order so you can learn one skill at a time. A real project can loop: research may change a flow, a prototype check may reveal a missing label, and the team may return to earlier choices. A prototype is a practice version used to try the proposed steps; describing one here does not mean building it.
Words to know.
Research
Questions and evidence about what people need or do.
Investigate a question
UXUser experience
The route and information that help someone complete a goal.
Find
Book
Can someone book a class without getting lost?
UIUser interface
The visible words, controls, type, color, and layout.
Think buttons, words, pictures, and space.
PrototypePractice model
A practice version used to try proposed steps; in this lesson you only describe it.
Click through screens before an app is built.
The idea in practice
See a worked example.
Start with one music-app goal.
For exampleA listener wants to find and play a song. Research asks what stops them today; the answer is not assumed.
Map each discipline to that goal.
For exampleUX maps Search → Results → Song; UI gives Play a readable label; a shared rule keeps that label consistent. A written prototype idea describes how someone could try the route.
Explain what a later check could change.
For exampleIf a later test shows people miss Play, reconsider its route, label, or placement. This lesson asks for notes, not a working app.
