DEMOCRACY is a Flutter app for finding district lawmakers from an address or current location. It collects National Assembly and National Election Commission data and shows bills, votes, plenary attendance and past election results with sources.

Core capabilities

• District resolution from an address or current location
• Bills, votes and plenary attendance per lawmaker, each with its source
• Winners of the 20th–22nd elections, 22nd count results and district history
• Result display limited by the Public Official Election Act publication windows
• Apple, Kakao, Google and email sign-in, account deletion and data export

Ownership

As the only developer, I built the Flutter app, Supabase schema and Edge Functions, public-data ingestion scripts and CI.

Current status: Deployed in the Supabase Seoul region with live data (254 districts, 299 lawmakers). Not yet released to stores; live counting and candidate analysis are in progress.

1. App-server boundary

The app never calls public APIs directly. All data goes through the bff Edge Function, and the app’s fixture JSON is the BFF response contract. The server’s contract.ts mirrors the Dart parsers so the two sides cannot drift.

2. Data ingestion

ingest-assembly and ingest-nec collect four National Assembly services and six NEC operations through nine pg_cron jobs. Plenary attendance has no open API, so per-session xlsx files are downloaded, checked against their total columns and loaded.

3. Address → district mapping

The district table in law is written against administrative dongs as of 2024-04-10. build_district_areas.ts matches today’s dong codes by code, then dong name within the same district, then legal-dong overlap, placing all 3,628 and stopping instead of guessing on ambiguity.

4. Publication limits as types

Restricted<T> is a sealed type without a value getter, so code that skips the withheld branch does not compile. Time is handled only as offset-aware KstInstant, and poll closing time comes from the server.

5. App structure

Each feature has data, domain, application and presentation layers composed with Riverpod 3 and a go_router shell. Retries apply only to dropped connections so 404 screens do not hang in loading.

6. Trust boundary and security

The server resolves districts itself through juso and V-World and ignores client-sent values. Only SHA-256 hashes of tokens are stored, never addresses or coordinates. Every table has RLS enabled with no policies, so only the service role can read it.

7. Caching and offline

The BFF caches per route: profiles 300 s, community 15 s, account no-store. When offline, the app shows the last response.

8. Open work

Live count streaming, server-side publication blocking and candidate analysis are not implemented. Pledge data has no API and is entered manually for a few districts.

The app does not call public APIs

A BFF keeps API keys out of the app and normalizes each agency’s response format in one place. The cost is managing server deployment and contract tests together.

Legal rules as types, not widget conditions

Guarding publication limits with an if on each screen is easy to miss on a new screen. A sealed type lets the compiler catch the omission.

Stop on ambiguous data

District mapping and attendance loading stop instead of guessing when unsure. Ingestion can halt, but that is better than publishing wrong political data.

Districts are resolved by the server

Trusting a client-sent district would let users post in another district’s community. The server resolves the address itself and never stores it.

Automated checks

• 468 Dart tests, 115 Deno tests and 38 golden images at 390dp
• Three CI jobs: format, analyze and test; macOS goldens; deno task ci
• A test blocking direct DateTime.now() use and a contract test making sure API keys never leak into responses

Live-data checks

• The first load left 20 district lawmakers unmatched; fixing Sejong naming and integrated-city rules brought it to zero.
• The address API returned dong names in a different form than the fixtures, dropping addresses; parsing now follows the live response.

Limits

There is no user testing or production metric yet.

Done

• District resolution from address or location, and a district home
• Bills, votes and attendance per lawmaker with sources
• 20th–22nd election winners, 22nd count results and district history
• Four sign-in methods, account deletion and data export
• Deployment in the Supabase Seoul region with CI

Next

• Live counting and server-side publication blocking
• Wider pledge data coverage
• Store release