What's New in the Mobile App — Q3 Update

Hey everyone — Eli here. Figured it's been a busy quarter on mobile, so let's step back and look at what actually shipped. This isn't the flashy marketing version; this is the stuff your technicians are already using (or about to discover).

Offline Mode: Finally Automatic

Okay so this one tripped me up too when I first looked at it. Previous versions made technicians manually toggle offline mode, which... nobody did. Now it kicks in automatically when the app detects a weak or missing connection. The trigger logic looks at ping latency and packet loss, not just "is WiFi connected."

There's a whole deep-dive on this in our offline launch post if you want the architecture details.

Photo Tools Got Actually Useful

We added annotation — circles, arrows, text overlays — directly in the capture flow. No more "take photo, open markup app, save, re-upload." It's all in one pipeline now:

capture → annotate → compress → queue for upload

Compression happens client-side now too, which helps on those rural job sites where you're hanging on by a single bar of signal. Related: if you're seeing upload stalls, there's a workaround for slow connections documented here.

Dashboard Refresh

The tech-facing dashboard got a visual overhaul. More importantly, it now caches the last known state for 24 hours, so opening the app doesn't feel like a cold start every single time. Yeah, this was a cache invalidation problem. The joke writes itself.

Performance: The Boring Stuff That Matters

• Work order list load time: down ~40% on average
• Memory footprint reduced on older Android devices (API 28+ still supported, but less painful now)
• Sync conflicts down significantly — we fixed a race condition where rapid status changes could create duplicate records

One Gotcha to Know About

If you're still on mobile app version 3.1.x or earlier, the new dashboard won't render correctly. It won't crash — you'll just get a fallback list view. The fix is... update the app. We know, we know. But forcing updates mid-day is its own mess, so we went with graceful degradation instead.

What's Cooking for Q4

Can't say much yet, but: better barcode scanning (the current library struggles with damaged labels), and some experiments with predictive sync — fetching likely-needed data before the technician asks for it. Early results are promising but also early.

Questions? Hit the comments. If something's acting weird, the sync troubleshooting guide is still your best first stop.

— Eli