Lessons learned from replicating Monitorizare Vot to Poland

Needed adaptations

There are 3 levels of administrative boundaries. Polling station IDs are unique only to the lowest level. Changes in the interface were needed: choosing from 3 connected select boxes or putting boundary unique id by hand in select box. Changes are still needed both on API side and apps to handle such cases dynamically. it turned out we have districts that are both level 2 & level 3 at the same time..
We needed multiple forms Apps interfaces needed to be adapted
Polling stations IDs sometimes doesn't start from 1 and sometimes are not a consecutive range. Example: https://wybory2018.pkw.gov.pl/pl/obwody/146514

Time taken to adapt (over a month of work):

data
- does polling stations have unique IDs? on which level uniuqe?
types
- does polling station unique IDs are numbers? That's how it is now done in DB
Coding questions is very important! Agree on that first
also seeing how the forms will look like in the app: Are some questions not mandatory? Is it better to frame sth as a seprate question, as a extra answer within the options or as an ask to add a note.

if appstore failed you can distribute apps via Ad Hoc Provisioning Profile (up to 100 devices) but you need to get devices UDIDs (using iTunes and connected phone)
SQL profficiency helps

map where are observers
map with metrics overlayed over administrative boundaries
status of forms filled and notes count by each observer / team
simple pie charts for each questions
everyone would like to have temporal reports: see what commissions have started counting at which hour, how long did it take, etc.
total amount spend observing
number of active observers / total observers