Feature
Works with no signal,
because your job sites never have any.
Wooded parkland, rural estates, a basement parking structure on a development site — none of them reliably have bars. LogLog was built assuming you have none, not as an afterthought bolted onto a cloud-first app.
The complaint everyone has about the last app
A crash mid-survey shouldn't cost you the survey
The most common complaint about field survey apps isn't a missing feature — it's the app itself dying partway through a job: a crash, a frozen map, a spinner that never resolves once the signal drops. LogLog's offline-first design means there's no live connection to lose in the first place. Every pin, every field, every photo writes to your device the instant you enter it, so a dropped signal, a closed tab, or the app restarting doesn't erase the tree you just recorded.
Your data lives in the browser, not the cloud
Under the hood, LogLog stores structured data in your browser's own local database — an IndexedDB store, if you're technical enough to care — with a second-layer backup in the browser's origin private file system as protection against the browser deciding to evict data under storage pressure. Neither requires an account or a server round-trip to write a record.
Photos and PDFs upload as a background queue once you're back in range, batched so a handful of small files don't get stuck behind one oversized one. If your device's storage genuinely fills up, LogLog tells you plainly instead of failing silently and quietly dropping the tree you just recorded.
Installable, no app store
LogLog is a progressive web app. Add it to your home screen on iPhone, Android, or desktop and it behaves like a native app — its own icon, its own window, no browser chrome. There's no app store review process to wait through and no separate download for each platform, because there's only one app.
Updates never interrupt a survey
New versions of LogLog install in the background but don't take over automatically — you'll see an "update available" banner when one's ready, and it's your call when to accept it. That means a background update never swaps out the app mid-tree, mid-pin, or mid-photo-upload. LogLog checks for updates roughly every 45 minutes when you have a connection.
Sync, honestly explained
When you're back online, LogLog syncs your project as a whole document, then resolves any conflict at the tree level: if you and a teammate both edited different trees while offline, both sets of changes merge cleanly. If you both edited the same tree, the last sync wins and silently overwrites the other — there's no conflict notification in the app yet. Realistically this only bites on the rare survey where two people cover the same tree at the same time; for the common case of splitting up a property between two or three people, per-tree merge works fine.
This is not real-time collaborative editing — no live cursors, no simultaneous typing in the same field. It's built for the actual shape of the work: one field day, maybe an occasional two-person overlap, not a team all editing the same project at once.
A small install, not a slow one
The PDF rendering engine is a couple megabytes on its own, so LogLog deliberately leaves it out of the initial install and fetches it lazily the first time you open a plan. That keeps the app itself fast to install and update for anyone who hasn't loaded a site plan yet, without slowing down the one time you actually need the PDF renderer.
Works on the phone you already have
No specialized data collector, no dedicated GPS hardware, no app-store account. Any modern phone, tablet, or laptop browser runs LogLog the same way — install it once to the home screen and every device on the team is running the identical, current version once it's synced its update.
A cloud-dependent app spins on a loading indicator the moment you lose signal; paper never had that problem, which is exactly why some arborists never left it. LogLog takes the same bet paper does — nothing about recording a tree depends on a connection — and adds the export and search a spreadsheet gives you on top.
Once you're back online, see how a finished survey turns into a deliverable on exports. Working with a crew? Read about team accounts.
A backup layer against the browser losing data
Browsers can, under storage pressure, evict data from IndexedDB without much warning. LogLog keeps a second-layer backup in the browser's own file system as a restore path if that ever happens — a deliberate safety net rather than trusting a single storage mechanism to never fail during a survey you can't easily repeat.
No signal? No problem.
Load a plan, drive somewhere with zero bars, and put it to the actual test.