Mobile UX: Source-by-source evaluation flow #110
Description
Problem
The current evaluation interface shows all properties for a politician at once, with an iframe showing the archived source. This doesn't work well on mobile:
- Can't show properties and source side-by-side
- Too many properties to fit in a drawer
- Users need to mentally track which properties came from which source
- Comparing properties (e.g., "mayor" vs "mayor of Amsterdam") requires seeing all at once
Proposed Solution
Change the evaluation flow from politician-centric to source-centric:
Instead of: "Here's a politician with all their properties, verify them"
Becomes: "Here's source 1 of 4. We extracted these 2 properties from it. Accept or reject?"
Mobile UX
- Full screen: Archived page with highlights applied
- Small drawer at bottom: Properties extracted from THIS source only (1-3 items typically)
- Existing data: Show relevant Wikidata properties alongside to help users decide (e.g., reject generic "Mayor" when "Mayor of Amsterdam" already exists)
- Navigation: Linear flow through sources (Source 1/4, 2/4, etc.)
Desktop
- Side-by-side layout can remain, just paginated by source instead of showing everything at once
Benefits
- Simpler mental model (linear flow)
- Context is inherent (source and its properties are paired)
- Drawer is viable (small content)
- Helps with property comparison by showing existing Wikidata data
- Works on mobile without building custom tab bars