<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Subhajitmallick on Medium]]></title>
        <description><![CDATA[Stories by Subhajitmallick on Medium]]></description>
        <link>https://medium.com/@subhajitmallick879?source=rss-fe938bbfa31e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*TeD554lAT4Y9NeMu</url>
            <title>Stories by Subhajitmallick on Medium</title>
            <link>https://medium.com/@subhajitmallick879?source=rss-fe938bbfa31e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:43:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@subhajitmallick879/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Flashback — Final GSoC’25 Report]]></title>
            <link>https://medium.com/@subhajitmallick879/flashback-final-gsoc25-report-3c011f1b9f48?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c011f1b9f48</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Thu, 11 Sep 2025 03:52:17 GMT</pubDate>
            <atom:updated>2025-12-07T07:15:58.651Z</atom:updated>
            <content:encoded><![CDATA[<h3>Flashback — Final GSoC’25 Report</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*GPfQD5GEIHi97l4B" /></figure><h3>My Project Summary — Flashback</h3><p>Earlier, the app experience was frustrating for learners who were redirected to earlier concepts for revision after making a mistake, since they had to re-answer all intermediate questions to return to their original point. With this project, my aim was to introduce a new Flashback feature that allows learners to revisit previously solved questions, view the correct answer tied to their misconception, and then return directly to where they became stuck — eliminating the need to reattempt intermediate steps. This ensures a smoother, frustration-free learning journey while reinforcing foundational understanding.</p><p>Additionally, this project improves the visual presentation of submitted answers for multiple choice and item selection interactions.</p><h3>Important Links</h3><ul><li><a href="https://docs.google.com/document/d/1Ed5zOvMxDpFmjH-MEDkjm-yR6E4ZgBrarFzFlSO1g-o/edit?usp=drive_link">My GSoC Proposal</a></li><li><a href="https://github.com/oppia/oppia/wiki/Google-Summer-of-Code-2025#41-flashbacks">Project Details</a></li><li><a href="https://github.com/oppia/oppia-android/issues/5732">GitHub Issue</a></li><li><a href="https://github.com/oppia/oppia-android/issues/5732">Sub-Milestone Breakdown</a></li><li><a href="https://docs.google.com/document/d/1NpWgRN6BgvlutWXTYkz997ft36nRMYCbxSO7RYy2iV8/edit?tab=t.0#heading=h.rpq25vez37fp">Product Requirements Document</a></li><li><a href="https://docs.google.com/document/d/12rUDcX96tn5r7WEVZd0fnxKY10YGM9bzIaadAbhC9II/edit?usp=drive_link">Feature Testing Document — Milestone 1</a></li><li><a href="https://docs.google.com/document/d/1tvYos9Eac13n9aMTJH5Kdopg7jpcZtkPV5cDRwhAXVM/edit?usp=drive_link">Feature Testing Document — Milestone 2</a></li><li><a href="https://www.figma.com/design/CUGy6Hdt9tdswrAJWMVtcX/Oppia---If-Stuck?node-id=0-1&amp;p=f&amp;t=MO54IU7psNq95xXS-0">Figma Design Mocks</a></li></ul><h3>Milestone 1</h3><p>In Milestone 1, I focused on introducing the Flashback feature to enhance the learner’s revision experience. I implemented the Flashback button that allows users to access previous solved question answer. I introduced Flashback screen which presents previously solved questions, explanations, and answers to reinforce understanding. This ensures learners can revisit concepts smoothly without reattempting intermediate steps.</p><ul><li>Introduce a feature flag for the Flashback feature | <a href="https://github.com/oppia/oppia-android/pull/5862"><strong>Pull Request</strong></a></li><li>Implement logic to determine when to show Flashback button | <a href="https://github.com/oppia/oppia-android/pull/5864"><strong>Pull Request</strong></a></li><li>Introduce new UI component for “Revisit Previous Question” button and add tests | <a href="https://github.com/oppia/oppia-android/pull/5842"><strong>Pull Request</strong></a></li><li>Implement navigation logic to view the Flashback Screen | <a href="https://github.com/oppia/oppia-android/pull/5865"><strong>Pull Request</strong></a></li><li>Introduce the UI components for Flashback Screen | <a href="https://github.com/oppia/oppia-android/pull/5868"><strong>Pull Request</strong></a></li><li>Implement navigation logic for returning to the pending question after viewing Flashback | <a href="https://github.com/oppia/oppia-android/pull/5869"><strong>Pull Request</strong></a></li></ul><h3>Milestone 2</h3><p>In Milestone 2, I focused on refining the Flashback feature by updating its triggering logic and improving the overall design. I introduced redesigned submitted answer layouts for multiple-choice and item-selection interactions. Additionally, I implemented event logging for the Flashback feature to capture learner interactions.</p><ul><li>Change Flashback Triggering logic | <a href="https://github.com/oppia/oppia-android/pull/5916"><strong>Pull Request</strong></a></li><li>Enhance conversation flow | <a href="https://github.com/oppia/oppia-android/pull/5910"><strong>Pull Request</strong></a></li><li>Update the design of submitted answers for multiple-choice and item-selection interactions | <a href="https://github.com/oppia/oppia-android/pull/5917"><strong>Pull Request</strong></a></li><li>Remove flashback confirmation dialog and update design of Explanation box | <a href="https://github.com/oppia/oppia-android/pull/5918"><strong>Pull Request</strong></a></li><li>Capture and log events from the new Flashback screen | <a href="https://github.com/oppia/oppia-android/pull/5939"><strong>Pull Request</strong></a></li></ul><h3>Outcome</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WWPogrC8ApIcl05Bx6LEJw.png" /></figure><h3>Flashback Output Screen Record</h3><p><a href="https://drive.google.com/file/d/1K69-KKF1B_AfvzawcjkW-vl5_q2URb66/view?usp=drive_link">https://drive.google.com/file/d/1K69-KKF1B_AfvzawcjkW-vl5_q2URb66/view?usp=drive_link</a></p><p>Connect with me on other platforms:</p><ul><li><strong>LinkedIn:</strong> <a href="http://www.linkedin.com/in/subhajit-mallick-63a5a0243">https://www.linkedin.com/in/subhajit-mallick</a></li><li><strong>GitHub:</strong> <a href="https://github.com/subhajitxyz">https://github.com/subhajitxyz</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c011f1b9f48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 4 Update of M2: Working on Flashback Logic and Overcoming Challenges]]></title>
            <link>https://medium.com/@subhajitmallick879/week-4-update-of-m2-working-on-flashback-logic-and-overcoming-challenges-fd048d8ed4b7?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd048d8ed4b7</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Tue, 19 Aug 2025 13:46:54 GMT</pubDate>
            <atom:updated>2025-08-19T13:46:54.199Z</atom:updated>
            <content:encoded><![CDATA[<p>This week began with energy as usual, and I focused mainly on developing new logic for flashback triggering and M2.2. However, midway through the week, I caught a fever. Soon after, we discovered that my elder sister had jaundice, and our family had to start her treatment as per the doctor’s instructions.</p><p>It was a tense and difficult time for me, and I shared my situation with my mentor. She suggested that I spend some time with my family and continue my work gradually. I followed her advice, dedicating time to my family during the day and working at night to keep up with my tasks.</p><p>Although this was one of the hardest and most stressful weeks of the year, I am glad that I managed to balance both responsibilities. Despite the challenges, I was able to complete my work for the week on time, which makes me feel proud and motivated moving forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd048d8ed4b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3 Update of M2: Finalizing Designs and Progress on M2.1, M]]></title>
            <link>https://medium.com/@subhajitmallick879/week-3-update-of-m2-finalizing-designs-and-progress-on-m2-1-m-d6b9502cedb4?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6b9502cedb4</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Tue, 12 Aug 2025 15:38:54 GMT</pubDate>
            <atom:updated>2025-08-12T15:38:54.934Z</atom:updated>
            <content:encoded><![CDATA[<h3>Week 3 Update of M2: Finalizing Designs and Progress on M2.1, M2.2</h3><p>This week, I focused on finalizing the designs for both M2.1 and M2.2. I had several meetings with my mentors to review the plans and make sure everything matched the design goals.</p><p>For M2.1, I worked on modifying the logic and testing it according to the design requirements. While I made good progress, a few parts of the work are still pending.</p><p>Even though there is still work to be done, I now have a clear understanding of the design for both M2.1 and M2.2. This will help me move forward smoothly.</p><p>Looking ahead, my goal for next week is to complete the remaining tasks for M2.1 and finish the work for M2.2. I’m confident that with the designs finalized, I can make steady progress.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6b9502cedb4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 2 Update of M2: Finalizing Plans and Solving Design Issues]]></title>
            <link>https://medium.com/@subhajitmallick879/week-2-update-of-m2-finalizing-plans-and-solving-design-issues-1ec18fb5135f?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ec18fb5135f</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Wed, 06 Aug 2025 06:25:04 GMT</pubDate>
            <atom:updated>2025-08-06T06:25:04.743Z</atom:updated>
            <content:encoded><![CDATA[<p>This week, I focused on planning how to build the next parts of my project for Milestone 2. I spent most of my time thinking through the best ways to solve technical problems and design the upcoming features.</p><h3><strong>Solving Design Conflicts</strong></h3><p>During the week, I ran into some confusion about the design and the strings used in the UI. To solve this, I had several meetings with my mentor and tech lead. We also reached out to the UXW team to get their suggestions on the product design and how things should look and feel for users.</p><p>These meetings helped clear up the confusion and gave me a better understanding of what the final product should look like.</p><h3>Moving Forward with Clarity</h3><p>Even though this week involved fewer coding tasks and more discussions, it was still very important. Now that the design and direction are clear, I feel ready to start the next parts of the work with more confidence.</p><h3>Looking Ahead</h3><p>I’m happy with the progress so far and excited to begin building the next features for Milestone 2 in the coming week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ec18fb5135f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to Work: A Strong Start to Milestone 2]]></title>
            <link>https://medium.com/@subhajitmallick879/back-to-work-a-strong-start-to-milestone-2-2f0c99d32ad9?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f0c99d32ad9</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 17:23:35 GMT</pubDate>
            <atom:updated>2025-07-31T17:23:35.875Z</atom:updated>
            <content:encoded><![CDATA[<p>After a refreshing two-week break, I resumed my GSoC journey on July 26 with renewed energy and a clear focus on Milestone 2. The week was largely dedicated to planning, clarifying goals, and getting back into the rhythm of development.</p><h3><strong>Getting Aligned</strong></h3><p>One of the initial challenges I faced was understanding the intended outcome for task <strong>M2.1</strong>. To address this, I actively engaged in mentor meetings and also participated in our calm discussion threads. These conversations were incredibly helpful in aligning expectations and clarifying technical uncertainties.</p><p>With that clarity, I was able to confidently start working on <strong>M2.1</strong> and map out the broader solution for the remaining milestone tasks.</p><h3>Progress So Far</h3><p>This week, my primary focus was on implementing <strong>M2.1</strong>. While diving into the code, I also began exploring possible approaches for the subsequent tasks in Milestone 2. I now have a solid direction and a high-level plan for how to approach the upcoming work.</p><h3>Looking Ahead</h3><p>The early momentum and problem-solving done this week have put me in a good position for the weeks ahead. I’m optimistic about completing the milestone on time and am excited to see how the rest of the implementation unfolds.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f0c99d32ad9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC 2025 Diary: Weeks 5 & 6 — Wrapping Up Milestone 1 Smoothly]]></title>
            <link>https://medium.com/@subhajitmallick879/gsoc-2025-diary-weeks-5-6-wrapping-up-milestone-1-smoothly-33d769ba721d?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/33d769ba721d</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Fri, 25 Jul 2025 04:24:31 GMT</pubDate>
            <atom:updated>2025-07-25T04:24:31.394Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC 2025 Diary: Weeks 5 &amp; 6 — Wrapping Up Milestone 1 Smoothly</h3><p>Weeks 5 and 6 went by quite smoothly, with steady progress and no major blockers. After getting a head start in the earlier weeks, I was able to maintain good momentum and finish the remaining tasks for <strong>Milestone 1</strong> right on time.</p><h3>Key Highlights</h3><p>During these two weeks, I completed and submitted three pull requests that helped tie everything together for the Flashback feature:</p><p>✅ <strong>PR 1.4:</strong> Added the navigation logic for viewing the Flashback card, along with the necessary tests</p><p>✅ <strong>PR 1.5:</strong> Introduced the Flashback screen’s UI and linked it with the “Revisit Previous Question” button.</p><p>✅ <strong>PR 1.6:</strong> Implemented navigation logic for returning to the original pending question after viewing a Flashback.</p><p>Each of these PRs built on the previous work and helped complete the full user flow for the Flashback experience.</p><h3>Smooth Collaboration</h3><p>I continued to have regular meetings with my mentors, which really helped clarify any technical questions and kept everything on track. Their guidance on how to organize my code, structure the pull requests, and write meaningful tests made the whole process feel manageable and productive.</p><h3>Final Thoughts</h3><p>Finishing Milestone 1 on time — and without major blockers — was really satisfying. It gave me the confidence that I’m on the right track and helped deepen my understanding of both the codebase and the open-source workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33d769ba721d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC 2025 Diary: Week 4 — Laying the First Bricks of Code]]></title>
            <link>https://medium.com/@subhajitmallick879/gsoc-2025-diary-week-4-laying-the-first-bricks-of-code-21a31cbec667?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/21a31cbec667</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Sun, 08 Jun 2025 14:57:12 GMT</pubDate>
            <atom:updated>2025-06-08T14:57:12.498Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC 2025 Diary: Week 4 — Laying the First Bricks of Code</h3><p>Thanks to my early start in Week 3, I entered Week 4 with a solid head start — and it really paid off. Much of the coding work planned for this week was already done, which gave me the breathing room to focus on refining the details.</p><h4>Writing Code &amp; Tests</h4><p>This week, I spent time carefully reviewing the code I had written earlier — making sure everything worked as expected and adding proper test coverage. I successfully completed two key tasks from Milestone 1 and submitted pull requests for both.</p><p>PR 1: Implemented the domain logic to control when the Flashback button should appear.</p><p>PR 2: Introduced the UI for the Flashback button, giving users a way to interact with the new feature.</p><h4>Learning from Mentor</h4><p>Regular mentor meetings continued this week and were especially helpful. I learned about PR chaining, how to manage related changes across multiple pull requests, and practiced using Git commands more effectively. These were valuable lessons that will help a lot in the weeks ahead.</p><h4>Final Thoughts</h4><p>Week 4 turned out to be a smooth and productive one. Getting ahead earlier gave me the time to polish my work, complete my tasks on time, and deepen my understanding of the codebase. With Milestone 1 off to a strong start, I’m excited to keep building on this momentum in the coming weeks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21a31cbec667" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC 2025 Diary: Week 3 — From Planning to Early Coding]]></title>
            <link>https://medium.com/@subhajitmallick879/gsoc-2025-diary-week-3-from-planning-to-early-coding-809086594902?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/809086594902</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Sun, 08 Jun 2025 14:42:33 GMT</pubDate>
            <atom:updated>2025-06-08T14:42:33.954Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC 2025 Diary: Week 3 — From Planning to Early Coding</h3><p>With my semester exams finally behind me, Week 3 of my journey brought a welcome change of pace. After the high-pressure balancing act of last week, this week felt much more relaxed and focused. I had more time and mental space to concentrate fully on the project — and it turned out to be a very productive week.</p><h4><strong>Project Planning &amp; Discussions</strong></h4><p>This week, I worked on creating the Critical User Journey (CUJ) and testing documentation for both Milestone 1 and Milestone 2. These documents helped lay the foundation for what the user experience should look like and how we plan to test it throughout development.</p><p>I also had several helpful meetings — both with my mentors and the design team. These discussions helped clear up some of the earlier confusion and brought more clarity to the project roadmap. It was encouraging to see everything starting to take shape.</p><h4><strong>Getting a Head Start on Coding</strong></h4><p>Although the official coding period begins on July 2nd, I decided to start writing code a few days early. Starting early gave me a head start to explore the codebase in more depth, catch potential blockers, and ease into the development phase without time pressure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=809086594902" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC 2025 Diary: Week 2 — Balancing Exams and Engineering]]></title>
            <link>https://medium.com/@subhajitmallick879/gsoc-2025-diary-week-2-balancing-exams-and-engineering-71f3646f9bc2?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/71f3646f9bc2</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Fri, 23 May 2025 13:58:17 GMT</pubDate>
            <atom:updated>2025-05-23T13:58:17.161Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC 2025 Diary: Week 2 — Balancing Exams and Engineering</h3><p>As I step into the second week of the Community Bonding period for Google Summer of Code 2025 with Oppia, this chapter of the journey has been an intense balancing act — managing the dual responsibilities of my academic semester exams alongside crucial proposal refinement work.</p><h4>Academic Commitments &amp; Time Management</h4><p>With a packed exam schedule this week, time seemed to fly. Yet amidst the academic grind, the GSoC proposal deadline loomed. To navigate this, I adopted a focused strategy: I accelerated my exam preparation, aiming to wrap up syllabus portions early in the day so I could dedicate time each night to refining my proposal. Though I couldn’t manage a full two hours every single day, I made the most of every free moment — especially over the weekend, when I dedicated extended hours to proposal revisions.</p><h4>Refining the Proposal</h4><p>One of the primary goals this week was to incorporate all mentor feedback into the proposal, ensuring technical clarity and thoroughness. I revisited every section with a critical eye, restructuring content where needed and resolving ambiguities. The result: a more polished and implementation-ready version of the project blueprint, which I then submitted for technical lead review.</p><h4>Mentor Meetings &amp; Solution Deep Dive</h4><p>This week, I had the opportunity to conduct two detailed meetings with my mentor. These sessions were instrumental in clarifying doubts and discussing the overall solution architecture. Together, we refined the approach and arrived at a better-aligned technical strategy for the project. Another key topic of discussion was sub-milestone planning — breaking down the implementation into 1–2 day PR-sized tasks to help keep the project agile and manageable.</p><h4>Reflection</h4><p>Looking back, this week demanded both discipline and determination. Juggling exams with GSoC preparation wasn’t easy, but the challenge brought out a new level of productivity and purpose. It’s been one of those weeks where, despite the pressure, I truly enjoyed the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71f3646f9bc2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GSoC 2025 Diary: Week 1 — A Night to Remember✨]]></title>
            <link>https://medium.com/@subhajitmallick879/gsoc-2025-diary-week-1-a-night-to-remember-3d9f0c696ffd?source=rss-fe938bbfa31e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d9f0c696ffd</guid>
            <dc:creator><![CDATA[Subhajitmallick]]></dc:creator>
            <pubDate>Fri, 16 May 2025 11:24:32 GMT</pubDate>
            <atom:updated>2025-05-16T11:40:08.079Z</atom:updated>
            <content:encoded><![CDATA[<h3>GSoC 2025 Diary: Week 1 — A Day to Remember✨</h3><h4>From heartbreak to happiness — my unforgettable selection moment and the beginning of an exciting summer with Oppia.</h4><h4>The Big Moment</h4><p>Like many aspiring contributors, I was buzzing with excitement on May 8, 2025 — the day GSoC results were announced. I kept checking my inbox over and over, hoping to see that golden email. But unlike some of my friends, who got their confirmation right away, my inbox remained silent.</p><p>After about 15–20 minutes of waiting and worrying, doubt started creeping in. Maybe I didn’t make it this year, I thought. Feeling heartbroken, I went to bed, thinking the opportunity had slipped away.</p><p>But then — at exactly 11:51 AM — I got the notification: “Congratulations, your proposal with Oppia Foundation has been accepted!”</p><p>I jumped out of bed in disbelief. The happiness hit me like a wave — all the sleepless nights, the hard work, the debugging, and endless documentation finally paid off. I was officially in! That single moment erased all the stress of the past weeks, and I couldn’t stop smiling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*eStWg-qIc785h4b7QHzzSw.png" /></figure><h4>My Project: Flashbacks</h4><p>I’m thrilled to be contributing to Oppia Android this summer through my GSoC project titled Flashbacks.</p><p>The current app experience can be frustrating for learners who are redirected to earlier concepts for revision after making a mistake, as they must re-answer all intermediate questions to return to their original point. This proposal introduces a new Flashback feature that allows learners to view the correct answer or revisit previously solved question answer tied to their misconception and then return directly to the point where they became stuck — eliminating the need to reattempt intermediate steps. This reinforces foundational understanding while enabling a smoother, frustration-free learning journey.</p><p>Additionally, this project improves the visual presentation of submitted answers for multiple choice and item selection interactions by replacing the current HTML-based approach with a cleaner, natively rendered experience.</p><h4>Community Bonding Period</h4><p>This week, I had the chance to attend the Contributor Briefing Meeting hosted by the Oppia team. It was great to meet fellow contributors and the incredibly welcoming org admins. We received clear guidance about expectations, timelines, and best practices for the summer.</p><p>I also had a couple of one-on-one mentor meetings — I’ll admit, I was a little nervous at first. But the support and encouragement I received instantly made me feel more confident about the journey ahead.</p><p>I’m truly grateful to the Oppia team for this amazing opportunity. The journey has just begun, and I’m super excited to bring the Flashbacks feature to life.</p><p>Stay tuned for more updates from my GSoC 2025 journey — this is just the beginning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d9f0c696ffd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>