> 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/learn-more/dynamic-vs-static-framework.md).

# Dynamic vs. static framework on iOS

Discover the benefits of using Apryse dynamic framework for your apps, including easier integration, faster compile times, and smaller App Store updates. Learn more about static vs dynamic frameworks

Apryse includes both dynamic and static versions of the framework. For most apps we recommend using the dynamic version of the framework for the following reasons:

* It is simpler to integrate
* It decreases compile times
* It allows for smaller App Store delta updates

The main reason to consider using the static framework is if your app is particularily sensitive to the initial download size. Because static linking will remove portions of the framework the app does not use, it will result in a smaller final .ipa. For more information, please see the [Framework size](/ios/learn-more/framework-size.md) guide.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/ios/learn-more/dynamic-vs-static-framework.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.