Using this question type will enable students to include both SI and non-SI mathematical units with numerical answers. This allows lesson creators to frame questions around physical quantities, or help students gain a better understanding of unit conversions by converting a value given in one unit into a different unit. The question type also includes support for several currency units such as dollars, cents, rupees, paise, etc.

This question type also allows creators to provide learners with appropriate feedback on their answers. For example, for a question whose correct answer is 2 km, Oppia can recognize not only equal answers (such as 2 km) as being correct, but also equivalent answers (such as 2000 m).

Here is a screenshot of what the question type looks like:

We hope that this question type will help learners learn about units effectively, while providing more flexibility to lesson creators. As always, if you find any bugs or have any feature requests, please feel free to file them in our issue tracker or make a post on the Oppia discussion forum. We look forward to seeing the new explorations that you create with this question type!

Learn mathematical units: a new Number with Units question type was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

With this question type and its hands-on approach, students can learn to compare and sort items by arranging things in ascending or descending order. We believe that this interface provides an intuitive approach for answering questions that require learners to sort a sequence. Here are some screenshots of what it looks like in action:

By dragging and dropping the items, learners can easily sort the sequences and get appropriate feedback on the submitted answers. As a lesson creator, you can provide feedback to the learner based on the correctness of the whole sequence, or the position of a specific item in the sequence. Note that the question type isn’t restricted to numbers: it’s also possible to add images, fractions or text as items in the sequence.

We hope that this question type will provide more flexibility to lesson creators, and give a way to learners to demonstrate their understanding of comparing and sorting. As always, if you find any bugs or have any feature requests, please feel free to file them in our issue tracker or make a post on the Oppia discussion forum. We look forward to seeing the new explorations that you create with this question type!

Learn by sorting: a new Drag and Drop Sorting question type was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

As a student, you might remember staring puzzledly at a math problem for hours on end, and needing a little nudge in the right direction. If only someone were around to give you a small hint! Thanks to the work of Kevin Thomas, learners on Oppia who are stuck on a problem now have the option to view hints and solutions.

Kevin Thomas was Google Summer of Code participant that worked with Oppia. Together with his mentors — Tony Jiang, Kevin Lee, and Joshua Cano — Kevin created the hints and solutions functionality that is optimized for both desktop and mobile versions of Oppia. Students love them, and so do we!

This is how the new functionality works:

1. When we detect that students are stuck on a problem — either because they have been spending too long at a card, or because they’ve entered a wrong answer and some time passes — a lightbulb icon will appear to show that a Hint is available.

2. When the student clicks on the light bulb, the hint text will appear.

3. If the Student is unable to answer the question, a second hint will appear.

4. Step 2–3 will repeat until all hints are exhausted.

5. If the student is unable to answer the question, a yellow light bulb will appear.

6. Clicking the yellow light bulb will trigger a pop-up that asks the student to confirm that they want to see the solution. If the student confirms, they will be shown the solution.

The hint functionality in Oppia has already been received positively by students. In several user studies we did in Delhi last November with a set of Oppia lessons on Fractions, students highlighted the friendly and approachable hints as something they really liked about the Oppia learning experience.

Oppia is excited to have this feature, and we look forward to improving it further based on feedback from students and teachers. If you’d like to incorporate this new feature in your lessons, check out the Oppia exploration editor! (You can add new hints by clicking the “Add Hint” button at the bottom.) We look forward to seeing your explorations!

Feature Featured: Hints and Solutions by Kevin Thomas was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

From the outset, Oppia has set its sights on alleviating the problem by using innovative technology to increase the supply of free and effective educational material online. The Oppia team realizes that this isn’t an easy task, but in 2017, we are pleased to report significant progress on multiple fronts that will allow Oppia to have a greater impact in 2018. Let’s take a look back at 2017!

Technology

A central part of Oppia’s work is our platform for creating interactive lessons, hosted at Oppia.org. When determining our platform roadmap, the team’s priority in 2017 was effectiveness: how do we make it easy to create effective lessons, and how do we make sure students who need these lessons most stay engaged?

Making an online lesson truly effective is not straightforward, and requires several iterations. In 2017, we conducted a series of user studies in India in order to gain feedback on the lessons. Through these, we learned what students liked and found useful, and also identified areas for improvement.

The Oppia team adopts a continuous improvement mindset. We go through iterations of creation and testing, and incorporate feedback into our processes and platform. One of our major learnings this year was that making the lessons accessible didn’t just involve students being able to access or operate their devices; in our target demographic, significant language barriers hindered students from being able to learn. Even when the subject matter of the lesson was mathematics, students needed to understand the feedback, story and instructions in order to stay engaged.

In order to overcome this, the Oppia team introduced multilingual audio support to the Oppia platform. Audio translations can now be added to both the main story card and subsequent hints, as shown in the screenshot below:

In addition, alternate languages are offered in a prominent spot so that students can easily see them when playing the lessons:

The introduction of this functionality led to a significant difference in students’ comprehension of the lessons. As you’ll see in more detail below, students in India loved them!

Team Engagement and Lesson Process Improvements

However, the platform is only part of the story. Having a platform that can result in effective lessons doesn’t mean that any lesson created on that platform is effective. In 2017, the Oppia team worked to gain a deeper understanding of how to create effective lessons, so that we can then find ways to create such lessons at scale and make them widely available.

Surprisingly, this is still a somewhat open problem. Many online education efforts have focused more on scale/quantity than on quality, and tend to be targeted at learners who are already reasonably proficient. On the contrary, Oppia’s goal is to make lessons that work well for everyone as widely available as possible, particularly for students who do not have access to quality education and consequently lack a strong grasp of the subject.

Fortunately, Oppia has been able to recruit a diverse set of volunteers from around the world to the team. Many of our volunteers, especially those from developing countries, have witnessed the inequality of education first-hand, and are working together to try and create lessons that are universally enjoyable, effective, and easy to relate to. Through this collaboration and periodic user testing, we’ve started developing a reliable and scalable process to create story-based lessons that support scaffolded skill-based instruction and target particular misconceptions.

This process has been formalized into a program that we’ve been using to onboard, assign, and drive the creation of enjoyable, effective lessons on our platform. The result of this is an exemplar set of story-based mathematics lessons that follows a young student, Matthew, as he faces various challenging math-related situations in the real world. You can check out a sample lesson here: https://www.oppia.org/collection/4UgTQUc1tala

User Studies

In 2017, the Oppia team also started taking our model lessons out into real-world situations. We did this by partnering with EvalDesign, an education evaluation firm, to bring our math lessons to schools in Delhi, India.

We conducted several user studies, with the last one taking place over five days at a government school in Delhi attended by students from low-income families. The results were great: students didn’t want to put the phones down at the end of the lessons, and they also couldn’t wait to get started again the next day! When asked to compare the Oppia lessons to those they had at school, they thought the Oppia lessons were much better, citing the audio translations, friendly hints, story and images, and the fact that the lessons contain lots of very good questions.

Here’s a sample quote from one of the students:

I liked learning the lessons on mobile because in the mobile we get very good questions and if we get something wrong we are told how to correct it and we are not scared when we are doing this. Because in this we get hints also. I really liked this app. I am not very interested in the lessons we learn in school because if we get a question wrong, we get a beating for it. That is why I am not interested in the teaching we have in school.

These studies demonstrate Oppia’s potential: it provides students with a way to learn that is helpful, understandable, and easily accessible with just a mobile phone.

Plans for 2018

Our momentum from 2017 carries into 2018. In Q1, we plan to conduct a randomized controlled trial in a government school in Delhi, India. The trial will be conducted in a population with a similar demographic to that of the user studies. The aim of this trial is to validate the effectiveness of the Fractions lessons we’ve created, in order to ensure that the Oppia platform makes it possible to create lessons that are not only enjoyable, but also effective.

The result of the trial will be an important driver of our 2018 roadmap. If the trial does not succeed, we will figure out what went wrong, and try again. If it does succeed, then this would be a major success for our work to date, since it will demonstrate that our methodology leads to measurable improvements in learning outcomes. We will then look into distribution and scaling, in order to ensure that these lessons can reach more students who need them.

If you would like to help out, please visit Oppia Foundation’s Get Involved page to discover how you can make a difference in the lives of learners around the world. And, in the meantime, stay tuned to our blog for the RCT results, as well as other exciting updates throughout 2018!

Oppia Year In Review: 2017 was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

As an entirely volunteer-run non-profit organization, Oppia has contributors from across the globe. Each volunteer not only contributes their work, but also their invaluable cultures and views that make up the fabric of our community.

To encourage more interaction and exchange of ideas amongst volunteers that are scattered across the globe — and also to have some fun — Oppia has just formed its very first Social Committee!

To kick off, the Social Committee will host a series of Social Meets throughout the end of 2017. Details of the events are listed here: https://github.com/oppia/oppia/wiki. The Committee will also be reaching out to the Oppia Community as the event approaches — stay tuned!

If you want to join in the fun, check this page out for ways to get involved: https://www.oppia.org/contact

Introducing Oppia’s Social Committee was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

Summer’s officially over, but we’re taking one last longing look at it in part 3 of our Google Summer of Code blog series. Fittingly enough, this week we’re featuring Avijit, a GSOC participant who helped work on making the creator dashboard that much more user-friendly.

As you may already know, Oppia is a community of learners and teachers looking to help anyone learn anything in an effective and enjoyable way. Being a community based on education, it’s absolutely important that the quality of content is not compromised at any cost. With quality content being the primary focus of their work; creators play a pivotal role in the learning pipeline. The learning experience can be better enhanced with improvements to the “explorations” (lessons) created. To accomplish this, the creator must be made aware of the current state of his/her exploration(s), and how they can improve them. And that’s where I came in- improving the creator’s dashboard.

Revamping the existing “Creator Dashboard” consisted of implementing a dashboard with the following goals:

1. Allow creators to see common statistics like total plays, average rating, common student misconceptions, and student-submitted feedback for the lessons they own — and to make it easy for creators to take action on this information.
2. Prioritize the explorations in the dashboard which need action, decided by different parameters such as number of new feedback instances and number of unresolved answers.

Before:

After:

The new dashboard page allows creators to choose how they view their explorations in either the default view, as shown above (card view), or in a tabular format (list view). Users can switch to the list view to see a more informative version of the dashboard.

The statistics shown in the top white row are values calculated across all the explorations of the user. In the default card view, explorations may be clicked on to open a dropdown tab which provides statistics for that exploration. However, if the exploration is private then the user will be taken directly to the editor. The explorations can be sorted using the select dropdown and even by clicking on the table headers in the list view.

Sharing the content created also just became easier; there are options in the dashboard to share explorations on popular social media platforms like Google+, Facebook, and Twitter.

Lastly, to provide an equally appealing experience for the users browsing the dashboard on a mobile device, care was taken to ensure the new dashboard is similarly functional to be almost as well equipped as the desktop version. Here’s how it looks on smaller screens:

I would like to thank Google for enabling students to participate in open source development through GSoC, the whole of Oppia community for accepting my project proposal and letting me embark on this fantastic adventure, and most importantly, my mentors — Sean Lip, Xinyu Wu, Allan Zhou for being there to help me and Rachel Chen for ideas and design mocks for the dashboard.

I learned a lot during my 3 months of GSoC. I did the best that I could to help the community. And though I can say that most of my work is concluded, there’s still a pull-request in git-hub left unmerged, a few ongoing pull-requests involving work unrelated to GSoC, and some more code I’ve promised to write. And I’m happily looking forward to all of it as my summer of code comes to an end.

Thanks to Avijit’s great work this summer, we’ve seen quite a change come through the Oppia interface. We’ve got some exciting things coming soon such as an Hour of Code event, and a blog post featuring Sourav, who helped organize a Hacktober bug-bash to help Oppia find a few bugs and help us make things better for you. Stay Tuned!

-Oppia Team

Google Summer of Code Part 3: Goodbye Summer, Hello Future was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

Google Summer of Code part 2

Summer may be over, but we’re still basking in how great the Google Summer of Code went for some of our Oppia contributors. Below we have Vishal Gupta, an Oppia contributor who made an impact with us this summer by helping improve the speed of the Oppia website. If you’re technical on what goes on behind the browser, then you’ll feel right at home!

Hi! I am Vishal, an open source contributor here at Oppia. I am also one of Google Summer of Code 2016 student with Oppia.

More about Oppia:

Oppia is a wonderful tool for self learning, it’s like a game which you could play endlessly.

In many places around the world, Internet connectivity is not really great or is a little

expensive. This restricts people from being able to use the wonderful opportunities that

are out there on the internet. We had a mission to make Oppia more efficient, which allows us to play our part in making the internet more accessible even to users with poor internet connectivity.

The Journey:

We set out to make Oppia load faster. This meant that we needed to analyze the entire codebase and mark out inefficiencies which could be improved.

According to Steve Souders, “80–90% of the time spent by users waiting for pages to load is spent on the frontend, all the work that needs to be done after the HTML document has arrived”. This statement along with our analysis of Oppia at the user end, pointed out some major issues that needed to be worked on. Thanks to our cool developers and Google App Engine (partly), the backend looked in good shape. Hence, we focused on improving the frontend and end to end performance of Oppia.

To quantize improvements that we were going to make, we needed something to measure them. We initially started with Chrome Dev Tools (which is fantastic) to measure basic metrics such as page load time and page size for a first time user and a returning user (cached resources). But, we needed a tool which would do this automatically every time we pushed changes to Github. There were a few tools available but each of them had some shortcomings and we decided to implement our own.

We used a tool called selenium to interact with browsers (since we needed to simulate performance in a real scenario) and browsermob-proxy to record the different files required to load Oppia. We then wrote another module that took this raw data and churned out useful performance metrics for us like total page size, total page load time, etc. We used unittest to write test for different pages. We wrote a bash script to run these tests and added them to Travis for continuous integration. Now, we test our performance every time someone pushes a new commit!

One of the major issues we identified was that resources were either not being cached or were cached for only 10mins. One limiting factor preventing longer caching times was not being able to uniquely identify resources. And, if we added a longer expire duration to these resources, we would be serving stale content when we pushed a new release. Hence, we worked on adding cache slugs to ALL static resources! We implemented cache slugs using a really simple idea but at a coarse level where a new release means every file is a new file, even if it has not changed between releases. For every release, we generate a random slug and serve all static resources under that slug (eg. /build/random_slug/file1.css, /build/random_slug/folder1/file1.css). Hence, the user doesn’t have to load all the resources every visit to Oppia.

After adding cache slugs, the total page load size decreased substantially for repeat users, offering an improved experience. But, looking at the html source we noticed that a large amount of js code was included (inlined) in the html page which meant that we were unnecessarily sending a large amount of data which we could potentially cache at the user end, improving the experience even further. We subsequently removed inlining of js code and instead included them as external scripts which could be cached. We also added minification to scripts that weren’t minified earlier (extension resources). Externalizing the scripts will also reduce response time, as the backend was earlier doing a good amount of IO to read these scripts and inline them.

Coming to an end:

My experience with the Oppia community has been fantastic! Everyone at Oppia has been really supportive and helpful. I would like to invite everyone out there to come and contribute to Oppia.It’s something that can make a huge impact on so many different levels and I’m so glad to have been a part of it. A big shout out to my mentors Ben and Madiyar who have always been there when I needed them. Also, special thanks to Sean and other Oppia mentors.

Thanks Again Oppia!

Life in the fast lane- Google Summer of Code Part 2 was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

You may have noticed that Oppia’s creator dashboard is looking better, and that the site has gotten faster. This is due to the efforts of Vishal Gupta and Avijit Gupta, both of whom have just completed a 3-month stint with Oppia as part of Google Summer of Code (GSoC), a Google program which enables students to take part in actively developing open source projects during their summer months.

This is Oppia’s first year participating in GSoC, and it was a blast! Many more students eagerly flocked to our ideas page than we had expected, and our Gitter channel was full of people saying hello, looking for starter projects, and asking for help with setting up a local Oppia server. We received dozens of emails asking for clarifications on our suggested projects, or reviews on early project proposals by students. In the end, we received 40 proposals, with a couple proposing new projects entirely or going beyond the ideas we had originally suggested.

As a first-time organization, we were offered two student slots. Figuring out which candidates should fill these slots was a difficult process, and involved multiple rounds of review and debate. In the end, we selected Avijit Gupta and Vishal Gupta to work on the creator dashboard and improving Oppia’s performance, respectively — we regard these projects as fundamentally important for the platform, and are very excited to see them coming to a conclusion.

Both Avijit and Vishal had access to multiple mentors who could help them throughout the summer. We’d like to thank all the individuals who mentored, reviewed applications, or were otherwise responsible for Oppia’s successful participation in GSoC this year: Allan Zhou, Ben Henning, Bren Briggs, Jacob Davis, Madiyar Aitbayev, Sean Lip, and Xinyu Wu. We’re also very grateful to Google for allowing our organization to participate in the program, and would like to extend our largest thanks to both Vishal and Avijit for their efforts throughout the summer.

Oppia hopes to return next summer in GSoC 2017. If you’d like to subscribe to news and updates about Oppia’s participation in GSoC, you can sign up to the oppia-gsoc-announce mailing list — or, if you’re already feeling enthusiastic, you can start helping out right away. In the meantime, stay tuned for upcoming blog posts by Avijit and Vishal sharing their individual GSoC experiences!

Google Summer of Code! Part 1 was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

Oppia is a community for learners and creators. Our mission is to bring engaging and educational lessons to the community as a means of an extra resource through lessons made by people just like you. We like to showcase our amazing people from time to time and we wanted to showcase Kristin, an Oppia contributor who is doing work behind the scenes to make code happen.

Kristin is also newer to coding, and Oppia was one of her first big opportunities to put to work her newly acquired skills. Learning is never easy, but Kristin gives us some insight into her learning curve through an excerpt of her blog below. Kristin shows us that learning is a process, and turning that progress into accomplishment takes time and effort:

Open Book, or Looking it Up isn’t Cheating

So, as you may or may not know, I’m a beginner JavaScript developer and I’ve been increasingly proud of the (struggling) headway I’ve made, though I know there’s still a ton to learn. But man, I got started on this project, which is using the Angular JS framework, and even my beginner project was a struggle. So you know what I did? I Googled things. I looked up stuff on Stack Overflow. I asked a few questions on Stack Overflow. I asked questions within the project. And now, I’m on my fourth or fifth assignment and submitting PRs (pull requests) like a (featherweight) champ. And I never once got accused of cheating or lost points off my grade!

In the higher ed environment I’m in now (and even in the professional development environment I was in previously), there remains this idea that multiple choice tests rule, that every student should be able to answer these questions with all the knowledge they should have memorized from the course presentations. But the bottom line (which all my colleagues are very passionate about) is that the real world doesn’t work that way.

There may be some things that you need to own in your own head, but many times, declarative-type knowledge is stored away in other forms (notebooks, note-taking apps, documents and documentation, job aids, etc.). The piece the humans have to get good at is synthesizing knowledge from various sources, collaborating with a variety of other people not like them, and solving problems. In other words, not multiple choice test stuff. Of course multiple choice is easy to grade; I can certainly see the appeal in that. But it’s generally super inauthentic and your learners know it.

Whenever possible, we should opt for authentic assessments that allow people to apply their new knowledge. In academia, that could look like making every test an open book test and/or collaborative test, because the questions students have to answer can’t be found by looking it up in the book. Or it might look like creating assignments that have students putting work out into the world (for example, writing and or editing Wikipedia articles and going through their peer review process or contributing to open efforts to transcribe historical letter — both actual assignments created at my former institution, the University of Texas,, by the way!).

Showcasing this is important to us not only because it was a way for us to show off Kristin’s great work, but it speaks to something larger that Oppia and its explorations address: There is no singular way to learn something for everyone. We’re all different. Maybe you learn best from flash cards, or from watching interactive videos, or maybe even just from simply reading a book about it.

On Oppia, if the lesson doesn’t help the learner, they can tell the creator. This is incredibly powerful because education is no longer in the hands of the “teacher” but rather the student. It re-creates the 1–1 tutoring feel, and gives students that chance to learn something in a way that hasn’t been presented to them before, much like how Kristin was able to find stuff on coding in places that weren’t just the classroom.

Oppia is that opportunity for collaboration between teachers, learners, creators, and hobbyists as a way to share their knowledge and build upon it. You don’t have to be afraid to look beyond the textbook to find the answers, you may just find what you’re looking for on Google, on a free course online, or even on Oppia. And if you can’t find it, tell someone! That’s how you find out who may know what you’re looking for and go beyond the textbook to learn what you need :).

Oppia wants to be your resource for lessons and things that you want to learn. Have a request for something you haven’t seen yet? Post on the forum! Think you have something to add to a lesson you’ve found? Sign-up and collaborate with the person who posted the lesson. We’re happy to have you join!

We’re excited to bring you new and fresh content soon so stay tuned, stay learning, and happy exploring!

-Oppia

One Way Or Another, I’m Gonna Learn Ya was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.

Welcome to an inside look at Stanford’s Team Oppia! From October to December 2015, Raine Hoover, Travis Shafer, Divya Siddarth, Santos Hernandez, and myself were honored to be this team in the CS+Social Good class.

Mission: Revamp Oppia’s profile page.

Prior web-programming experience: Limited.

Status: Completed.

What we learned: Where do I even begin?

Here’s a quick introduction to Oppia. Oppia, named after the Finnish word meaning “to learn”, is a free, open-source learning platform. It outpaces many other online education initiatives by focusing on one-on-one tutoring experiences. Simply try one of its lessons, called “explorations”, at Oppia.org, and you will experience lessons that teach through a series of questions that cater to their learners’ unique responses. The explorations are crowd-sourced, meaning that anyone can become a teacher on any topic. As a result, Oppia is an educational Wikipedia of sorts, one that can seriously change the face of online education.

Similar to Wikipedia, crowdsourcing has amassed a significant amount of content for Oppia. At last count, Oppia has over 4,200 explorations and over 125,000 users. Yet, also like Wikipedia, this crowdsourcing questions the quality of the content. A lack of credibility is damaging to any site, let alone an educationally-focused one. Our team sought to address this dilemma through a redesign of the user profile page that had three overarching goals:

1. Give credibility to our contributors

• The new profile page would demonstrate contributor impact.

1. Incentivize contributors to create high quantity, high quality explorations

• Higher visibility of contributors’ explorations encourages accountability.

1. Allow learners to discover other explorations from contributors they have enjoyed learning from in the past

• Higher visibility of contributors allows learners to identify the content sources.

Soon after we started our project, it became abundantly clear that significant steps had to be taken prior to any kind of implementation. Compared to the other three CS+Social Good projects, ours was unique for having a pre-existing codebase. This called for careful planning to ensure seamless software integration, design consistency, and scalability. First, we created wireframe design mock-ups of the new profile for user-testing. We spent two weeks on design revisions in response to user feedback. Finally, we included the final mock-ups within a detailed profile design specification document that was reviewed by the entire Oppia team.

Here are our results.

The original profile page:

The current, live profile page:

The new profile page features two separate sections, three tabs, user statistics, and user contributions. Feel free to go to www.oppia.org/profile/kerryxwang to explore the new features that are discussed below.

The top section of the profile contains users’ personal information and includes two brand-new features: interests and first contribution date. Users can now add their subject interests to their profile; we hope this will encourage collaborations between contributors with mutual interests. In addition, the date of our users’ first contribution, defined as either the publication of a new exploration or the edit of a published exploration, is showcased on their profile. This provides some information on the contributor’s level of experience.

The bottom section of the profile contains users’ contribution information. The first tab contains three statistics: user impact score, number of created explorations, and number of edited explorations. While the latter two statistics are self-explanatory, the impact score was defined specifically for this context. It incorporates the average rating and number of playthroughs for each of a user’s explorations in one numerical indicator. Previously, the numbers of created and edited explorations were not being tracked, but we believed that the publication of the statistics could both incentivize contributors to contribute more and also indicate contributor experience.

Our team strategy was to split up the profile into many smaller projects that were completed independently, and we are proud to have had our work come together to form the complete page. In addition to the technical jobs, several of our smaller projects were supplemental design projects. As Oppia is constantly improving, we wished to lay groundwork for future improvements. Thus, in parallel to the implementation of the current features, we developed three prototypes for future implementation.

One prototype is a design for a more informational and user-friendly statistics tab.

Another future improvement is the gamification of the profile page. We created Author, Contributor, and Explorer badges that users can earn as they contribute to Oppia:

Lastly, as applications are increasingly becoming mobile-friendly, we created a mobile mock-up of the profile page.

Our team is extremely grateful to have learned so much through this project. As a team, we started with very little web-programming experience and a varied background from product design to human biology to journalism. Throughout this experience, not only did we learn about design and software engineering, we learned a lot of valuable intangibles. These include navigating a large codebase, using Github, and learning the software engineering process. Our new Oppia profile page is up and running, and we are ecstatic to see its growth! A second redesign is already in progress, building on the work we have completed, so look out for a relaunch in the upcoming months.

Oppia is the epitome of learning for all, as it is a learning space for both its users and its creators.

We would like to give thanks to Sean Lip, Amit Deutsch, Jacob Davis, and Xinyu Wu for their mentorship and support. In addition, this project could not have been possible without Manu Chopra, Lawrence Lin Murata, and the rest of the CS+Social Good team.

Profiling Oppia’s New Profile Page was originally published in Oppia.org on Medium, where people are continuing the conversation by highlighting and responding to this story.