Front-left cornerCorner 1 of 4 · GPS ±8 m

Front-left cornerTaken 25 Sep 2026, 08:44 WIB · GPS ±8 m

360° walk-aroundGPS ±8 m

360° walk-around0:41 · GPS ±6 m

360° walk-around0:12

Front-left corner

A photo didn't uploadIt's saved on this phone. We're trying again in the background, so keep going.

Fit the whole vehicle at 45°

00:14

Start at the front plate, walk clockwiseKeep walking · stops by itself at 1:00

Turn on location to take photos

Each photo records where it was taken, so the camera opens only with your location on.

Finding your location

Move near a window or outside for a moment. The camera opens as soon as there's a fix.

Turn off fake location to continue

Your phone is reporting a location from a mock-location app. The camera opens again once it reports your real location.

PHOTO

VIDEO

Use Photo

Use Video

This photo looks too darkTurn on the light, or retake it somewhere brighter.

Video too short (0:12)Walk all the way round: at least 20 seconds.

Photo check

Step 2 of 4 · Your vehicle

Checking your photosThe AI looks for blur, darkness, the vehicle and a readable plate. Up to 30 seconds. 15 photos ·

Couldn't check your photosThe photo check isn't answering right now. Your photos are safe on this phone. Try again, or continue: the check runs later and the Surveyor sees the result.

Retake these while you're next to the car, or add a reason. The Surveyor sees the AI's notes either way.

Each photo below needs a retake or a reason before you continue (Asuransi Demo's strict setting).

Rear sideRetake suggested

AI: the plate isn't readable.

Your reason: Rear plate bent after the collision.

Retake

Damage · nearRetake suggested

AI: the photo is blurry.

Retake

13 photos AI-checkedAI-checked

All 15 photos look good

Next, your documents.

Continue

You can continue now; the Surveyor sees the AI's notes and your reasons.

Continue

2 photos still need a retake or a reason.

Check finished13 AI-checked · 2 to look at.

Check finishedAll 15 photos are AI-checked.

C4 follows the iPhone camera's layout: the preview fills the screen and a veil covers what won't be kept, so the clear window, outlined, is exactly the shot: 3:4 for a photo, 9:16 for 720p video. Rear camera only, dark in every theme.
Live camera only: no gallery or file picker exists anywhere in the app (CAP-02), so there is no last-photo thumbnail either.
GPS is required (CAP-01): without the location permission the camera says how to turn it on; without a fix it waits, and opens as soon as there is one. Fake location (Android mocked, iOS isSimulatedBySoftware, #666) shows no camera at all; each refused attempt is a high signal.
The Slot fixes photo or video, so the pill shows only that mode. Close and the light are bare icons. A multi-shot Slot shows its count under the title ("Corner 1 of 4").
After each shot or video, Retake or Use: only the used one is kept, with its retake count, and Use returns to the guide. Blur and darkness are an instant hint at the top; the shot may still be used. Video stops by itself at 1:00 and is refused under 20 s, at about 2.5 Mbps. Stills keep EXIF.
Each used shot uploads in the background: a presigned PUT, or 5 MB parts that resume for video and files over 5 MB. A failed upload retries by itself while capture goes on; the file leaves the phone only once its Media item is stored, and after 5 counted failures that item alone asks for a retake.
The Quality check: one AI pass over the accepted photos, the scene photo included, when the photos are finished (video is for people; AI reads photos only). Up to 30 seconds; a toast reports the result.
The Client's mode is Lenient: Skip at any time, after a sheet that says what skipping means, and the check finishes in the background. A flagged photo shows "Retake suggested" with the AI's note; the Client may retake it, add a reason, or continue with the warning to the documents.
Strict, the Surveyor's and the Workshop's default: no Skip before the result or 30 s, and Continue waits for a retake or a reason on each flagged photo.
Tags: AI-checked, Retake suggested with the AI's note, Not AI-checked; never "verified". An outage never blocks: try again, or continue, and the check runs later.

Strict is drawn as a state to show what it would do. The Client's mode is Lenient (#180, #653); Strict is the staff capturers' default, and their capture runs these same screens with their mode (#628).
The outline is the clear window's edge. The mockup's review settled "no framing outline: the clear window is the frame" (10 Oct), newer than PRD C4's "An outline shows the expected framing".
Drafted: the no-permission notice ("Turn on location to take photos", "Each photo records where it was taken, so the camera opens only with your location on.", "Open settings"); the upload banner ("A photo didn't upload", "It's saved on this phone. We're trying again in the background, so keep going."); the check's footer line "You can continue now; the Surveyor sees the AI's notes and your reasons."; "(Asuransi Demo's strict setting)".
The check is a screen, not dialogs: Checking is a banner with its countdown and Skip in the footer, and Couldn't check a banner with Try again and Continue, since a screen's own state is a banner and progress shows only on a clicked control. Skip? and the reason stay sheets.
Finding location shows a spinner in its notice, with no button nobody pressed (the mockup's "Finding" button).
Reset goes, a button no other form has; each reason saves from its sheet, and Continue moves on in place of Save.
Fake location's Bahasa Indonesia line goes: the prototype is English only, and the app shows its catalogue in the Client's language.
Sample data: the reason reads "bent", as the staff Capture tab shows it (the mockup said "missing"); shots are dated 25 Sep 2026, as the staff Capture tab has them.

ticket #671 → comment: Without the location permission the camera shows "Turn on location to take photos" with Open settings; without a fix, "Finding your location" with a spinner and no button.
ticket #671 → comment: A failed upload shows a banner over the live camera while it retries in the background; capture goes on.
ticket #671 → comment: The clear window carries a thin outline, the shot's edge; there is still no framing silhouette.
ticket #676 → comment: The Quality check is a screen: Checking is a banner with the countdown and Skip in the footer; Couldn't check is a banner with Try again and Continue; Reset goes and Continue replaces Save. Lenient lets the Client continue with flagged photos.
ticket #656 → comment: The check covers the accepted photos and the scene photo, never the video; each flagged result carries a short note the Client reads ("AI: the plate isn't readable.").
ticket #645 → comment: The notes are written for the Client, one short line each: "AI: the plate isn't readable.", "AI: the photo is blurry."

The app is drawn in a phone frame on a wide screen; at phone width the frame drops. (12 Oct 2026)
The Client's Quality check is Lenient: a failed check warns and the Client may retake or continue; Strict blocks until retaken. The Quality check Settings screen is not drawn; it waits for #184. (12 Oct 2026)

From client-capture.html (C4 Camera and Quality check, #180) and web/claim-capture.html (the reason, the shot times); #645, #653, #656, #666, #671, #676