> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/ios/guides/cordova.md).

# Ionic/Cordova PDF viewer and annotation plugin

Explore the Apryse native SDK for integrating a powerful document viewer and PDF editor into your Ionic/Cordova app. Learn more about this cross-platform solution now! The Apryse iOS SDK streamlines s

## This project is no longer in development. If you are looking for cross-platform solution, check out [React Native](https://github.com/ApryseSDK/pdftron-react-native/) or [Flutter](https://github.com/ApryseSDK/pdftron-flutter/). If you are looking to add to your current Cordova/Ionic project, check out the [WebViewer sample](https://github.com/ApryseSDK/webviewer-cordova-sample/).

This section is in reference to the Ionic/Cordova native plugin. For an overview of the options for PDF and Office viewing in an Ionic/Cordova app, please see [Viewing a PDF in Ionic/Cordova with Apryse](/ios/guides/cordova/pdftron-ionic-cordova-options.md).

Ionic/Cordova allows you to build native apps on iOS and Android from a single codebase. This tutorial will help you integrate the Apryse native SDK into your Ionic/Cordova app.

Currently the Apryse Ionic/Cordova wrapper exposes [PdfViewCtrlTabHostFragment](https://sdk.apryse.com/api/android/javadoc/reference/com/pdftron/pdf/controls/PdfViewCtrlTabHostFragment.html) on Android and [PTDocumentViewController](/ios/basic-operations/open/doc-view.md) on iOS. The viewer is an all-in-one document reader and PDF editor that can be further customized by Javascript API as well as modifying native components.

<a href="https://github.com/ApryseSDK/pdftron-cordova/" class="button primary">Get the Cordova/Ionic source code</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/ios/guides/cordova.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.