Problem
Drexsell was designed for a closed university community rather than a general marketplace. The product needed to make it easy for students and faculty to exchange goods while feeling specific to that environment instead of like a generic classifieds clone.
The project also had a delivery problem: the work had to ship as both a web application and a native Android companion inside the constraints of a freshman design project and a four-person student team.
Approach and architecture
The architecture split the product into two connected surfaces:
- a PHP and MySQL web application for the primary marketplace experience
- a Java and XML Android application for the mobile companion
That division let the team deliver an end-to-end system across backend, frontend, and mobile instead of reducing the project to a single interface.
Key decisions
Treat web and mobile as one product
One of the project highlights is that the backend and frontend were delivered together as one product. Extending that to a native Android companion meant the project was organized around a coherent marketplace experience rather than isolated technical exercises.
Keep the community boundary central
Because the audience was Drexel students and faculty, the marketplace needed to feel approachable for a closed community. That product constraint shaped both the scope and the design decisions more than raw feature count would have.
Coordinate across multiple stacks early
The team was working across PHP, MySQL, JavaScript, Bootstrap, Java, Android, and XML. In a short student timeline, coordinating those choices early was more important than trying to optimize any single layer in isolation.
Challenges
The portfolio data calls out three main challenges:
- keeping web and mobile experiences coherent
- designing an approachable marketplace for a closed community
- shipping across multiple stacks within a student project timeline
Together, those challenges made project coordination and product consistency just as important as implementation speed.
Outcome and learning
Drexsell delivered both the marketplace backend/frontend and a native Android companion. The durable lesson is that even student projects benefit from thinking in systems: shared product intent, clear coordination, and realistic scope matter as much as the individual technologies.
It also stands out as an early example of working across product delivery, team communication, and cross-platform engineering at the same time.