<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://chag60460.github.io/fritter-case-study/feed.xml" rel="self" type="application/atom+xml" /><link href="https://chag60460.github.io/fritter-case-study/" rel="alternate" type="text/html" /><updated>2026-08-22T06:57:38+00:00</updated><id>https://chag60460.github.io/fritter-case-study/feed.xml</id><title type="html">Fritter, A Social Feed Redesign</title><subtitle>A design case study: research, concept design, critique, and implementation for a healthier social feed.</subtitle><entry><title type="html">A6 Fritter Backend</title><link href="https://chag60460.github.io/fritter-case-study/fritter/2022/10/29/fritter-frontend.html" rel="alternate" type="text/html" title="A6 Fritter Backend" /><published>2022-10-29T00:00:00+00:00</published><updated>2022-10-29T00:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/fritter/2022/10/29/fritter-frontend</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/fritter/2022/10/29/fritter-frontend.html"><![CDATA[]]></content><author><name></name></author><category term="fritter" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">A5 Fritter Backend</title><link href="https://chag60460.github.io/fritter-case-study/fritter/2022/10/13/fritter-backend.html" rel="alternate" type="text/html" title="A5 Fritter Backend" /><published>2022-10-13T00:00:00+00:00</published><updated>2022-10-13T00:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/fritter/2022/10/13/fritter-backend</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/fritter/2022/10/13/fritter-backend.html"><![CDATA[]]></content><author><name></name></author><category term="fritter" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">A4 Fritter Review and Refinement</title><link href="https://chag60460.github.io/fritter-case-study/fritter/2022/10/06/fritter-review-and-refinement.html" rel="alternate" type="text/html" title="A4 Fritter Review and Refinement" /><published>2022-10-06T00:00:00+00:00</published><updated>2022-10-06T00:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/fritter/2022/10/06/fritter-review-and-refinement</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/fritter/2022/10/06/fritter-review-and-refinement.html"><![CDATA[]]></content><author><name></name></author><category term="fritter" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">Application State, Conceptually</title><link href="https://chag60460.github.io/fritter-case-study/blog/2022/10/03/lecture-eight-blog.html" rel="alternate" type="text/html" title="Application State, Conceptually" /><published>2022-10-03T20:30:00+00:00</published><updated>2022-10-03T20:30:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/blog/2022/10/03/lecture-eight-blog</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/blog/2022/10/03/lecture-eight-blog.html"><![CDATA[<p>It’s so exciting to start connecting all the concepts together and consider how to program the whole application. I find it fun (also challenging) to shift from designing a state into coding a state. The way I understand today’s lecture—instead of using mathematical notions like unions and sets—is through the analogy of OOP (once again, similar to my blog on L5).</p>

<p>I sort of see the concept as a type of class that we are constructing. It acts both as a constructor and a “blueprint”. The states associated with this concept are thus almost like inherited classes, yet they are also part of what makes the concept a “class”. In other words, the concept is only valid with the presence of these children classes. To ensure that states are independent with each other, they are also their own class while sharing the same parent class with other states.</p>

<p>The actions, in my analogy, are like dunder methods in the concept class, yet they are not fully defined in this class unless more than one states use the same action. In terms of OOP, each action (dunder method) is then extended in the state class and fully defined there. They can be like “setter” and “getter” methods that affect each state. However, the constraints present in each state (invariants) prevent certain things from modified (such as a folder can’t contain itself or be moved into itself). On the other hand, two states’ actions can jointly affect another state, while the three states remain independent.</p>]]></content><author><name></name></author><category term="blog" /><summary type="html"><![CDATA[It’s so exciting to start connecting all the concepts together and consider how to program the whole application. I find it fun (also challenging) to shift from designing a state into coding a state. The way I understand today’s lecture—instead of using mathematical notions like unions and sets—is through the analogy of OOP (once again, similar to my blog on L5).]]></summary></entry><entry><title type="html">A3 Fritter Converge</title><link href="https://chag60460.github.io/fritter-case-study/fritter/2022/09/30/fritter-converge.html" rel="alternate" type="text/html" title="A3 Fritter Converge" /><published>2022-09-30T00:00:00+00:00</published><updated>2022-09-30T00:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/fritter/2022/09/30/fritter-converge</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/fritter/2022/09/30/fritter-converge.html"><![CDATA[]]></content><author><name></name></author><category term="fritter" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">Authentication, The Third Culture</title><link href="https://chag60460.github.io/fritter-case-study/blog/2022/09/28/lecture-seven-blog.html" rel="alternate" type="text/html" title="Authentication, The Third Culture" /><published>2022-09-28T21:30:00+00:00</published><updated>2022-09-28T21:30:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/blog/2022/09/28/lecture-seven-blog</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/blog/2022/09/28/lecture-seven-blog.html"><![CDATA[<p>In today’s lecture, we talked about Tim Ticket’s visitor authentication method. On a concrete level, it asks for the user’s phone number. On a more conceptual level, it uses the number as a token for authentication. Some concerns associated with such authentication include that it is costly and can be simplified.</p>

<p>I can’t help but think back to when my roommate from last year first started cross-registering and tried to access campus. It was when CovidPass was still active. In order to gain access to campus buildings, she needed to put in her ID number in CovidPass. In order to log into Atlas, she needed to physically visit E17 and activate her student ID. This created a deadlock situation for her, because my ex-roommate did not feel comfortable going to E17 without a valid attestation in CovidPass. Desperate, she asked me to set up a Tim Ticket for her. I followed the instructions. When I saw “Valid” on the screen, I thought it was all set to go, only to find out that it still didn’t work for her when she tried to access campus. I did not know about the additional steps on the visitor’s side or the timed QR code until this lecture!</p>

<p>Authentication is a means of protecting people’s privacy and prevent data leak, yet it sometimes also makes things complicated. I remember when I was first setting up MIT Certificate and Duo. It was in the COVID year. As a third cultural kid, I moved around a lot and happened to be abroad in Shanghai during that time. With internet latency and VPN issues, I had to send multiple emails to eventually resolve it. This got me start thinking about where authentication and accessibility collide: is there a middle ground that the two could meet in?</p>]]></content><author><name></name></author><category term="blog" /><summary type="html"><![CDATA[In today’s lecture, we talked about Tim Ticket’s visitor authentication method. On a concrete level, it asks for the user’s phone number. On a more conceptual level, it uses the number as a token for authentication. Some concerns associated with such authentication include that it is costly and can be simplified.]]></summary></entry><entry><title type="html">Hotel California, Spirited Away</title><link href="https://chag60460.github.io/fritter-case-study/blog/2022/09/26/lecture-six-blog.html" rel="alternate" type="text/html" title="Hotel California, Spirited Away" /><published>2022-09-26T22:00:00+00:00</published><updated>2022-09-26T22:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/blog/2022/09/26/lecture-six-blog</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/blog/2022/09/26/lecture-six-blog.html"><![CDATA[<p>When the term “roach motel” first popped up in lecture, I thought it was referring to a dirty motel filled with cockroaches. Then when the demo about deleting an Amazon account showed up, Professor Satyanarayan mentioned how having an Amazon account is like entering “Hotel California”. You can literally “checkout anytime,” but you can “never leave” your account!</p>

<p>I thought the above play on words in deceptive design is brilliant. In fact, the idea of “easy entrance, difficult exit” can be applied in multiple contexts. For example, it’s easy to register for certain classes, but people then need to work hard to pass the class. More famously, Hayao Miyazaki’s film “Spirited Away” actually employs this idea.</p>

<p>Within the film, Chihiro’s family accidentally entered the spirit world after driving through a tunnel. The street in the spirit world is filled with restaurants, where there is seemingly delicious free food. Chihiro’s parents are turned into pigs after eating the food. To turn her parents back into human and leave the spirit world, Chihiro has to help out with the bathhouse in the spirit world. Moreover, she has to identify her parents from a group of homogenous looking pigs!</p>

<p>It cool to see how “roach motel” establishes an archetype for many media, and even real life examples. I look forward to the next lecture.</p>]]></content><author><name></name></author><category term="blog" /><summary type="html"><![CDATA[When the term “roach motel” first popped up in lecture, I thought it was referring to a dirty motel filled with cockroaches. Then when the demo about deleting an Amazon account showed up, Professor Satyanarayan mentioned how having an Amazon account is like entering “Hotel California”. You can literally “checkout anytime,” but you can “never leave” your account!]]></summary></entry><entry><title type="html">Summer Night, Escape Room</title><link href="https://chag60460.github.io/fritter-case-study/blog/2022/09/21/lecture-five-blog.html" rel="alternate" type="text/html" title="Summer Night, Escape Room" /><published>2022-09-21T21:00:00+00:00</published><updated>2022-09-21T21:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/blog/2022/09/21/lecture-five-blog</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/blog/2022/09/21/lecture-five-blog.html"><![CDATA[<p>Have you ever watched Myth Busters, where the crew revealed the mechanism behind a certain product? This experience is what I felt in today’s lecture, where we got to the core of concept design. From today’s lecture, we learned that many underlying concepts behind a design are synced together, allowing room for automation. For example, the airplane bathrooms couple turning on light and locking the door, while light switches decouple brightness and on-off switch. This is absolutely eye-opening, and I feel like an audience taking a peek behind the curtains at an auditorium.</p>

<p>Coming up with sync rules for the underlying concepts is such a fun process. It reminds me of my experience being in an escape room two years ago. At 9pm at night, my friends and I spontaneously decided to go to an escape room in the downtown area. The space has three rooms in total, where we had to use clues to figure out how to get out of the previous room in order to reach the next room. Looking for clues inside each room is like finding the underlying concepts behind each design. We have to know what purpose each concept serves and what action/state such a concept support. This is analogous to finding the scope of the clue in our escape room.</p>

<p>The next step in concept design is to figure out where the concepts stand in relation to each other, which we call synchronization. This is, in my opinion, a super fun process. It is like connecting the clues together in an escape room. Part of this process involves meticulous calculation and thinking outside of the box. On one hand, we want to user to feel comfortable using our design. On the other hand, we want to be innovative.</p>

<p>Finally, we are able to achieve automation. This is just like opening the door and advancing into the next room in an escape room! It is when the framework of a product is complete and the user can test run it.</p>]]></content><author><name></name></author><category term="blog" /><summary type="html"><![CDATA[Have you ever watched Myth Busters, where the crew revealed the mechanism behind a certain product? This experience is what I felt in today’s lecture, where we got to the core of concept design. From today’s lecture, we learned that many underlying concepts behind a design are synced together, allowing room for automation. For example, the airplane bathrooms couple turning on light and locking the door, while light switches decouple brightness and on-off switch. This is absolutely eye-opening, and I feel like an audience taking a peek behind the curtains at an auditorium.]]></summary></entry><entry><title type="html">A2 Fritter Diverge</title><link href="https://chag60460.github.io/fritter-case-study/fritter/2022/09/20/fritter-diverge.html" rel="alternate" type="text/html" title="A2 Fritter Diverge" /><published>2022-09-20T00:00:00+00:00</published><updated>2022-09-20T00:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/fritter/2022/09/20/fritter-diverge</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/fritter/2022/09/20/fritter-diverge.html"><![CDATA[]]></content><author><name></name></author><category term="fritter" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">Modularity, from Their Side</title><link href="https://chag60460.github.io/fritter-case-study/blog/2022/09/19/lecture-four-blog.html" rel="alternate" type="text/html" title="Modularity, from Their Side" /><published>2022-09-19T21:00:00+00:00</published><updated>2022-09-19T21:00:00+00:00</updated><id>https://chag60460.github.io/fritter-case-study/blog/2022/09/19/lecture-four-blog</id><content type="html" xml:base="https://chag60460.github.io/fritter-case-study/blog/2022/09/19/lecture-four-blog.html"><![CDATA[<h1>Modularity, from Their Side</h1>

<p>Today’s lecture went over software modularity. Specifically, we got to learn about concept design. This involves three steps</p>

<li>1) Name the Concept</li>
<li>2) Say the Purpose</li>
<li>3) Explain the Operational Priciple</li>

<p>I never knew that designing a user interface (front-end) involves such meticulous process. It is very eye-opening, and I can’t help but see a parallelism between code modularity (in OOP) and concept design.</p>

<p>When developing an object, we first want to define the scope of the program. This is somewhat analogous to naming a concept. For example, if I want to some sort of program that helps me to process of database, I would name such a class something related to “data_processor”.</p>

<p>After we’ve defined the scope, we can start adding attributes. This step here is similar to saying the purpose of a concept. Python-ically, it is like adding dunder methods to a class. The focus here is to give an overview of what the class is capable doing, just like informing users of what the concept does in concept design.</p>

<p>Finally, we can actually define the attributes by adding code and docstring, thereby fulfilling each method’s functionality. This step is like explaining the operational principle of each concept. We are able to see what how each concept works and how it’s used to fulfill its purpose, just like in OOP.</p>

<p>Overall, the lecture today is quite insightful. It helps me to see that many things related to software development can be interdisciplinary. I look forward to the next lecture.</p>]]></content><author><name></name></author><category term="blog" /><summary type="html"><![CDATA[Modularity, from Their Side]]></summary></entry></feed>