Usage in SwiftUI

1 define test users appstorys allows you to capture screens and elements of your app using the "test user" functionality 2\ adding test users you can add test users directly from your appstorys dashboard you need to define a "name" and "userid" for this test user the userid must match the one set in your app for that user 2 a how it works once added the test users will see a “capture screen” (mentioned in point 3) button on their devices within the app to help appstorys identify and track specific ui elements within your swiftui screens, you can assign a custom identifier to each element use the capturetag() modifier to tag components you want appstorys to recognize and measure interactions with captureappstorystag(“your element name”) tapping this button will send the complete screen data — including layout elements, text, buttons, and structural hierarchy — to the appstorys dashboard the screens and elements then become available within your dashboard for campaign targeting and configuration like tooltips, spotlight, coachmarks and more a widgets appstorys widgets() explanation for position if you want to create multiple widgets in a single screen, you can use the position attribute (as defined in track screens) to define the multiple positions which you can then select as a dropdown from the dashboard while creating new widget campaigns appstorys widgets(position "second widget") captureappstoryswidgettag("second widget") only widgets and stories are to be called separetely b to call banner floater csat pip videos modals bottom sheets tooltips, spotlight, coachmarks you only need to call this single line of code on root or every screen withappstorysoverlays() c reels appstorys reels() d stories appstorys stories() f tooltips & spotlight & coachmarks you can create a tootltip, spotlight or coachmark campaign by selecting the "tooltip" option from the dashboard you need to make multiple steps for a tootlip campaign and only one step for a spotlight campaign to ensure tooltips, spotlights & coachmarks display correctly, appstorys automatically renders them over your existing app ui to enable this, you must call the integration code at the top of your app stack , above all other views and components this ensures that campaigns like tooltips, spotlights & coachmarks appear seamlessly and consistently across all screens, without being obstructed by other ui elements