Back to projects

AmanMemilih

Indra Mahesa
Indra Mahesa Software Engineer
Civic Tech Web3 Mobile
github.com/orgs/amanmemilih

What if a national vote recapitulation workflow could be altered by one weak admin credential or a man-in-the-middle attack? That question stopped feeling theoretical during the 2024 Indonesian general election cycle. Our team kept seeing the same pattern in the field: data that did not line up, heavy reliance on centralized control, and trust that lived in people instead of verifiable systems.

AmanMemilih started as our semester project at Telkom University and grew into a civic-tech stack we still talk about with pride. The idea is simple to say and hard to build: make vote recapitulation transparent, tamper-resistant, and easier for operators who are under pressure at the TPS. We were not trying to replace the entire electoral system overnight. We wanted a reference architecture that showed how Web3, blockchain, and distributed storage could answer a very specific fear: that recap data could be changed after the fact without anyone noticing.

That meant immutable anchors on chain where it mattered, IPFS for files that should not live on a single VPS, and product flows that do not assume the admin panel is always honest. It also meant designing for real users, not a hackathon demo. Operators need speed. Supervisors need audit trails. Citizens need a reason to believe the number they see is the number that was reported.

Public-facing transparency layer
Public-facing transparency layer The Next.js dashboard is where recap data is meant to be read, not hidden. We designed this surface for stakeholders who need to audit flows without digging through opaque admin panels: clear hierarchy, status that reads at a glance, and a path from summary to detail that matches how operators and supervisors actually ask questions in the field. This is the amanmemilih-nextjs side of the house, the layer most people mean when they say they want election tech to feel open.

Behind the dashboard we split responsibilities the way you would on a product that has to survive maintenance. Flutter handles the operator path on the ground. Go and Express back the APIs and integration points. Docker ties environments together so a new contributor is not guessing which port is which. When we argued about security, it was never abstract. We asked what happens if credentials leak, if traffic is intercepted, if someone tries to rewrite a submission after midnight. Those questions shaped both the schema and the UI copy.

Mobile flow for operators in the field
Mobile flow for operators in the field Most of the pressure lands on Sirekap-style operators: count fast, report accurately, and do it on a phone in noisy, high-stakes conditions. This screen reflects the mobile-first thread Aaron drove in Figma, from lo-fi wireframes to hi-fi prototypes, plus the personas and use-case diagrams we used to keep stakeholders honest. My engineering work focused on keeping those interactions feasible: API shapes, client state, validation, and feedback that reinforces traceability instead of looking polished only in a mockup.

We studied how Sirekap-style workflows behave in the real world, not only on slides. Deadlines, partial connectivity, and the stress of reporting upward all show up in small UX decisions: where confirmation lives, how errors read, what happens when a sync fails and the operator is still standing in front of angry witnesses. Good civic tech is boring in the right places. The exciting part should be that the data survives scrutiny, not that the button glows.

On the engineering side I spent a lot of time aligning what the mobile and web clients promised with what the APIs could prove. That included recap payloads, status transitions, and the hooks we needed so a supervisor could reconstruct a story later. Aaron pushed on trust through design: visual cues, feedback loops, and flows that make tampering feel harder because the system expects verification, not blind faith. Wildan, Yazid, and Rifqi rounded out implementation and integration work so we were not a single-repo semester throwaway.

The team behind the build
The team behind the build This is us at Telkom University while AmanMemilih was taking shape: Aaron Joseph Karel Daimbani, Indra Mahesa, Wildan Syukri Niam, Yazid Al Ghozali, and Rifqi Alghifari. Campus projects often die after presentation day. We kept going because the problem felt bigger than a grade. Election integrity is not a niche topic in Indonesia. It is something everyone has an opinion about, and many people have a story about data that did not match what they saw on the ground.

You can follow the code in the open at github.com/amanmemilih: amanmemilih-nextjs, amanmemilih-flutter, go-amanmemilih, amanmemilih-express-api, and amanmemilih-docker. Forks and stars are nice. What matters more is a coherent multi-repo story you can actually trace, not a single README and a prayer.

AmanMemilih is more than a campus prototype. It is a civic-tech bet that election integrity deserves infrastructure you can verify. Your vote should rest on democratic pillars you can inspect, not luck. We kept building after the semester ended because that bet still feels worth making.