What do you think? When designing/developing an app, making sketches, interviewing potential users, and watching people use a prototype or similar app, are important ways to see how users will interact with the app and can help you make important design decisions.

• True

• False

"Code a little, test a little" is a good idea when coding. In other words, don't just write a ton of code before running it or having someone else review it.

• True

• False

topButton and bottomButton will be "orange" and "red", respectively, when the program shown is finished running.

• True

• False

What color will "topButton" be we run this program but the user NEVER clicks the button?

• red

• blue

• green

• orange

What will be displayed in the console if we run this program and click "topButton" twice?

• cat bird dog

• cat dog bird

• cat dog bird bird

• Nothing will be displayed in the console

What will be displayed if we run this program and click bottomButton once and then topButton once?

• cow pig chicken

• pig cow chicken

• chicken

• chicken pig cow

What is displayed if we run this program and click "bottomButton" ONCE?

• banana dragon fruit cherry

• apple banana cherry dragon fruit

• banana dragon fruit cherry apple

• banana dragon fruit apple cherry

• True

• False

In sequential programming commands run in the order they are written. In event-driven programming some commands run in response to user interactions or other events.

• True

• False

Which of the following is NOT a good reason to include comments in programs?

• Comments help the computer decide whether certain components of a program are important

• Comments help programmers debug issues in their own code

• Comments help document how code was written for other programmers to use

• Comments enable programmers to track their work throughout the development process