pull down to refresh

Really like the strict on-device approach — rare to see that level of discipline.

Curious about the data model: how are you structuring route storage over time?
Do you optimize for long-term history (many walks) or assume relatively lightweight usage per user?

Also, for the goshuin seal flow — have you considered making it exportable in a verifiable way (e.g. signed locally), or would that conflict with the privacy-first design?