Jobsite photo coverage board for your CompanyCam crews

I want an app my production manager opens every morning to see which jobsites are actually being documented in CompanyCam. It is a photo coverage board, not a report: every row is a live jobsite, and every row has actions the manager can take on the spot.

The main view lists every active project using List Projects. Filter out anything with status "deleted" and anything with archived set to true. Archived is a separate soft state from deletion, so the active jobsite filter has to check both. CompanyCam list endpoints return a bare JSON array and accept page and per_page, so page through until a short page comes back.

Each row shows the project name and address, days since the last photo, how many photos landed in the last 7 days, which crew members posted them, and the labels currently on the job. Pull photos per project with List Project Photos, which returns most recently captured first, so a bounded page is enough for both the recency figure and the 7 day count. Resolve poster ids to names with a single List All Users call cached for the whole refresh, and read the label chips from List Project Labels. Timestamps such as created_at and updated_at are Unix epoch integers, so days since last photo is epoch math rather than date string parsing.

Render the latest three to six thumbnails inline on each row from the photo uris array, picking the entry whose type is thumbnail, so the manager can eyeball coverage quality without opening CompanyCam at all. Clicking a thumbnail opens the larger web rendition in place.

Any site with no photo in more than 3 days sorts to the top in a red going dark band, ordered by the longest silence first. Everything else sits below in a normal band, also sorted by days since the last photo. Make the 3 day threshold a saved setting so the manager can tighten or loosen it per how their jobs run.

A second view flips the board around by crew: one row per CompanyCam field user showing their current posting streak of consecutive days with at least one photo, their last upload date, photos posted in the last 7 and 14 days, and which jobsites they covered. Sort the weakest documenters first so it is immediately obvious who is skipping documentation.

From a project row the manager can do four things. Nudge the crew lead with a Slack direct message, using Open a Conversation to get the DM channel for that person and then Send a Message with a prefilled, editable note naming the job and how long it has been dark. Post a reminder straight onto the job with Add Project Comment. Tag the job with a "Needs Photos" label via Add Labels to Project. Attach the standard documentation checklist by picking a template from List Checklist Templates and calling Create Project Checklist from Template.

Persist a mapping the manager fills in once: each CompanyCam user matched to their Slack member ID, plus which crew member is the lead on each project, so the nudge button knows who to message. Also persist the going dark threshold, the default label name, the default checklist template, and when a nudge was last sent per project, so a row that was already nudged today shows "nudged 2h ago" instead of inviting a second ping. Store all of this per user of the app.

CompanyCam allows 240 GET requests per minute per token, so fan the per project photo and label fetches out in small batches with bounded concurrency, cache the user list for the duration of a refresh, and give the manager a manual refresh control rather than polling in the background. Where a cheap refresh is possible, use the modified_since filter with an ISO8601 timestamp. If one call fails, keep the rest of the board rendered and mark just the affected row. Show a clear empty state when there are no active projects, and if Slack is not connected, disable only the direct message button while the comment, label, and checklist actions keep working.