SolarSoftwares
Book a demo

What Is Mobile App Offline Mode?

How we keep reviews fair

Quick answer

Mobile app offline mode (also called offline-first) lets a solar crew survey, install or inspect with no signal. It saves forms, photos and signatures on the phone, queues them, and sends them when a connection returns. It has 4 parts: capture, queue, sync and conflict handling.

Ready to see how it works?

Tell the SolarSoftwares team which tool you are considering. We reply by email to book your demo.

Book a demo
Jump to a section

Key takeaways

  • Of six field apps, five have company pages that document offline use. Only meteocontrol VCOM describes conflict behaviour, and it warns of data loss.
  • Photos dominate the queue. In the invented example (6 jobs, 40 photos each at 3.5 MB), photos are 99.96% of the 840.36 MB. It takes about 140 minutes to clear at 1 Mbit/s.
  • The merge rule decides what survives. In the example record of 6 edits, a whole-record rule overwrote 3, a field-by-field rule overwrote 2, and holding overlaps overwrote 0.
  • Test with airplane mode on, and edit the same job on two devices, before you buy.

Four of the six tools below are field-service or O&M apps, so see the best solar field service management software. For survey apps, see the best solar site survey apps.

Offline mode at a glance

Offline mode is a storage and sync design, not one feature. It has a capture side, a queue and a merge rule.

ItemDetail
PartsLocal capture on the phone, a queue of pending changes, a sync step, and a rule for clashing edits.
Unit and rangeQueue size in MB and time in minutes. Photos set most of it. The example 6-job example: 840.36 MB.
Where it mattersSurveys, installs, inspections and O&M visits where signal is weak or absent.
Standard or ruleNo standard. Each company sets its own limits and merge rule.
In softwareField service, survey, inspection and O&M apps. See the table below.

Why does offline mode matter for installers?

A crew that loses signal on a roof, in a meter room or on a plant needs the app to keep taking records. If it stops, the crew writes on paper and types it up later.

Those records flow into other documents. Survey data goes into design (see site survey). Test readings and photos go into the commissioning record and the handover pack. Photo practice has its own page: site photo documentation.

Two bar charts of invented inputs: queue upload time by photo count, photo size and link speed, and edits overwritten by merge rule

Figure 1. In the examples, photo size and link speed set the queue time, and the merge rule sets how many edits are overwritten.

What works offline, and what does not?

Recording work on the device works offline on the company pages we read. Anything that needs the server or another person does not.

TaskWhat the pages read say
Forms and checklistsCoperniq: previously opened forms stay accessible (number, text, date, dropdown). ServiceTitan lists forms and checklists. VCOM saves form input on the device.
Photos and filesServiceTitan lists photos and media. Coperniq says photos and files can be attached to forms. CompanyCam queues captures for upload.
SignaturesServiceTitan: on-device signatures work. Sending an e-signature request link needs a connection.
Time trackingCoperniq and ServiceTitan list it as working offline. CompanyCam lists time entries too.
Needs a connectionCoperniq: sending forms for review, new tasks, records never opened online. ServiceTitan: current upgrade pricing, card swipe and Tap to Pay, purchase orders. CompanyCam: checklist fields not opened before going offline.

Raptor Maps works differently. Its download page calls Raptor Solar an "offline-first mobile experience" and says you download a site before you go, one circuit block at a time.

How does offline sync work?

The app saves changes on the phone and sends them when a connection returns. Companies differ on timing, retries and how long cached data lasts.

  • Automatic upload. Coperniq says offline work syncs automatically once you reconnect. ServiceTitan says no manual action is required to sync.
  • Retries. Coperniq’s help page (no absolute date) says it retries a failed item up to three times, then shows it on a sync status screen. CompanyCam’s upload troubleshooting page (5 August 2026) describes manual Retry buttons. Its offline article says captures upload on their own once you are back online.
  • Freshness window. The same Coperniq page says it keeps task data available offline for up to 24 hours after it was last loaded.
  • Timer or manual sync. VCOM’s page gives a default automatic sync interval of 15 minutes. It cannot sync while offline.

How are sync conflicts handled?

A conflict happens when the phone and the office both change the same record before the phone syncs. The tool’s merge rule then decides which edit survives.

Among the company pages listed, only meteocontrol VCOM describes this. It says a form cannot be locked when you open it offline, so others will not know. It recommends opening forms while you are still online. Separately, it warns that opening a form locked by another technician can lead to data loss, and describes a case where one assignee’s input is overwritten. The Coperniq, ServiceTitan and Raptor Maps pages listed do not describe conflict handling.

The table shows one example record with 6 edits: 3 on the phone offline, 3 in the office. The phone syncs at 14:05. Fields edited on both sides are roof pitch and notes. Policies are a model, not any company’s.

Each row shows which value survives under one merge rule.

Merge ruleRoof pitchNotesMain breaker / customer phoneEdits overwritten
Whole record, phone syncs lastPhone’sPhone’sPhone’s / Old value3 (all office edits)
Whole record, office saves lastOffice’sOffice’sOld value / Office’s3 (all phone edits)
Field by field, latest edit time winsPhone’s (10:10 beats 09:40)Office’s (13:00 beats 11:00)Phone’s / Office’s2
Same, phone clock 90 minutes slowOffice’s, the wrong winnerOffice’sPhone’s / Office’s2
Field by field, overlaps held for reviewHeldHeldPhone’s / Office’s0 (2 held)

Whole-record rules lose the most work. Field-level rules lose only the overlap. A wrong device clock can pick the wrong winner. Holding overlaps loses nothing, but a person has to decide.

Worked example: a day of photos with no signal

A crew finishes 6 jobs in a dead zone. All inputs are example. Each job has 40 photos at 3.5 MB, plus 20 KB of form data, 30 KB of signature and 10 KB of measurements. Back online, the app gets 80% of a 1 Mbit/s link. Each row below changes one setting.

Setting (example)QueueTime to clearClears in 60 min?
Base: 40 photos at 3.5 MB, 1 Mbit/s840.36 MB140.06 minNo (480.36 MB left)
20 photos a job420.36 MB70.06 minNo (60.36 MB left)
1.2 MB photos288.36 MB48.06 minYes
10 Mbit/s link840.36 MB14.01 minYes

The method: queue MB is jobs times (photos times photo MB, plus form, signature and measurement KB divided by 1,000). Time is MB times 8, divided by usable Mbit/s. Forms, signatures and measurements add 0.36 MB, so photos are 99.96% of the base queue.

Real phones may cut photo size, retry failures or throttle background uploads. Treat these figures as a size check, not a forecast.

Check your own queue and conflicts

Enter your jobs, photo count, photo size and link speed. Part 2 counts overwritten edits for three merge rules. It loads the example first. If the calculator does not load, open the offline sync calculator on its own page.

Open the calculator on its own page

What should you test before buying?

Run six tests on a real phone, with a real job template. Do them during a trial, before you sign.

  1. Turn on airplane mode, then fill a form, take photos, add a signature and type measurements.
  2. Force-close the app while offline, reopen it, and check the data is still there.
  3. Open a job you never opened online. The Coperniq page says forms never opened online are unavailable offline.
  4. Edit the same field in the office and on the phone, then sync. Record which edit survives, as in the conflict table.
  5. Set the phone clock wrong by an hour and repeat test 4.
  6. Queue a full day of photos, then time the upload. Check retries, failed-item screens and what happens if you delete the app with items unsynced.

Ask the company for the cache window, the merge rule and the photo size setting in writing. For alarm-driven visits, see CMMS and work orders.

How solar software handles offline mode

Five of the six tools document offline use, and only VCOM states a conflict rule. Pages listed October 2026.

SoftwareOffline documented?Conflict rule stated?Page and date
meteocontrol VCOMYesYesVCOM help, work orders in the O&M app, last updated 22 October 2026 on the page.
CoperniqYesNot statedCoperniq support, offline mode for forms and time tracking, no absolute date shown on the page.
ServiceTitanYesNot statedServiceTitan help, field mobile app offline capabilities, published and updated 29 October 2026 on the page.
Raptor MapsYesNot statedRaptor Maps knowledge hub, two pages, no date shown (copyright 2025).
ScaniflyNot statedNot statedScanifly help, two pages, no date shown (copyright 2026).
CompanyCamYesNot statedCompanyCam help, offline mode article, 9 September 2026 on the page. Upload page 5 August 2026.

What each page says:

  • meteocontrol VCOM: O&M app: "All your input is auto-saved on your local device while working in the form." Sync is not possible offline. Default automatic interval 15 min. It warns that opening a form locked by another technician can lead to data loss, and describes one assignee’s input being overwritten.
  • Coperniq: Forms and time tracking work offline. Sending forms for review and creating tasks need a connection. Task data stays for up to 24 hours.
  • ServiceTitan: Notes, signatures, photos, time tracking and findings work offline. Some items need a connection.
  • Raptor Maps: The Raptor Solar app "works in offline mode, simply download your site for offline use". One circuit block at a time.
  • Scanifly: The mobile app and checklist pages describe capture and upload in the field. They do not mention offline use.
  • CompanyCam: "Everything you capture sits in a queue and uploads on its own once you’re back online." You can only complete checklist fields you opened before going offline. The article does not describe conflicts.

Not stated: the company page we cite does not say. That does not show the app lacks the feature. To compare apps, see the best solar site survey apps.

Common mistakes with offline mode

FAQs

Do solar field apps work without signal?

Some do. Of the six apps listed, five have company pages that document offline use. The pages differ on what works and how long data stays. Test your own job template in airplane mode.

What happens to photos taken offline?

They are saved on the phone and queued. Coperniq’s undated page says items sync once you reconnect and retries a failed item up to three times. CompanyCam’s offline article says captures sit in a queue and upload on their own once you are back online.

How much data does a day of site photos use?

Photo count and size decide it. The example of 6 jobs at 40 photos each at 3.5 MB is 840.36 MB. Use the calculator with your own phone’s photo size.

What if two people edit the same job?

One edit can overwrite the other, depending on the tool’s merge rule. VCOM warns that opening a form locked by another technician can lead to data loss. Ask the company, then test it with two devices.

  • Site survey: collecting roof, electrical and site data before design.
  • Work order: the job record a field crew completes and closes.
  • Photo documentation: the site photos that prove work done.
  • CMMS: software that tracks maintenance work and history.

Next step: run the six tests above in a trial, and use the best solar site survey apps list to pick which apps to trial.

Sources

Last updated 30 October 2026. Next scheduled review: 30 January 2027.

See the software on your shortlist.

Tell the SolarSoftwares team what you want in your solar software.

Your request goes by email to the SolarSoftwares team. A demo time is set only after we reply.