Definition. Offline mobile preview renders a document in the application running on the user's device. OfficeAPI lists Android and iOS among its supported operating systems and provides document preview and conversion without a hosted processing dependency.
What should the mobile integration decide?
Android and iOS are 2 mobile targets with different application packaging and lifecycle rules. The overview also names HarmonyOS; support for an operating system should not be interpreted as a specific ready-made viewer component or a published UI framework SDK.
| Application decision | What to verify |
|---|---|
| Native integration | Package compatibility with the actual mobile application target |
| File access | The app can open the selected document under platform access rules |
| Viewing surface | The rendered result remains readable in the app's screen layout |
| Application lifecycle | Leaving and returning to the app does not confuse the viewing state |
OfficeAPI documents 2 invocation paths generally. Choose the path actually available and appropriate to the mobile integration package; do not assume that arbitrary process launching works equally on every mobile platform.
Which files should you test?
The preview source contains 3 office families: Word, Excel and PowerPoint. Inventory the formats used by your app and consult each family's exact extension list. For example, spreadsheet preview includes coverage that differs from spreadsheet conversion.
Evaluate documents with dense text, wide spreadsheets and presentation slides in the smallest supported screen layout. Viewing support does not establish editing, annotation or a particular zoom/navigation control; those requirements need their own interface design and integration check.
How do you validate the mobile workflow?
- Confirm the source extensions in the preview list and the OS in the environment list.
- Integrate the native engine using the actual supplied package for the target application.
- Open representative local documents and test file-access failures as well as successful viewing.
- Test orientation changes, leaving and returning to the app, and replacing the current source with another file.
- Repeat the viewing path with network access disabled and verify the behavior of the application as a whole.
These are application-level acceptance checks, not claims that OfficeAPI implements the mobile lifecycle or document picker for you.
How does this fit an on-device AI feature?
A local viewing step lets the user inspect a document before or after another application action. If a local model needs a different file format, check the conversion outputs accepted by that model and application. The on-device AI guide describes how to keep those responsibilities separate.
Frequently asked questions
Does the document have to leave the device?
OfficeAPI processing is offline. Whether the application synchronizes or uploads files is a separate choice.
Is there a documented mobile editor?
The product sources establish conversion and preview, not an editing interface.
Do desktop integration instructions apply unchanged?
No. Validate mobile packaging, file access and lifecycle against the actual target even when the engine is shared.