The WFP just released Hunger Map Live — a real-time global food insecurity dashboard. The timing felt right to contribute back.
Today we're open sourcing the Djowda platform architecture: a miniature reference implementation of one food ecosystem component, built on top of the DIFP protocol concept.
👉 github.com/Moses-Code-Dev/FoodSecurity-DIFP-Android-Playground
A note on what this is
The production codebase is going through a sanitization process — a single production component sits at ~250k lines of code. This release is intentionally simplified so that developers and AI tools can ingest the core architecture without noise.
The full codebase will be released gradually at github.com/Djowda over the coming months, component by component.
What you can build on top of this
🌍 Next-gen food coordination infrastructure
The DIFP protocol is designed for internationally interoperable food coordination. The repo is a working starting point. A Tunisian cooperative and an Indian marketplace speaking the same protocol, with zero custom integration — that's what this is pointing toward.
📍 Geo-targeted food discovery on live maps
The MinMax99 spatial grid bakes location into every message. Hyper-local, cell-based food visibility — collaborative, affordable, or free for producers who need reach without a marketing budget.
🎮 Interactive map engine for games
The MinMax99 grid is essentially a ready-made spatial coordinate system. Lords of Mobile-style interactive maps, powered by native in-device Android code, are a natural derivation. The IP is there if you want to use it.
6 Challenges for the community
These are genuine open problems. If you work on any of them, open an issue or share what you find.
Challenge 1 — Web version across 6 components
Build a web implementation covering at least 6 different food ecosystem component types (farmer, store, wholesaler, restaurant, delivery, user) that all speak the same DIFP protocol without breaking interoperability. Bonus: make them federate across two independent nodes.
Challenge 2 — Jetpack Compose port
Rewrite the existing component in Jetpack Compose. A good test of how well the architecture holds up across UI paradigms — and a useful contribution if you get it right.
Challenge 3 — Android Gemini fused response renderer
This one is genuinely unsolved and widely needed: build an Android library for rendering mixed UI from a single AI response message — text, chart, grid of items, and action buttons all in one response surface. The current Gemini SDK on Android doesn't handle this cleanly. If you solve it, it's useful well beyond this repo.
Challenge 4 — MinMax99 map overlay
Overlay the MinMax99 grid as a layer on top of existing map engines — Google Maps, OpenStreetMap, Mapbox. Build a layer switcher. Visualize cell boundaries, cell IDs, and participant density per cell. This would be a powerful tool for anyone using the protocol.
Challenge 5 — Stress test at scale
Simulate millions of concurrent users on the coordination layer. Document what breaks first. We have assumptions about Firebase fan-out performance at scale that have not been tested under real load. If you run this, share the numbers.
Challenge 6 — AI coding benchmark
Can your AI coding tool produce a production-ready DIFP component from the spec alone?
Test it. Take the DIFP v0.2 specification, give it to Claude, Gemini, Copilot, or whatever tool you use, and ask it to build a conformant node component. Document what it gets right, what it misses, and where the spec needs to be clearer. This is useful both as a benchmark and as protocol feedback.
Repo details
License: AGPL-3.0
Protocol: DIFP v0.2 (message envelope + spatial grid)
Platform: Android (Java)
Status: Miniature reference — full releases at github.com/Djowda
⚠️ Before publishing any derivative app: rename the package identifier to avoid Play Store conflicts. The Djowda name and logo are trademarks — see the README for full notices.
Links
- 📦 Playground repo: github.com/Moses-Code-Dev/FoodSecurity-DIFP-Android-Playground
- 📄 DIFP Protocol Spec: djowda.com/difp
- 🏗 Full platform (coming): github.com/Djowda
- 🌍 WFP Hunger Map: hungermap.wfp.org
We built this in the open because the food coordination problem is bigger than any one team. The repo is yours — fork it, break it, build on it, and tell us what you find.
Top comments (1)
The MinMax99 grid is the architectural signal. Most food security platforms start with listings, here's what's available. You started with location as the primary key baked into every message. That's not a feature choice. That's a protocol decision that changes what kinds of questions the system can answer. Not "where is food" but "who can reach it." The difference between inventory and access is the difference between a directory and a coordination layer. The open challenges list is honest. Challenge 3 (mixed UI from a single Gemini response) is the one no one has solved well. If someone cracks that, it's useful everywhere, not just here.