Yes, +John Duhring
. I've spun up two development versions of Oppia
now to test, one at home on my Mac and one at work on a Unix box. I haven't deployed on Google App Engine
As +Judy Arzt
points out, this type of interaction is not far away from what you get when you call your bank (voice-mail jail). Nevertheless, you can pose questions in a way that makes students think
and keeps them thinking/guessing
until they (hopefully) develop some understanding and transition to the next "state" (as Oppia questions are called).
A book I've just finished reading, Doing Data Science
 puts it this way:
"[I]n education in traditional settings, we focus on answers. But what we should
focus on, or at least emphasize more strongly, is how students behave when they don't know the answer
A clever question writer can use Oppia
to put students into this uncomfortable position over and over. And scaffold their teasing out the answer. And then monitor the results
to see what happens. The post-interaction analytics appear to be pretty good (color-coded state frequency reports -- which show you how often students visited each of the states of your exploration). This potentially leads to development of better
explorations where "better" has some objective measure (such as percentage of students completing/progressing).