Programming Basics
Pair Programming
Flowcharts & Algorithms
Lists, Variables, & Data
Events, Sensors, & Logic
100

What do we call mistakes in code that stop the app from working?

Bugs

100

Who is responsible for typing the code?

The Driver

100

Which shape represents a YES/NO decision?

Rhombus (diamond)

100

A list that stays the same and never changes is called a ______ list.

Static list

100

Which sensor triggers an event when the phone is shaken?

Accelerometer

200

What structure repeats actions until a condition is met?

Loop

200

Who checks for errors and gives direction?

The Navigator

200

Which shape typically begins and ends a flowchart?

Oval

200

Which type of list changes when the app runs?

Dynamic list

200

What block do we use for user-triggered actions (like button clicks)?

Event handler

300

What App Inventor item temporarily stores values for later use?

Variable

300

Why are two perspectives (Driver + Navigator) better for debugging?

More eyes catch more mistakes and improve accuracy.


300

Give an example of a Yes/No real-world decision.

“Is it raining?” / “Should I bring a jacket?” / “Is my phone charged?”

300

Give one example of a Static List in a real app.

Months of the year, Zodiac signs, 50 states

300

What does disabling a block do?

Prevents code from running without deleting it.

400

Why do we use comments in code?

To explain the purpose of code / help future debugging

400

Give one example of miscommunication that could happen during pair programming.

Navigator gives unclear directions OR driver codes ahead without listening.

400

Come up with a mini algorithm for a morning routine using 3 steps.

Wake up → Get dressed → Eat breakfast

400

Give one example of a Dynamic List in a real app.

User’s notes list, shopping list, reminders list

400

Give an example of an event handler block.

Control, Logic, Variable, Math

500

Explain one way to reduce redundancy in an event handler using a computational concept.

Use procedures or loops to avoid repeating identical blocks.

500

Explain how pair programming mirrors real-world computer science teamwork.

Teams collaborate, assign roles, debug together, and combine strengths—just like in professional development.

500

Explain how flowcharts help programmers before building an app.

They clarify logic, prevent mistakes, and map the sequence of decisions and actions.

500

Explain how a list + random block could be used to make a “Random Joke App.”

Store jokes in a list → use random index → display selected joke on screen.

500

Explain why procedures are important when building multi-screen apps.

They reduce repetition, organize complex actions, and keep code efficient and consistent.