The site has no signal. The app doesn’t care.
IssuesId is a mobile defect tracking app that treats the phone in your hand as the record. Photo, voice note, plan pin and location are saved on the device the moment you tap, and synced in the order you captured them when the signal comes back. It installs from the browser on iPhone and Android: no app store, no MDM, no per-device licence.
Everyone has lost a defect to a spinning wheel
Level three plant room, no bars, three defects in your head. The app wants to phone home before it will let you save anything, so you take the photos on the camera instead, tell yourself you will type them up in the shed, and by the time you are back in signal you have two of the three and a photo you cannot place. That is not a small failure. It is the reason site teams stop trusting a tool after one bad afternoon and go back to the notebook, and the notebook is why handover packs are missing the things that mattered.
The places with no signal are exactly the places the defects are: basements, lift cores, stairwells, plant rooms, the back half of a block before the comms riser is live. A defect tracking app that needs a connection is not a tool for those places. It is online software with a safety blanket.
IssuesId is built the other way round. The phone is the source of truth until it syncs. Every defect, photo, pin and status change is written to the device first, with no network in the loop, and the screen never waits on a request. The test we hold ourselves to: put the phone in airplane mode, capture a dozen defects with photos across four locations, close the app, reboot the phone, reopen it still in airplane mode. Every defect is there as you left it. Walk back into signal and watch them sync without a tap.
One tap, then keep walking
A defect is a photo, a place, a few words and a trade, and none of those should need typing on a landing. The photo comes from the camera or the camera roll, and an iPhone’s HEIC is decoded on the way in rather than rejected. The place comes from the QR label you scanned on the door, or the project’s location tree, not from GPS; a coordinate pair on level four points into two apartments and a corridor, and nobody has won a handover argument by reading out a longitude. The words are dictated and transcribed into text. The trade is one tap, the contractor a second, and the notification sends itself.
What gets recorded without you doing anything is the part that matters later. The capture time is read off the image on the device, so a photo taken at 9:14 in a basement and synced at 4:30 still says 9:14. The pin you drop on the drawing is stored as a ratio of the image, so it lands in the same spot on a phone screen and on an A3 PDF. And the original photo is never painted over: your circle and arrow are a separate layer drawn on top, so the untouched file is there the day someone says the picture was doctored.
What it does about conflicts, honestly
This is the question a site manager who has been burned will ask, so here is the mechanism rather than the adjective. Every offline action lands in a queue on the phone, in the browser’s own database, and the queue survives closing the app and rebooting. You can always see how many items are waiting; the counter is in the top bar. When a connection turns up the queue drains on its own, in the order things were captured, so the timeline on the server matches the order on site.
Three decisions keep six phones and a fortnight of offline work from turning into duplicates. Every record gets its identity on the device, not the server, so the defect you raised in the basement is the same defect after it syncs, with no temporary numbers to reconcile. Changes are append-only events rather than overwrites: when two people edit the same defect offline we do not pick a winner and quietly bin the loser, we replay both in timestamp order and put anything that genuinely conflicts in front of a person. And photos sync on their own, separately from the record, so a defect is complete and assigned before its 4 MB photo has crawled up one bar of 4G. The record lands first; the evidence catches up.
Installs from the browser. There is nothing to approve.
IssuesId is a progressive web app. Open the address on the phone, accept the install prompt, and it sits on the home screen and in the app switcher, launching in its own window with no browser bar. Updates download in the background and arrive as a banner with one button; tapping it reloads into the new version with your open forms and queued items intact.
That removes three objections at once. There is no app store listing to wait on and no version your IT team has to whitelist. There is no mobile device management enrolment, so a sub-contractor’s own phone works the day they arrive. And there is no per-device or per-seat licence: IssuesId is priced per active site, so every inspector, supervisor and trade on the job can have it on their phone without a conversation with procurement.
Three screens cover most of a day on site
Arrive and scan the label on the door, and the phone is already at the right room with its open items cached. The trade opens their list from an emailed link, with nothing installed and nothing to sign up for. The level summary shows what is open where, without a signal. Everything else, the reports, the workflow rules, the correspondence, is there for whoever has a keyboard, and it stays out of the way of the person with ninety seconds and one thumb.
Site phones are cheap and three years old. That is fine.
We are not going to print a battery figure, because it would be a guess about your phone. What we can tell you is what the app does not do. It does not poll GPS, because it does not use GPS. It does not need a connection to save, so it is not retrying in the background while you walk. It caches the app itself the first time you open it and does not download it again on every launch, and it caches your photos by file rather than by the expiring link they were served on, so they are not re-fetched every hour.
Storage is handled the same way. Photos upload straight to storage rather than through the app server, and the record is usable before the photo has finished. The location tree loads one level at a time, so a 400-room tower does not load itself onto your phone to answer a question about level three.
What it needs is a phone whose browser has had an update in the last few years: Safari on iOS, Chrome on Android, and the same screens on both. If the phone can open a web page and take a photo, it can run IssuesId.
The phone is the capture end of a longer record
What you log on the phone becomes the register the office works from, the list a trade opens from an emailed link without an app, and the report a client reads at handover. The guide to construction defect management software goes through that whole path with an example export. If your site calls the pre-handover walk snagging, the snagging software page walks it in those terms. And the features page lists what else the same record carries: inspections, work orders, RFIs, correspondence.