Mocks for Oppia Android "if_stuck_state" flow

[ankitkaushik]

Meeting Notes
None

Platform
Oppia Android

Describe the request

• Need review of Figma prototype showing flows for learners in "if_stuck_state" to get unstuck.
• Need to create mocks for the flows shown in Figma, based on the ideas described in the PRD

Context
Learner engagement on Oppia has been shown to suffer with the experience of challenging questions that learners answer incorrectly. To solve this problem for learners using Oppia Android, we have proposed a new flow for learners that get stuck ("if_stuck_state") on one of these questions to get unstuck. The linked PRD details this proposal.

Links
PRD
Mocks

DESIGN APPROVAL CHECKLIST -- DO NOT EDIT.

• UX Design approved (Android mocks should include dark mode)
• UX Writing approved
• Design Systems Team approved
• Product approved

For a design project to be completed, it needs approval from UXD, UXW, DS and PM. Please tag the following reviewers when your project is ready (at least one reviewer for each of the 4 bullet points below):

• UXD: @GlowWindow (for Android projects)
• UXW: @stepmalt
• Design systems: @qluuu / @celestinetales
• PM: @seanlip

[jlevick]

@seanlip I'm not sure what's going on with this?

[seanlip]

Hm, I'm not sure either. @kaiyuxu @ankitkaushik could either of you please give an update -- what is the remaining gap and when will it be possible to wrap this up? Thanks!

[ankitkaushik]

Hi Sean, My understanding is that the mocks have been completed and shared with the engineering and learner team for implementation. Kaiyu - please correct if that is not the case. Are we looking to determine a completion date for the engineering deliverables? Best, Ankit

…

On Fri, Sep 15, 2023 at 3:29 AM Sean Lip ***@***.***> wrote: Hm, I'm not sure either. @kaiyuxu <https://github.com/kaiyuxu> @ankitkaushik <https://github.com/ankitkaushik> could either of you please give an update -- what is the remaining gap and when will it be possible to wrap this up? Thanks! — Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSZYFUHF5Q5VHIZZEQ4VD3X2P7VJANCNFSM6AAAAAATUU6HR4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[seanlip]

@ankitkaushik This hasn't been sent to the engineering team yet. There are still unresolved comments on the mocks -- I think one is waiting on you and one is waiting on @kaiyuxu . Perhaps you could both take a look, so that we can wrap this up?

Thanks!

[ankitkaushik]

Hey Sean - thanks for flagging, I believe I just replied to one of the comments waiting on me.

…

On Mon, Sep 18, 2023 at 10:40 AM Sean Lip ***@***.***> wrote: @ankitkaushik <https://github.com/ankitkaushik> This hasn't been sent to the engineering team yet. There are still unresolved comments on the mocks -- I think one is waiting on you and one is waiting on @kaiyuxu <https://github.com/kaiyuxu> . — Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSZYFVQD332YH7Y3CNJ7T3X3BMPFANCNFSM6AAAAAATUU6HR4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ankitkaushik]

Hi Kaiyu, There are still a few unresolved comment threads on the mocks - would you be able to follow up on those at your earliest convenience? Best, Ankit On Mon, Sep 25, 2023 at 2:20 AM Ankit Kaushik ***@***.***> wrote:

…

Hey Sean - thanks for flagging, I believe I just replied to one of the comments waiting on me. On Mon, Sep 18, 2023 at 10:40 AM Sean Lip ***@***.***> wrote: > @ankitkaushik <https://github.com/ankitkaushik> This hasn't been sent to > the engineering team yet. There are still unresolved comments on the mocks > -- I think one is waiting on you and one is waiting on @kaiyuxu > <https://github.com/kaiyuxu> . > > — > Reply to this email directly, view it on GitHub > <#50 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABSZYFVQD332YH7Y3CNJ7T3X3BMPFANCNFSM6AAAAAATUU6HR4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[kaiyuxu]

Hey Ankit - I'm currently traveling for my PTO out of the country. I'm having some internet connection issue to google and figma but get back to the comments as soon as I can. Thanks for following up.

[ankitkaushik]

Hi Kaiyu - just wanted to follow up on this thread to see if there might be any updates, thanks.

…

On Mon, Oct 2, 2023 at 8:15 PM kaiyuxu ***@***.***> wrote: Hey Ankit - I'm currently traveling for my PTO out of the country. I'm having some internet connection issue to google and figma but get back to the comments as soon as I can. Thanks for following up. — Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSZYFV6RV4QRPRVWKGCG7DX5NKJRAVCNFSM6AAAAAATUU6HR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTHE2TSNJVGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[seanlip]

Some quick notes on where the project is, since we are transitioning its ownership from @kaiyuxu to @malee04:

• Prototypes and most of the flow have been prepared by @kaiyuxu in https://www.figma.com/file/CUGy6Hdt9tdswrAJWMVtcX/Oppia---If-Stuck?node-id=0%3A1&t=N5ZdYIwujpCb2du6-1 . Please use those mocks/flows as a basis; you might want to make a copy of the Figma file.
• There are two specific comments left to address. One is:
  • A question about whether the "return to question" buttons should be fixed or floating.
  • A request for the "read-only submission view" for the different types of questions, taking care to try and ensure that the different question types are consistent.
• There is also an open email thread to look at re testing the prototypes and understanding whether users are facing any issues. We would need to work with the UXR team to prepare a research plan for this.

@malee04 Please feel free to ask if you have any questions about the above. (Also, please make sure to download the Android app from the Play Store and use it, so that you can get a sense for the different question types in the app. Thanks!)

[seanlip]

Previous designs: https://www.figma.com/file/CUGy6Hdt9tdswrAJWMVtcX/Oppia---If-Stuck?node-id=0%3A1&t=N5ZdYIwujpCb2du6-1

New designs: https://www.figma.com/file/biarFLCQ3c389PL1xmukRo/Oppia---If-Stuck-(Malee's-Copy)?type=design&node-id=0-1&mode=design&t=RHOylkXfKnqkw98g-0

[malee04]

Design options: https://www.figma.com/design/biarFLCQ3c389PL1xmukRo/Oppia---If-Stuck_Malee?node-id=2346-1338&t=rMHMfhtddhghTKR0-1

[seanlip]

Note: UXW has finished reviewing the mocks here (confirmed by @tamiorendain on 5 Nov 2024): https://www.figma.com/design/biarFLCQ3c389PL1xmukRo/Oppia---If-Stuck_Malee?node-id=2346-1338

[tamiorendain]

Realized I never moved this forward - status updated!

[Melodydsb]

Hi Sean,

Quick reminder of the current situation :

Problem statement
Currently, when a learner answers a question incorrectly in Oppia, they are redirected back to a previous card to review the concept. However, the current implementation is inefficient: the learner is forced to replay all intermediate steps before reaching the original question again, which disrupts the learning flow and creates frustration.

Solutions to explore
To improve this experience, the goal is to introduce a flashback system that allows learners to review past content without breaking their progression. Instead of physically moving backward in the sequence, the learner would see the relevant past card as a pop up and then seamlessly return to their current question.

V1 to optimise
I’ve added a new flow after the second attempt at answering a question. If the student fails and the question is based on a concept they should already know, an "I need help" button appears. When the student clicks on the button, an overlay pops up with key concepts related to the question, allowing the student to quickly revisit the concept.

Once the overlay is closed, a confirmation modal appears, giving the student two options:

1. Try answering the question again.
2. Go back to the full lesson.

Preview

Flow
https://www.figma.com/design/PxVtirmSBPUtKUJfsgwWI7/Oppia---If-Stuck---Concept-Flashback---Feb-2025?node-id=0-1&t=gEVphDjgNTEuA9ZJ-1

FEEDBACKS & NEXT STEPS

Soft Redirection to Past Cards
Instead of just a short concept review, allow learners to access the full relevant past card directly.
Ensure they aren’t forced to redo previous steps but can quickly review and continue without disrupting progress.

Develop the Flashback Mechanism
Implement an overlay system that displays the past card when needed.
Once the learner has reviewed the card, they can close the overlay and resume where they left off.

[seanlip]

@Melodydsb Thanks for the summary, it is helpful! I broke out the flashbacks issue into its own one at #179, so that the team can tackle that one first and then come back to this larger one to figure out the overall "stuck" flow.