The problem: UHM students have a “rapid” churn rate in goods and services. Students leave the dorm for an on-campus apartment and need to get rid of dorm-specific stuff and acquire apartment-specific stuff. Students graduate and need to get rid of stuff because they’re moving off-island. There is therefore a tremendous amount of “campus-specific” goods and services that could be more effectively recycled and reused if there was an effective marketplace for these specific kinds of items.
The solution: The Manoa Flea Market is an application for UHM students to facilitate buying and selling of student-related goods and services.
It is similar to Craigslist, except for the following:
These factors make Manoa Flea Market an attractive alternative to Craigslist.
When designing your version of this application, keep the following in mind:
Roles: There are at least two roles in this system: users and administrators. Users are UH students who can buy or sell goods and services. Administrators are special users who have the ability to monitor the behavior of users in the system, ban users who violate the conditions for use of the system, and create new categories and other functionality.
Categories: Similar to Craigslist, there are broad categories for goods and services. One obvious pair of categories is “Textbooks to sell” and “Textbooks wanted”. There are no “hookup” categories (i.e. Men seeking Women, etc.). You will need to do some research to figure out the appropriate set of categories.
Notifications: By default, communication occurs via UH email, but students can also elect to receive information via text message. To do this, they must specify both their mobile phone number as well as their provider (i.e. Verizon, AT&T). Most providers have an “SMS gateway” mechanism that will enable your app to generate a text message to them. (Another alternative is Twilio, but that costs money).
Alerts: Users can set up alerts, for example if they are looking for a sofa, or a particular textbook, or whatever. Then they are automatically notified when that item is listed for sale.
Photos: The system must support photos. Initially, images can be specified as URLs, but the final version should support uploading of photos.
Complaints: Users can mark content or other users as inappropriate. The admins must resolve these issues and ban users who violate the Terms of Use.
For useful Meteor code examples, be sure to see the Meteor 4 module.
Note: if you choose this idea for your final project, you cannot name it “Manoa Flea Market”! Come up with a different name for your final project.
Some possible mockup pages include:
Whether or not the following bullet points list all pages or not, the completed use case should show an end-to-end scenario of using the system.
After implementing the basic functionality, here are ideas for more advanced features: