Ways to collect · Joripo documentation

	Joripo Collect	ODK Collect	Web forms
Runs on	Android 8.0 or newer	Android	Any modern browser
Works offline	Yes	Yes	No: the page needs the server
Signs in with	The person's Joripo account, on an approved phone	A device key (QR code), or email and password where the owner allows it	A Joripo account, or nobody if the form allows anonymous access
Runs every Joripo feature	Yes: the same engine as the tester	Standard XForm features only (what differs)	Yes: the same engine as the tester
Case lists	Yes	No case screen	No
Text and audio audits	Both	As ODK Collect records them	Text audit; audio where the browser can

Joripo Collect is the recommended way for fieldwork: one engine runs the tester, web forms and the phone, so what works in the tester works in the field, and the phone is tied to a person, approved by you, and stoppable at any time.

ODK Collect works unmodified, for teams that already use it. It runs the standard part of a form; a form using a function only Joripo's runtime implements will not open in it, and the upload warns you.

Web forms suit respondents filling a form themselves, and enumerators on a laptop or a tablet with a connection.

What happens when a submission arrives

The server checks who sent it: an approved phone's key, a device key, a signed-in person, or an anonymous web form the form allows. Anything else is refused, and the phone keeps the form to send again.
The submission and its attachments are written to the server's file store, attachments first and the submission last, so a crash never leaves half a submission. The device is told it was received (OpenRosa's 201) only once it is stored; a device that hears anything else keeps the form and tries again.
It is indexed, and the quality checks that look at one interview run on it.
If the form's review workflow is on, it starts awaiting review; if the workspace has a case list, the case it names is updated.
It appears under Monitor at once.

A stored submission is never lost because a later step failed: if indexing fails, the file is still on disk, and the server indexes anything on disk it does not know at its next start.

When collection stops

Nothing is accepted for a workspace that is archived or deleted, or for an organisation that is suspended: phones keep their finalized forms and send them if it is restored. The Web data collection switch turns every web form of a workspace off at once. Revoking a phone or a device key stops only that one.