Skip to main content

Orwell App: 3rd Place Congressional App Challenge [NJ06]

 



In October, I worked on a legislative engagement app, Orwell, and submitted it to the Congressional App Challenge along with two Tanushes and a Winston from my school.

Problem: Only 47% of youth showed up to vote in the last election cycle 
This problem seemed essential to me. Beyond my own personal interest in national + world affairs, this statistic kept me: why doesn't youth-- the group with arguably the most at stakes-- show up to vote in the country? Democracy is built upon the necessity of civic engagement! 


Solution: We found that a lot of youth doesn't end up voting because a) they don't understand policy b) they don't find policy accessible or c) they don't think policy impacts them personally. In our app Orwell, we break down recent bills passed in Congress, create a "personal impact summary" by showing how bills affect someone specifically based on demographic account information, and make information accessible by creating fun quizzes and animations to the app. We also add streaks and points and a leaderboard in an attempt to gameify civic engagement. 


Some cool skills I learned along the way: 
*ML: I got to really deep dive into ML here and learn how to use Hugging Face models + create my own sentiment analysis pipeline. I've been wanting to do this for a while now because it is such a useful tool to have in your pocket, and Orwell finally gave me an opportunity to work with LLMs, NLP, and webscraping too. 
*JS animations: making bills run across the page (our mascot for the app) was some of the most rewarding frontend work I did (along with the trumpet we played when someone logged into the app)
*Choosing a...better team (how do I put this nicely?): my team did what they could with the time they spent on it I suppose. However, I ended up heavylifting 90% of the work after coming up with the idea as well. I still remember asking Christina Asquith (Hack Club Co-Founder) how to better choose cofounders for a future venture..."choose people whose skill you can attest to, will be committed, and those you don't have a problem spending free time with." I will not forget that advice again. 
*Leave more time for presentation + revision in these kinds of projects. I am so excited we got an award from all the apps in our district for this! But I definitely think that 1st prize was within reach if we just edited our video better + made some more last minute changes on the app itself...**sigh...the pain of regret** But yes, on group projects you shouldn't leave things to last minute it seems. 
*Navigating government APIs + bills: I just think it was cool to see that we ended up analyzing a bill on veterans eye lenses..like these were in the weeds kinds of acts I didn't expect our Congress to actually sit down and judge which was interesting. 
*Not writing spaghetti code: SO...I have a habit of writing messy code because usually I don't merge it with others. Like even at Pennapps, I was able to get away with it because I worked only on hardware and didn't REALLY merge code. But here there were just FILES and FILES so yeah. I had to clean stuff up a bit. 

Also. Name inspo for our app?: We named the app "Orwell" after the scene in Animal Farm in which the animals could not read the laws on the walls anymore and gave all the power on the farm to the pigs. Social and political commentary...maybe? LOL 

Overall, I loved creating Orwell, and would perhaps like to continue developing this into an actually deployable app in the future. I definitely see the problem the app is trying to solve, and I think with a few tweaks we can try making this the civic tool version of "wordle." (ambitious? maybe.) 

 Note: Why haven't a written a post since October? I've been...swamped with work and deprived of sleep (as another post on Athena and an upcoming one on Prototype and Mongol trials and moderating a cool AMA with the Netflix CTO will demonstrate). 
ANDDD our github link : ) [[disclaimer: some spaghetti code leftover]]: https://github.com/winstonbedwar/congapp.git
*note to self: add more UI images here 


Comments

Popular posts from this blog

Undershirt to mitigate + monitor late effects of breast cancer [Seamless]

This was my final project at BWSI, and part of the reason I received the Dr. Bob Berman Disruptive Tech Award for e-textiles this year for BWSI. I'm so excited about it and plan to continue it in the coming months.  I have so much to say in this post, but for now I'll just share screenshots of my portfolio document and go on and on about it when I'm not compromising on sleep lol: Up Next:  -Experimenting with more motors  -Inserting batteries  -Expanding health monitoring UI! 

NOTHOLE

nothole in the making...still integrating the sensor and ESP here what is a...nothole? Nothole is a sensor system on a car that can sense potholes + their severity + their location, and send this back to a central server application that can consolidate this data for usage by government officials and construction workers to provide for more efficient repavement of roads. This project won my group 1st place in HackMIT Blueprint's beginner track!  we had two parts: sensor (ultrasonic sensor) + server system via ESP8266   So technically...pothole detection has been done before (there are whole articles on it). What HASN'T been done before is consolidating it on a server. Ideally, we wanted to make a Google Maps application (using the JS API) but couldn't since we ran out of time in the 7 hours we had to build this. My partners, Jasper and Alex, focused on making the ultrasonic sensors work without fault + setting up the demonstration. On the other hand, I spent my hours figu...

Pennapps '25 + Sunscreen Reminder Shirt (Soliss)

^^meet wearable Soliss  So I spent most of last weekend on the floor of UPenn's Levine building (crazy deja vu I was literally right here for Upenn scioly in March). I slept 7 hours of the 36 hour hackathon and coded like mad for the rest of it (no seriously I fell asleep while CODING). I didn't win an award this time, but built a super cool FUNCTIONAL WEARABLE : D (I applied skills from BWSI!)  1) What is Soliss? Over my 36 h - 7h = 29h journey, I built Soliss with a team I found at the hackathon. This was a wearable that could track excess UV radiation hitting the skin and remind the wearer to reapply sunscreen. The wearable also connected to an app which allowed the user to track overall danger levels of UV radiation on their skin (calculated via a formal algorithm, and personalized to the user's demographic etc). Personally, I created the wearable part of the project (so all the hardware etc). In my 29 hours I prototyped/designed, breadboarded, coded, and the hardest pa...