Skip to content

Commit 542470b

Browse files
eandreeva-twreandreeva-twr
committed
Merge branch 'ADP-5877-NEW' into develop
2 parents e4a792e + 2238828 commit 542470b

17 files changed

Lines changed: 116 additions & 132 deletions

‎src/components/reusable/FallbackPaywallIntroduction.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
<!--- FallbackPaywallIntroduction--->
22

3-
To maintain a fluid user experience, it is important to set up [fallbacks](/fallback-paywalls) for your [paywalls](paywalls), flows, and [onboardings](onboardings). This precaution extends the application's capabilities in case of partial or complete loss of internet connection.
3+
To maintain a fluid user experience, it is important to set up [fallbacks](/fallback-paywalls) for your flows, [paywalls](paywalls), and [onboardings](onboardings). This precaution extends the application's capabilities in case of partial or complete loss of internet connection.
44

55
* **If the application cannot access Adapty servers:**
66

7-
It will be able to display a fallback paywall or flow, and access the local onboarding configuration.
7+
It will be able to display a fallback flow or paywall, and access the local onboarding configuration.
88

99
* **If the application cannot access the internet:**
1010

11-
It will be able to display a fallback paywall or flow. Onboardings include remote content and require an internet connection to function.
11+
It will be able to display a fallback flow or paywall. Onboardings include remote content and require an internet connection to function.
1212

1313
:::important
1414
Before you follow the steps in this guide, [download](/local-fallback-paywalls) the fallback configuration files from Adapty.

‎src/content/docs/ios/ios-handle-permissions.mdx‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
title: "Handle permission requests in flows (beta) - iOS"
33
description: "Implement AdaptySystemRequestsHandler to respond to system permission requests triggered from paywall and onboarding flows."
44
metadataTitle: "Handle Permission Requests in Flows (beta) - iOS | Adapty Docs"
5+
draft: true
56
---
67

78
If a flow includes buttons that request system permissions (push notifications, camera access, and others), the SDK calls your `AdaptySystemRequestsHandler`. You implement this handler to request the permission from the OS and return the result.

‎src/content/docs/ios/ios-handling-events.mdx‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: "Handle paywall & flow events - iOS"
3-
description: "Handle paywall and onboarding flow events in your iOS app."
2+
title: "Handle flow & paywall events - iOS"
3+
description: "Handle flow and paywall events in your iOS app."
44
metadataTitle: "Handle Flow Events - iOS | Adapty Docs"
55
toc_max_heading_level: 4
66
keywords: ['event', 'AdaptyFlowControllerDelegate', 'AdaptyPaywallControllerDelegate', 'flowController', 'didSelectProduct', 'didStartPurchase', 'didFinishPurchase', 'didFailPurchase', 'didFinishRestoreWith', 'didFailRestoreWith', 'didFailLoadingProductsWith', 'didFailRenderingWith', 'didFinishWebPaymentNavigation']
@@ -13,7 +13,7 @@ keywords: ['event', 'AdaptyFlowControllerDelegate', 'AdaptyPaywallControllerDele
1313
This guide covers event handling for purchases, restorations, product selection, and paywall rendering. You must also implement button handling (closing paywall, opening links, etc.). See our [guide on handling button actions](handle-paywall-actions) for details.
1414
:::
1515

16-
Paywalls and flows don't need extra code to make and restore purchases. However, they generate some events that your app can respond to. Those events include button presses (close buttons, URLs, product selections, and so on) as well as notifications on purchase-related actions. Learn how to respond to these events below.
16+
Flows and paywalls don't need extra code to make and restore purchases. However, they generate some events that your app can respond to. Those events include button presses (close buttons, URLs, product selections, and so on) as well as notifications on purchase-related actions. Learn how to respond to these events below.
1717

1818
:::tip
1919

@@ -23,7 +23,7 @@ Want to see a real-world example of how Adapty SDK is integrated into a mobile a
2323

2424
## Handling events in SwiftUI
2525

26-
To control or monitor processes occurring on the paywall or flow screen within your mobile app, use the `.flow` modifier in SwiftUI:
26+
To control or monitor processes occurring on the flow or paywall screen within your mobile app, use the `.flow` modifier in SwiftUI:
2727

2828
```swift showLineNumbers title="Swift"
2929
@State var flowPresented = false
@@ -64,16 +64,16 @@ You can register only the closure parameters you need and omit those you do not
6464

6565
| Parameter | Required | Description |
6666
|:-----------------------|:---------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
67-
| **isPresented** | required | A binding that manages whether the paywall or flow screen is displayed. |
68-
| **flowConfiguration** | required | An `AdaptyUI.FlowConfiguration` object containing visual details of the paywall or flow. Refer to [Get paywalls and flows](get-pb-paywalls) for more details. |
67+
| **isPresented** | required | A binding that manages whether the flow or paywall screen is displayed. |
68+
| **flowConfiguration** | required | An `AdaptyUI.FlowConfiguration` object containing visual details of the flow or paywall. Refer to [Get flows and paywalls](get-pb-paywalls) for more details. |
6969
| **didFailPurchase** | required | Invoked when `Adapty.makePurchase()` fails. |
7070
| **didFinishRestore** | required | Invoked when `Adapty.restorePurchases()` completes successfully. |
7171
| **didFailRestore** | required | Invoked when `Adapty.restorePurchases()` fails. |
7272
| **didFailRendering** | required | Invoked if an error occurs while rendering the interface. In this case, [contact Adapty Support](mailto:support@adapty.io). |
73-
| **placeholderBuilder** | optional | A function for rendering the placeholder view while the paywall or flow is loading. Defaults to a `ProgressView`. |
74-
| **fullScreen** | optional | Determines if the paywall or flow appears in full-screen mode or as a sheet. Defaults to `true`. |
75-
| **didAppear** | optional | Invoked when the paywall or flow view appears on screen. |
76-
| **didDisappear** | optional | Invoked when the paywall or flow view was dismissed. |
73+
| **placeholderBuilder** | optional | A function for rendering the placeholder view while the flow or paywall is loading. Defaults to a `ProgressView`. |
74+
| **fullScreen** | optional | Determines if the flow or paywall appears in full-screen mode or as a sheet. Defaults to `true`. |
75+
| **didAppear** | optional | Invoked when the flow or paywall view appears on screen. |
76+
| **didDisappear** | optional | Invoked when the flow or paywall view was dismissed. |
7777
| **didPerformAction** | optional | Invoked when a user clicks a button. Two action IDs are pre-defined: `close` and `openURL`; others are custom and can be set in the builder. |
7878
| **didSelectProduct** | optional | Invoked when a product is selected for purchase by the user or by the system. |
7979
| **didStartPurchase** | optional | Invoked when the user begins the purchase process. |
@@ -82,7 +82,7 @@ You can register only the closure parameters you need and omit those you do not
8282
| **didStartRestore** | optional | Invoked when the user starts the restore process. |
8383
| **didFailLoadingProducts** | optional | Invoked when errors occur during product loading. Return `true` to retry loading. |
8484
| **didPartiallyLoadProducts** | optional | Invoked when products are partially loaded. |
85-
| **showAlertItem** | optional | A binding that manages the display of alert items above the paywall or flow. |
85+
| **showAlertItem** | optional | A binding that manages the display of alert items above the flow or paywall. |
8686
| **showAlertBuilder** | optional | A function for rendering the alert view. |
8787

8888
## Handling events in UIKit
@@ -99,7 +99,7 @@ func flowControllerDidAppear(_ controller: AdaptyFlowController) { }
9999
func flowControllerDidDisappear(_ controller: AdaptyFlowController) { }
100100
```
101101

102-
These fire when the paywall or flow view is presented and dismissed.
102+
These fire when the flow or paywall view is presented and dismissed.
103103

104104
### User actions
105105

‎src/content/docs/ios/ios-handling-onboarding-events.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import 'react-medium-image-zoom/dist/styles.css';
1111
import Details from '@site/src/components/Details';
1212

1313
:::tip
14-
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get paywalls & flows](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
14+
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get flows & paywalls](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
1515
:::
1616

1717
Before you start, ensure that:

‎src/content/docs/ios/ios-onboarding-input.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import Details from '@site/src/components/Details';
88
import ZoomImage from '@site/src/components/ZoomImage';
99

1010
:::tip
11-
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get paywalls & flows](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
11+
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get flows & paywalls](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
1212
:::
1313

1414
When your users respond to a quiz question or input their data into an input field, the `onStateUpdatedAction` method will be invoked. You can save or process the field type in your code.

‎src/content/docs/ios/ios-onboardings.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ displayed_sidebar: sdkios
88
import CustomDocCardList from '@site/src/components/CustomDocCardList';
99

1010
:::tip
11-
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get paywalls & flows](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
11+
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get flows & paywalls](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
1212
:::
1313

1414
<CustomDocCardList />

‎src/content/docs/ios/ios-paywalls.mdx‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
2-
title: "Paywalls and flows - iOS"
3-
description: "Display and manage paywalls and flows built with the Adapty Paywall Builder or Flow Builder in your iOS app."
4-
metadataTitle: "Paywalls and Flows - iOS | Adapty Docs"
2+
title: "Flows and paywalls - iOS"
3+
description: "Display and manage flows and paywalls built with the Adapty Flow Builder or Paywall Builder in your iOS app."
4+
metadataTitle: "Flows and Paywalls - iOS | Adapty Docs"
55
---
66

77
import CustomDocCardList from '@site/src/components/CustomDocCardList';
88

99
## Display paywalls
1010

11-
### Adapty Paywall Builder & Flow Builder
11+
### Adapty Flow Builder & Paywall Builder
1212

1313
<CustomDocCardList ids={['get-pb-paywalls', 'ios-present-paywalls', 'ios-handling-events', 'handle-paywall-actions']} />
1414

‎src/content/docs/ios/ios-present-onboardings.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ import Tabs from '@theme/Tabs';
1212
import TabItem from '@theme/TabItem';
1313

1414
:::tip
15-
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get paywalls & flows](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
15+
**Starting from SDK v4 (beta)**, you can build [flows](get-pb-paywalls) as a more powerful alternative to onboardings. Unlike onboardings which run inside a WebView, flows render natively on the device — giving you smoother animations, a consistent iOS look and feel, faster load times, and no WebView runtime dependency. See [Get flows & paywalls](get-pb-paywalls) and [Display flows & paywalls](ios-present-paywalls) to get started.
1616
:::
1717

1818
If you've customized an onboarding using the builder, you don't need to worry about rendering it in your mobile app code to display it to the user. Such an onboarding contains both what should be shown within the onboarding and how it should be shown.
@@ -95,7 +95,6 @@ To do this, define a placeholder (what exactly will be shown while the onboardin
9595
<Tabs>
9696
<TabItem value="swift" label="UIKit">
9797
```swift showLineNumbers
98-
import Adapty
9998
import AdaptyUI
10099

101100
extension YourOnboardingManagerClass: AdaptyOnboardingControllerDelegate {
@@ -133,7 +132,6 @@ By default, links in onboardings open in an in-app browser. This provides a seam
133132
If you prefer to open links in an external browser instead, you can customize this behavior by setting the `externalUrlsPresentation` parameter to `.externalBrowser`:
134133

135134
```swift showLineNumbers
136-
import Adapty
137135
import AdaptyUI
138136

139137
let configuration = try AdaptyUI.getOnboardingConfiguration(

0 commit comments

Comments
 (0)