Car Pride™
A private space for the photos people simply want to keep with their vehicle.
My Garage • photo / video evidence
Galleries / Media
Galleries / Media organizes Crank’s visual evidence — pride photos, condition photos, run media, field captures and other images/video — without making the user leave the asset/evidence workflow.
Car PrideCondition evidenceRun mediaField captures
Current capability map
What this section does.
This page describes the capability architecture represented in the current Crank development build. Interface wording may continue to be polished, but the functions below are the working product structure.
Condition photos
Pre-existing damage, service condition, rental condition or jobsite state can be documented visually.
Field captures
Photos taken during Experience Recorder, maintenance or other field workflows can be retained with context.
Motorheads media
Performance images/video can be reviewed alongside the runs that produced them.
Asset identification images
Equipment, motor, pump, gearbox and serial/model tags can be stored as reusable asset knowledge rather than one-off camera roll pictures.
Measurement-point photos
CrankScope reference images support return-to-the-same-point vibration measurements.
Local playback / review
Media remains available for in-app review without requiring social-media or cloud publication.
Intentional sharing
The operator decides when a copy leaves Crank.
Storage-aware imaging
Equipment/nameplate and reference photos can use optimized copies while preserving an explicit keep-original choice when full camera resolution is needed.
Operating flow
How it fits together.
Step 1Capture / import
Step 2Bind to asset or record
Step 3Review in Crank
Step 4Reuse as reference
Step 5Share only when chosen
Crank truth boundary: A photo is more useful when Crank knows what it is for. The architecture favors asset and record context over a generic pile of unlabeled camera files.