ZengChai

ReMo is a crucial key in the second-hand motorcycle market, inspired by the challenges faced by a motorcycle shop like Seng Cycle World. The growing demand for specialized trading platforms, ReMo is aimed to improve the buying and selling experience for both the sellers and buyers. By focusing on the user needs and market trends, ReMo aims to offer a bunch of essential features. From seamless authentication to user-friendly product management and communication tools by using WhatsApp, ReMo aims to improve the users’ experience in navigating the marketplace with ease and confidence. By using machine learning algorithms, used motorcycle pricing can be predicted. It helps to increase transaction success rates and ensure fairness and transparency for both buyers and sellers. Additionally, ReMo provides the ownership transfer procedure to offers users a seamless experience by using secure fingerprint authentication at pre-designated sites. ReMo is planning to have constant development in order to provide a better user experience within the motorcycle trading community by implementing a hybrid approach of Waterfall and Agile approaches in the system. Hence, ReMo has the ability to change the used motorcycle market and set new standards for excellence in the second-hand motorcycle industry by having its wide feature set.

• Utilized dual hosting platforms for frontend and backend, ensuring high availability and enhanced reliability through automated failover.
• Implemented CRUD operations for listings and user profiles using RESTful APIs with a repository pattern for optimized database interactions.
• Optimized API payloads with DTOs (Data Transfer Objects) and pagination, reducing frontend load time and minimizing bandwidth usage.
• Designed a multi-layered data architecture (DO/DTO) to securely decouple database entities from frontend interactions, eliminating sensitive data exposure while enforcing JWT-based authentication.
• Maintained a clear separation of concerns (UI, business logic, and data layers) for improved reusability and modularity by utilizing the MVC (Model-View-Controller) architectural pattern for the backend system and the MVVM (Model-View-ViewModel) architectural pattern for the frontend.
• Adhered to SOLID principles by using interfaces for service and repository layers, along with Spring’s dependency injection (@Autowired, @Bean), ensuring loose coupling, easier testing, and scalability.