Konjo
In progressKonjo is for people who want to get more done and stay organised in a day full of notifications. Productivity apps tend to add more lists, alerts and settings when what is missing is focus. Konjo helps you decide what to do next, start without friction and keep going without relying on willpower alone. Coming soon to Google Play.
Learn more
- Works offline: data lives in a SQLite database on the phone and the app never waits on the network. It syncs only the changes since the last sync with a Spring Boot backend (Java 21, PostgreSQL and Redis); if two changes conflict, the most recent one wins.
- XP is stored as an append-only log of events, so the total always adds up and can be audited. On top of it sit 70 tiered achievements, and sleep, steps and heart rate are correlated with productivity.
- The architecture and the decisions are mine; the agents work inside a seven-stage pipeline. Before any code is written, each change goes through design and a security review checked against the OWASP Top 10. Afterwards, a weighted score decides whether it moves on or goes back. The backend build fails below 80% line coverage, and a hook stops the agents from accessing sensitive data.
- My own RAG served over MCP: a FAISS index of the 33 spec documents that rebuilds itself when one changes, so the agents look up the passage they need instead of loading a whole spec. In its benchmark it answered 15 of 15 queries with 72% fewer tokens.