Group Project
Planty
A web platform offering monthly planting kits with guides, tips, and disease detection resources for beginner gardeners.
Project
Group
Platform
Web
Tech Stack
Laravel, Tailwind CSS, MySQL, Midtrans
Role
Designer and Frontend Developer
What the app does
- Monthly Kit Subscription
Users can subscribe to monthly planting kits delivered with seeds, soil, and care instructions.
- Plant Learning Hub
Guides on how to grow different types of plants, from herbs to flowers and vegetables.
- Disease Spotting Tips
Educational resources to help identify and prevent common plant diseases.
- Seamless Checkout
Integrated Midtrans payment gateway for secure and real transaction flows.
Key takeaways
- Learned how to apply agile scrum to organize tasks, manage sprints, and track progress effectively.
- Implemented real payment integration using Midtrans for a subscription-based model.
- Designed and developed a responsive web interface for both learning content and e-commerce flow.
Tech stack
Links
Long story
Planty started as a simple idea: make gardening easier and more accessible for everyone. We wanted to create a service where users could subscribe to monthly planting kits and also learn about planting through curated content, from how to grow different types of plants to identifying early signs of disease.
This was my first project that fully embraced the agile scrum framework. At the beginning, our team struggled with sprints and story point planning — we were more focused on just building features. But as we adjusted, we saw how following the framework made development smoother and more predictable.
I was responsible for the design and frontend development. We built the platform with a clean and intuitive interface, making it easy for users to explore plant guides and manage subscriptions. We also integrated a real payment gateway using Midtrans, which made the project feel much more like a real-world product.
What I took away the most from Planty was how powerful agile scrum can be when used correctly. It helped us keep progress steady, deal with technical debt quickly, and balance our workload across other commitments. By the end, we had a working product that felt both educational and practical.