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

# Integration (Native Features)

Natively allows you to set up many features. Pick up most suitable for your business.

## Available Native Features

1. Push Notifications with OneSignal.
2. Fetching device info
3. Geolocation (Foreground/Background live location tracking)
4. Store data in local storage
5. Biometrics authorization and storing user's credentials
6. Send SMS/Email through native screens
7. Native Date Picker
8. Native Camera (Take a photo or record a video)
9. QR/Barcode scanner
10. Native contacts (fetch all contacts or create new)
11. In-App Purchases (RevenueCat)
12. Native toast and banner
13. Share sheet for photos, files, text and URLs
14. Open external URL inside of the app (In-App browser)
15. Open external installed apps
16. Request user's review
17. vCARD(.vcf) files handling
18. HTML5 fullscreen video
19. tel:,sms:,mailto: handling
20. File download (through Native share sheet)
21. AppsFlyer Analytics
22. Facebook Analytics
23. Apple's HealthKit Integration
24. Social (Google, Facebook, Telegram) auth support (through the web)
25. Custom launch screen
26. Pull to refresh
27. Swipe navigation
28. Custom app icons
29. Status bar customization
30. Audio recording
31. Debugger console
32. Admob integration
33. NFC Read/Write
34. Apple Sign In
35. [And more coming soon](https://ideas.buildnatively.com)


---

# 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.buildnatively.com/guides/integration.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.