Collabora Office desktop and mobile apps

When users need Collabora Office desktop and mobile apps alongside Collabora Online

Offline editing is a separate decision from the server. Collabora Online runs in your infrastructure and only edits documents while the browser can reach it, so it does not cover staff who need to work on a plane, in a site with poor connectivity, or on a device that is not connected to your network. Before you size or deploy the server, list the groups who need offline work and the devices they use, because that list determines which client apps you evaluate.

The supplied product information describes several client options. *Collabora Office* brings the Collabora Online editing experience to Windows, macOS and Linux and runs locally on the device. *Collabora Office Classic* is the LibreOffice-based desktop suite that Collabora describes as its long-term supported desktop option, and Collabora states LTS support of 2 years as standard on its other products, with up to 5 years if required. Free apps exist for Android and iOS, and Collabora Office is listed for ChromeOS. Confirm with Collabora which app fits each group, which versions are supported on each platform, and whether the support term you need applies to the app you pick. Ask for the support terms in writing, since the lifecycle for each product may differ.

DeployOpen plans and implements the self-hosted Collabora Online side of this arrangement: server deployment, WOPI integration with your host platform, access policy and updates. The desktop and mobile apps are installed and managed on user devices through your endpoint tools, so your device management team should own rollout and app updates. Document the split of responsibilities early, and test that a file edited offline and then synced returns to the server with formatting intact, using the documents your staff actually use.

Which Collabora app fits which user group

Most staff edit documents in a browser through a WOPI host such as Nextcloud, and the Collabora Online server does the editing work. This group needs no local install, but every edit depends on a live connection to the server, so the server's plan and availability decide what they get. The Collabora Online pricing page gives the terms to compare.

Business plan: 3 euros per user per month for up to 99 users, according to the pricing page. It includes long-term support, a service level agreement, signed security updates and customer portal access.
Enterprise plan: quoted for 100 or more users with volume discounts. It adds integration support, customization services and roadmap input.
Free edition limits: CODE is free and suited to testing, home use or small teams. Collabora does not recommend it for production.
Connectivity dependence: browser editing stops when the connection to the server stops, so plan for outages and remote access.
User counting: confirm how Collabora counts users, including shared accounts, service accounts and users who only view documents.

Before you commit, confirm with Collabora which plan covers your user count and whether the support terms apply to your deployment.

How the desktop and mobile apps share a codebase with Collabora Online

Collabora Online, the Collabora Office desktop app and Collabora Office Classic all descend from LibreOffice technology, which is why they share document handling, editing logic and much of their behavior. Collabora Online is the browser-based suite integrated into platforms through the WOPI protocol. Collabora Office brings the Collabora Online experience to run locally on Windows, macOS and Linux, with free mobile apps for Android and iOS and availability on ChromeOS. Collabora Office Classic is the LibreOffice-based desktop suite that Collabora positions as its long-term supported desktop option. The product pages describe these as related products rather than publishing a feature matrix, so the exact overlap between them is something you need to establish yourself.

Shared code means that a document opened in the browser and the same document opened locally should generally be read and written by the same underlying engine, but it does not guarantee identical results. Differences can arise from the client version you run, the fonts installed on each device, the platform's own file handling, and features that are enabled in one product and not the other. Before rollout, open a representative set of your DOCX, XLSX, PPTX, ODF and PDF files in each client you plan to support, then save, reopen and compare layout, tracked changes, comments, formulas, charts and embedded objects. Record the client and server versions used for each test so that a later mismatch can be traced.

Sync behavior is the area most likely to surprise users. Confirm with Collabora how the desktop and mobile apps handle a document that is edited offline and also changed on the server, which copy wins, whether conflicts are flagged, and whether your integrating platform can see local edits at all. Also confirm which Collabora Office edition, and which support term, fits your fleet, since the product pages describe long-term support for Collabora Office Classic and standard support terms for other products. Treat offline editing as a separate policy decision from browser editing, and write down the test results and the versions they cover so the policy can be reviewed when either side is upgraded.

Configuration and policy options and when each fits

This table compares the ways you can let users edit documents, from browser-only editing in Collabora Online to desktop and mobile apps for named groups. Read each row against your offline needs, device policy and appetite for change, then confirm the open points with Collabora before you write the policy.

Option	Who it suits	What it changes for IT	What to confirm
Browser-only editing through Collabora Online	Most staff on managed endpoints who edit while connected to your network	One server estate to patch, size and monitor. Documents stay in your hosting platform and no local app is installed.	Which host platforms and file types your users need, and whether any workflow requires offline access
Collabora Office desktop app for named groups	Users who need to edit while offline or on a laptop away from the network	Adds a client to manage on Windows, macOS, ChromeOS or Linux. Access can be limited to named groups rather than the whole workforce.	How the desktop app is licensed and supported for your user count, and how it is delivered and updated on your endpoints
Collabora Office Classic for stability-focused users	Teams that prefer a long-term supported LibreOffice-based desktop suite and slower change	Creates a second product lifecycle to track alongside Collabora Online. Support windows differ from the online release cadence.	The exact support period and end-of-life dates for your version, and how Classic relates to the desktop app in your roadmap
Mobile apps allowed on managed devices	Users who review or make light edits on phones or tablets	Requires mobile device management rules for app installation, data sharing and app-level controls. Mobile apps are free, per the Collabora Office page for education.	Which mobile device management platform you use, and which app settings and data protections it can enforce
Mobile apps blocked by device policy	Organizations with strict data loss controls or classified content	Keeps document editing on browser or desktop, so the mobile attack surface stays out of scope. Users may need a separate path for phone access.	Whether blocked apps also cover personal devices that access your file platform, and how exceptions are approved
Desktop app and Collabora Online together	Mixed workforces with some offline needs and a central document platform	Two clients to test for file format fidelity and to keep on compatible versions. Documents still sync through the hosting platform.	How documents round-trip between desktop, mobile and online editing, and how version drift is tested
Free CODE edition for testing only	Pilots, home use or small test groups	Not recommended for production, so it cannot carry a policy decision for live staff. Rolling monthly releases differ from a supported branch.	Which production edition, support terms and update channel you need before any group relies on the tool

How to plan the rollout of desktop and mobile apps

This sequence turns the question of offline editing into a tested, supported rollout, so that each user group gets a suitable app, documents survive the trip between online and offline use, and support staff know who handles what.

Identify the user groups that need offline editing
Start by listing the teams whose work genuinely happens away from a reliable connection, such as field staff, travelling executives, or people in sites with unstable networks. Interview a sample from each group and record which documents they edit, which formats they use, and how often they work offline. Ask the business owner of each group to sign off the list. The step is done when every group has a named owner, a documented offline use case, and a short note on whether browser-only editing is enough for them. Groups that only edit in the browser today should stay on Collabora Online.
Match each group to an app and platform
For each approved group, choose the app that fits its devices and workflow. Collabora Office brings the Collabora Online experience to Windows, macOS and Linux, while Collabora Office Classic is the LibreOffice-based desktop suite with long-term support. Collabora describes free mobile apps for Android and iOS, and availability on ChromeOS. Confirm with Collabora which build, support tier and licensing terms apply to your organization, since the desktop and mobile apps do not share one support model. Record the chosen app and version for each group. The output is a simple matrix of group, platform, app and support tier.
Test document fidelity across formats on each platform
Build a test set drawn from real business documents, with copies of your most-used DOCX, XLSX and PPTX files, plus any ODF, PDF or legacy files that matter to your workflow. Open each file in the chosen app on each platform, then check layout, fonts, tables, charts, comments, tracked changes and embedded objects against the original. Record every deviation with a screenshot. The check is passed when a DOCX, XLSX and PPTX file can be opened offline, edited, saved, reopened online in Collabora Online, and reopened offline again without loss. Any failure goes back to the app or format decision in the previous step.
Run a pilot with a small group
Select a small pilot group from each approved user population, ideally including people who work offline and people who rely on the browser. Give them the app, a short guide, and a clear channel for reporting problems. Ask them to work through the offline and online cycle for their own documents over an agreed period, and to log sync conflicts, lost formatting, login issues and performance problems. Review the log with the pilot group and the IT team. The pilot is complete when the open issues are either fixed, documented as known limitations, or accepted by the business owner in writing.
Set device and update policy
Decide how apps are installed, configured and updated on managed devices. Define who can install the desktop app, which build and version are approved, how updates are tested and pushed, and how mobile apps are distributed through your mobile device management tool. Confirm how the apps connect to your Collabora Online server and whether the desktop and mobile apps need any network or certificate settings from your environment. Ask Collabora to confirm how security updates reach each app, since this determines how quickly you can respond to advisories. The output is a written policy that IT can apply without guessing.
Document support paths and hand over
Write a support document that tells users and help desk staff where to go for each kind of problem. Cover installation, sign-in, sync conflicts, lost formatting, offline document access, and suspected security issues. Name the internal first-line team, the escalation route to platform engineers for Collabora Online, and the route to Collabora for product issues under your support contract. Keep the document versioned with the approved app builds. The step is complete when the help desk has run through the document with a test ticket for each category and each escalation path has a named owner.

Security and update risks for offline editing

Offline editing moves document copies, application patches and package trust outside the server you control. The cards below cover the controls and questions that connect those local risks to the Collabora Online release line your users depend on.

Documents on unmanaged devices

A desktop or mobile copy of a document can outlive the sharing permission that allowed it. Ask whether your device management can encrypt local storage, block copies to personal cloud folders, and wipe application data when a laptop or phone is lost. Confirm whether the Collabora Office apps write temporary or autosave files to a location your endpoint tools can see and clear. Decide which document classifications may leave the server at all.

Patching cadence for installed apps

Each installed desktop or mobile app is a separate patch target that your team must track alongside the server. Ask Collabora which security fixes are delivered to the desktop and mobile apps, how quickly, and through which channel. Set a rule for minimum app versions, and confirm how your endpoint tools report installed versions so out-of-date clients can be found and restricted.

Signing keys and package verification

Before you install or update a package, verify that it is signed by the key you expect. Collabora has updated package signing keys for RPM and DEB users in the past, so your process must include a planned key rotation step. Record the fingerprints you trust, confirm how the publisher distributes new keys, and make sure your software deployment tool checks signatures rather than installing unsigned files.

Update channels versus the server release line

Desktop and mobile apps may not follow the same branch or cadence as your Collabora Online server, so their features and file handling can drift apart. Ask which release line each app tracks, whether it matches the server branch you run, and how long each branch receives point releases. Test documents in both places before you approve a mixed version state.

Support lifetime for desktop suites

Collabora Office Classic is described as a long-term supported LibreOffice-based desktop suite, and Collabora offers LTS support for 2 years as standard on its other products, with up to 5 years if required. Confirm the support period for the exact product and version you deploy, because a suite past its support window keeps receiving no fixes. Put that end date in your asset register and in your replacement plan.

Advisory tracking for every client

Security advisories cover the server and the client code paths that share technology, so a fix may apply to a desktop or mobile app even when your server is current. Subscribe to Collabora's advisories, map each one to the products and versions you run, and record which endpoints need action. Keep a short written process that says who approves an emergency client update and how fast devices must receive it.

Questions buyers ask about Collabora desktop and mobile apps

Do Collabora desktop apps need a separate server?

Not necessarily, but confirm it with Collabora before you size anything. Collabora describes Collabora Office for desktop as running locally on Windows, macOS and Linux, so offline editing does not follow the browser path through your WOPI host. Your Collabora Online servers still serve browser users in Nextcloud or another WOPI host, and those workloads keep their own sizing. Ask Collabora to confirm three things in writing: whether any desktop or mobile feature calls a server, which license unit applies to each installation, and how updates reach installed copies. The answers decide whether you need extra infrastructure, so they belong in the scope before purchase.

What drives the cost of rolling out Collabora desktop and mobile apps?

The main cost drivers are the number of people who need offline editing, the number of devices they use, your policy for installs and updates, how much testing your document set requires, and the support terms you choose. Collabora's pricing page lists the Business plan at 3 euros per user per month for up to 99 users, including long term support, a service level agreement, signed security updates and customer portal access. Enterprise pricing for 100 or more users is quoted with volume discounts and adds integration support, customization services and roadmap input. Ask the vendor whether the license unit is a user or a device, because that changes the total.

At what user count does Enterprise pricing apply?

According to Collabora's pricing page, the Business plan covers up to 99 users, and organizations with 100 or more users receive a quote with volume discounts. The Enterprise plan adds integration support, customization services and roadmap input, so the threshold matters less than whether you need those services. Before you compare plans, confirm how desktop and mobile installations count toward the user total, whether offline users are included in the same count as browser users, and which support terms apply to each plan. Ask for the quote in writing with the counting rules stated.

How long does a Collabora desktop pilot take to scope?

The scoping time depends on the device groups, operating system mix, the number of document types in use and whether the pilot includes Android and iOS. No fixed duration applies to every organization, so ask for a written pilot plan instead of a single estimate. The plan should name the device groups and their sizes, the test document sample, the success criteria for formatting fidelity and the people who sign off. A useful pilot also states how long each phase runs and what triggers a go or no-go decision. If a quote gives only an overall duration, ask which phases it covers.

What does our IT team need to provide for the rollout?

Your IT team usually provides an inventory of operating system versions and device owners, the endpoint management tool that will deploy the software, and the identity and group structure that controls who gets which app. It also needs to approve the network rules that let installed copies reach update sources, set a change window for pilot and production waves, and name an owner for support tickets. Finally, it should supply a sample of real business documents with known formatting problems so the team can test fidelity. Agree these inputs in the scope, because missing inventory and approvals are common reasons for delay.

Which desktop edition should we choose for long-term support?

Collabora Office Classic is the long-term supported LibreOffice-based desktop suite, while Collabora Office for desktop brings the Collabora Online experience to local machines. Collabora offers LTS support for 2 years as standard on its other products, with up to 5 years if required, according to the Collabora Office page. Those figures describe Collabora's other products, so confirm the exact LTS period, end-of-support date and security update terms for the desktop edition you plan to deploy. Get the answer in writing and check it against your own lifecycle policy before you standardize on one edition.

Can our own team run the desktop and mobile rollout?

Your team can run it if it has endpoint packaging and deployment skills, a test plan for your document set, and capacity to handle user support. Collabora's free CODE edition is described as suited to testing and small teams, but it is not recommended for production, so it is useful for trials only. For production, the Business plan includes long term support, signed security updates and customer portal access. DeployOpen can plan, implement, test, document and support the rollout under a fixed scope agreed in writing, and offers ongoing support and upgrades as retainers.

What DeployOpen plans and implements for desktop and mobile access

DeployOpen can agree the desktop and mobile work in writing as a fixed-scope engagement, starting with requirements that decide which apps each user group needs. In practice that means recording which users need offline editing, which operating systems they use, whether personal devices are allowed, and which document formats must open without loss. The output is a written scope that names each app, each group, the server-side Collabora Online version it will be paired with, and the acceptance criteria for each deliverable. Scope, deliverables and timelines are confirmed before any work starts, so the quote follows directly from the requirements.

The core technical work is alignment between the desktop or mobile apps and the server you run. DeployOpen can review the Collabora Online deployment that serves browser editing, confirm that the desktop and mobile versions are matched to it, and plan the fidelity test plan that compares how representative DOCX, XLSX and PPTX files open, edit and save across both. Deliverables typically include the test matrix, the results, a rollout guide for administrators and end users, and documentation of the decisions taken. Confirm with Collabora which app versions and licensing terms apply to your user count before the scope is finalized, since the Collabora Office page describes the products but does not replace a licensing review.

DeployOpen prepares systems, documentation and test evidence for your own compliance assessments, but it does not issue audit reports, attestations or certifications. Independent auditors and certification bodies perform those assessments. Ongoing work such as app version tracking, re-running the fidelity tests after server updates and handling new user groups is available as a retainer after the initial rollout. Ask any provider, including DeployOpen, to state in the written scope which of these items are one-time and which recur, and who owns the test results afterward.

Decisions to make before rollout

Adding offline apps changes where documents live, who maintains the software and who answers when something breaks. The decisions below connect the browser editing set up in Collabora Online with the desktop and mobile apps, so each one should be settled before users receive installers.

Which groups get offline apps

Offline editing suits field staff, travelers and users with unreliable connections, but every installed copy is a document store outside the browser session. Start by mapping which roles need offline work and which can stay browser-only. Confirm with your Nextcloud or other WOPI host administrators how offline files will sync back and which groups can open them.

Collabora Office or Classic

Collabora Office brings the Collabora Online experience to Windows, macOS and Linux, while Collabora Office Classic is the LibreOffice-based desktop suite with long-term support. Choose based on whether users need the online feature set locally or a stable, long-lived desktop suite. Ask Collabora which support term applies to each product and how upgrades between them are handled.

Mobile app policy

Free Android and iOS apps are easy to install, which makes them the hardest channel to control. Decide whether personal devices may install them, whether mobile device management will restrict them, and whether documents may be opened in third-party apps. Document the answer in your acceptable use policy before the mobile rollout begins.

Where local files may be stored

Local copies can end up in personal cloud folders, USB drives or unencrypted laptop storage, which weakens any sharing restriction set in the host platform. Set rules for approved locations, disk encryption requirements and whether downloads are permitted at all for sensitive classifications. Verify which restrictions your host platform can enforce on files after they leave the server.

Who owns app updates

Desktop and mobile apps ship on their own release cadence, separate from the server packages you run. Decide whether IT pushes updates through endpoint tooling, whether users update themselves, and who tracks Collabora security advisories for the installed clients. Mismatched versions between server and apps can cause editing differences, so agree on a supported version pairing.

How support tickets route

A problem may come from the host platform, the Collabora Online server, the desktop app or the device. Define one first-line queue, a named owner for the server and a path to Collabora for product defects. Write down what logs and version details each team needs so tickets are not bounced back to the user.

How DeployOpen scopes and delivers Collabora Online alongside desktop and mobile apps

DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For Collabora Office desktop and mobile apps alongside Collabora Online, we start by agreeing in writing which devices, users and offline editing needs are in scope, then build and hand over only that agreed work.

How we scope

Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
The written scope lists which desktop platforms, mobile platforms and user groups receive the apps alongside the Collabora Online server.
We ask you to confirm which documents need offline editing and which must stay server-side only.

How we build

We install and configure the Collabora Online server in your environment first, so the apps are tested against the editing service they will share.
We test document fidelity for Microsoft and OpenDocument files opened and saved from each desktop and mobile app.
We document the deployment, app distribution steps and known differences between browser and local editing for your team.

How we hand over

You receive the agreed deliverables, configuration records and written procedures for installing and updating each app.
We walk your administrators through the tested steps, so your team can repeat them without our involvement.
We document open items, such as platform versions or features you still need to confirm with Collabora, so nothing is left implied.

How we support

Ongoing support, upgrades and continuous testing are available as retainers after handover.
A retainer can cover re-testing of document fidelity when Collabora releases new app or server versions.
Support scope and response arrangements are set in the written agreement, so you know what is covered before you need it.

Collabora Office desktop and mobile apps alongside Collabora Online