WesAdmits 2.0

A new website to compile four wesadmits facebook groups into one website. 

My role: UX research, UX/UI design,  Front-end coding ( html5, css)

Context & Overview

Wesleyan has 4 Facebook groups (WesAdmits20XX), divided by class year (although anyone from any class year can join whichever group). Here, people post requests for rides, lost and founds and other miscellaneous things. This is a clearly inefficient system, although it is the only existing way that meets the needs of students. I wanted to create an app that made these ride requests, lost and found posts, etc. more efficient. Right now, I have to post my request on all 4 batch groups, hoping someone will answer. On user’s feeds, not everything is sent to the entire student body, and my post may

potentially just fade away. I sought an engineer to help me with the backend and I designed the beginnings of the user interface and coded the front-end.

Empathy & Research

Current “Product” 

I scrolled through all 4 Facebook groups (phew!) My main finding was that people posted with recurring themes: looking/ offerring a ride, losing/finding an item, announcing an event, sharing an opinion. Within these categories, people had a general “format.” For ex., ride finders gave a place, time, date, and an incentive.


After learning more about the current “product,” I made a survey and posted it on the 4 Facebook groups (~( ̄▽ ̄)~*).

Insights from Survey and Drawing User Flows

- Majority use WesAdmits to collaborate with others mostly because everyone is already on

it and it is easy to use.

- People dislike it because it is unorganized. Several suggest separating the kinds of posts.

- People actally actively search through the feed before searching via the search bar.

- People prefer messaging the person who posted, instead of commenting, because of the ease of conversation and so that others are not bombarded with lofty comments.

- Most use it for specific functions. The top functions are rides, lost and found, events and announcements.

- Search accessibility is not a main priority since people check the feed more often than not.