The Core User Flow

The Core Mandate: People don’t lack care; they lack coordination and trust. Visita removes the friction that stops willing people from acting.

The Visita Core User Flow is built on a simple premise: “I see a problem → We fix it → Everyone sees it”

​

0. Entry (Light Onboarding)

How a user arrives without pressure.

• Triggers: QR code, WhatsApp link, seeing a problem in real life, or a ward meeting invitation.
• Philosophy: “You’re not joining a platform — you’re stepping into your place.”
• Action: Light onboarding with just Name + Optional Photo + Skill Tags. No ideology, no party.

​

1. The Fork (Critical Choice)

The user chooses one path immediately. There is no guilt and no lock-in.

​

2. Reporting a Problem

The “Hole in the Ground” principle. A problem must be actionable.

1. Pin: Map-based location (GPS or manual drop).
2. Define: Structured prompts (What? Why? Urgent?). No ranting.
3. Translate: System converts complaint to a task list (e.g., “Blocked drain” -> “Clear debris, Check damage”).

​

3. Community Activation

Silent but powerful coordination.

• Local Visibility: Problem becomes visible to neighbors and skill-matched residents.
• Micro-commitments: Users click “I can help” (Time, Skill, Resource).
• No Virality: Only proximity relevance. No algorithmic amplification of outrage.

​

4. Trust & Coordination Layer

The Task Room opens. This is a focused action space, not a forum.

• Features: Task checklist, Who’s doing what, Time/date agreed.
• Chat: Task-bound, time-limited, archived after completion.
• Rule: No endless debate. Action over opinion.

​

5. Offline Action

The real work happens offline. Visita supports it, not replaces it.

• People meet.
• Work is done.
• Photos/videos taken during action.

​

6. Proof, Closure & Reputation

Trust is built through verification.

1. Completion: Before/after media uploaded. Task marked “Completed”.
2. Validation: Neighbors confirm the fix. Phase out “likes” in favor of verification.
3. Reputation: Contribution record updates (Tasks completed, Reliability score).

​

7. Meaningful Identity

Reputation that actually means something.

• Non-gamified: No streaks or dopamine loops.
• Deeply meaningful: “That person who always shows up.”
• Stats: Roles played (Fixer, Watcher), Reliability Score.

​

8. Escalation Path

When local action isn’t enough (Institutional Escalation).

• Auto-generated report: With evidence and community backing.
• Recipient: Municipality / NGO / Business.
• Result: Pressure without chaos. Clear proof and public timeline.

​

9. Memory & Momentum

Building the Ward’s Institutional Memory.

• Solved Problems: A record of what has been fixed.
• Contributors: A history of who served.
• Psychology: New residents see “Things actually happen here.”

---

​

Critical Design Principles

This flow quietly rebuilds trust without preaching, filters talkers from doers, and restores dignity at the ground level.