Inspiration
Walking through local markets in Kenya, we saw a heartbreaking irony: farmers were dumping crates of overripe mangoes and avocados into bins while just a few kilometers away, urban families were struggling to find affordable, fresh fruit. We realized the problem wasn't a lack of food—it was a lack of connection. We built Fruittie to bridge the gap between the farm gate and the dinner plate, ensuring that "perishable" doesn't have to mean "waste."
What it does
Fruittie is a real-time marketplace that synchronizes the fruit supply chain.
For Sellers: It provides a platform to list harvests immediately, reaching a wider pool of buyers before the first signs of spoilage.
For Buyers: It offers a transparent window into available local produce with integrated logistics.
The Core Impact: By reducing the "search time" and "transit lag," Fruittie extends the shelf life of produce available to consumers and secures the income of Kenyan farmers.
How we built it
Our stack was chosen for scalability and speed—essential for a market where every hour counts:
Frontend: Built with React to create a responsive, mobile-first interface for traders on the move.
Backend: A robust Node.js and Express server handling real-time listings and user authentication.
Database: MongoDB Atlas for a flexible, cloud-based document store that can handle diverse fruit varieties and seasonal data.
Logistics Integration: We mapped out transport routes to ensure that when a buyer finds fruit, they find a way to move it.
Challenges we ran into
The biggest hurdle was Data Integrity and Connectivity. Many of our primary users—the farmers—operate in areas with fluctuating internet. We had to optimize our backend to be "lightweight" and considered how to handle offline states. Additionally, navigating the GPG keyring and security configurations (like the apt-key deprecation!) during our server setup reminded us that building a secure platform requires constant learning and adaptation to modern DevOps standards.
Accomplishments that we're proud of
The "Freshness Index": Successfully creating a workflow where buyers can see the exact time from harvest to listing.
Seamless UI: Building a dashboard that Jackton and the team made intuitive enough for a farmer to use with one hand while in the field.
Full-Stack Synergy: Watching Victor’s lead, Jackton’s frontend, and Notch’s backend come together into a single, flowing user experience.
What we learned
We learned that Post-Harvest Loss (PHL) isn't just a logistics problem; it's an information problem. We deepened our understanding of the Kenyan agricultural economy and the technical necessity of moving away from deprecated tools toward more secure, modern Linux environments. We also learned the importance of "Network Access" security—balancing the need for open development with the necessity of protecting user data.
What's next for Fruitttie
Our vision doesn't stop at a marketplace:
AI Ripeness Prediction: Using computer vision to help sellers grade their fruit quality via a smartphone camera.
USSD Integration: Expanding Fruittie to work via short-code so farmers without smartphones can still list their produce.
Cold-Chain Partnerships: Partnering with solar-cooled transport providers to offer an "End-to-End Fresh" guarantee.
Log in or sign up for Devpost to join the conversation.