Show an interactive weight goal chart in a paywall
Follow this recipe to display the projected weight of each user as a chart in a paywall flow. The user enters their current and goal weight in an onboarding flow. Your app collects both values. The chart shows the weekly progress that the user can expect with your app, from one value to the other. Your app renders the chart as a native Swift Charts view in a custom element.
This recipe only covers iOS apps. Apps built with other frameworks only display the custom elements’ fallback content. Support for Android and cross-platform frameworks is upcoming.
Before you start
- Update your app to Adapty iOS SDK 4.4 or later. Earlier SDK versions show the fallback content for every custom element.
- Set up your app to fetch and display flows.
- Create two separate flows — one for the onboarding, and one for the paywall. Add each to a placement. The code in this recipe fetches the paywall flow from the placement with the ID
weight_paywall.
1. Ask for the current and goal weight in the onboarding flow
In the Flow & Paywall Builder, add two Number inputs to the onboarding flow:
- One for the current weight in kilograms, with the Element ID
weight. - One for the goal weight in kilograms, with the Element ID
goal_weight.
To make your app read the weights the same way in every locale, select Integer from the Format dropdown of both inputs. An input sends its value to your app as text, exactly as the user types it. The code in this recipe reads “70.5” and “70,5” differently. Whole numbers have no decimal separator.
To make sure that your app receives both values, end the onboarding flow with a screen that has no inputs. On that screen, add a button with the Close flow action. Inputs send their values when they lose focus or when the user moves to another screen.
2. Add the custom element to the paywall screen
In the paywall flow, add a custom element to a screen, and set it up for the chart:
- Type:
line_chart. - ID:
weight_goal. - Height: Keep the default Fixed height. The chart fills the custom element.
Keep the custom element out of containers that respond to touch, such as a carousel. Otherwise, a drag along the chart also moves the carousel.
Inside the custom element, add an Image with a sample weight chart. Users see it as the fallback when their version of your app doesn’t display the chart.
3. Save the current and goal weight in your app
Collect the current and goal weight from the flow_user_input events of the onboarding flow, as in Process data from flows. To know that the user reached the last screen, watch for a flow_screen_showed event with is_last_screen set to true. When the onboarding flow closes after that screen, pass both weights to showWeightPaywall, the method that opens the paywall flow with the chart.
The following code is for UIKit. One view controller is the delegate of both flows. It must also implement the purchase and restore methods of the AdaptyFlowControllerDelegate protocol. This example leaves them out. To see them, go to Present flows and paywalls in UIKit.
In SwiftUI, use the didReceiveAnalyticEvent and didDisappear closures of the .flow modifier instead of the delegate methods. Present the paywall flow with a second .flow modifier.
4. Create the chart view
Create a model of a weight plan, and a SwiftUI view with the chart. The plan has one entry per week, from the current weight to the goal weight. When the user drags along the chart, the view marks the week at the touch point, and displays the projected weight for that week:
The plan assumes that the weight changes by 0.5 kg per week. To use another rate, edit weeklyChange.
The drag along the chart needs iOS 17 or later. On iOS 16, users see the line, but can’t drag along it.
5. Match the chart to the custom element
Write a resolver that returns the chart view for the line_chart Type and the weight_goal ID. Store the weight plan in a property of the resolver:
Attach the resolver to the paywall flow when you fetch its configuration. Create the resolver with the weight plan from the current and goal weight:
If your app sets an app-wide resolver, this resolver replaces it in the paywall flow. WeightChartResolver returns nil for any other Type and ID, because the paywall flow in this recipe has no other custom elements. If your paywall flow has other custom elements, pass the app-wide resolver to this one. Then call the app-wide resolver for their Types and IDs, as in Attach a resolver to one flow.
6. Test on a device
The Flow & Paywall Builder can’t run your app code, so its canvas only shows the fallback. To preview the chart:
- Publish both flows. To see the latest published versions instead of cached ones, register the device as a test device.
- Run a build of your app that includes the resolver, on iOS 17 or later. Complete the onboarding flow with a current and a goal weight. Verify that the line of the chart starts at the current weight and ends at the goal weight.
- Drag along the chart, and verify that the projected weight for the week under your finger appears above the line.
To test the fallback, remove the customElementsResolver argument from the getFlowConfiguration call, and open the paywall flow again.
To find out why the fallback appears instead of the chart, follow the instructions in the Test on a device section of the iOS guide.