Results Screen¶

Results Screen

The Results Screen displays the generated virtual try-on results and provides various interaction options for users to engage with the results, such as:

Allow users to interact with the results
Collect user feedback on the try-on quality
Enable users to continue with different photos
Store the generation history

Features¶

CartWishlistFeedbackContinueHistoryDisclaimer

Cart Integration¶

Cart Integration

Allows users to add products from the try-on results directly to their shopping cart.

Handling¶

You need to handle the addToCart action that the SDK will trigger when a user wants to add a product to their cart; SDK will close right after that, allowing you to present your own UI for product customization, such as size selection or other options needed for cart addition
The SDK will provide the product ID of the item the user wants to add

Customization

Customization¶

Text Elements ¶

addToCart - Label for the "Add to Cart" button

Wishlist Integration¶

Allows users to add products from the try-on results to their wishlist for later consideration.

Integration benefits

Seamless integration with your existing wishlist functionality
Consistent user experience across your app
Real-time wishlist status updates

Data Management¶

You need to implement a data provider that:

Provides the wishlistProductIds list of product IDs currently in the wishlist
Handles the setProductInWishlist callback to add or remove products from the wishlist

Data privacy

You don't need to provide the user's complete wishlist. You can filter to include only products related to the current try-on session, or provide the full wishlist - it's up to you. The SDK only uses this data to correctly display the wishlist status for products and doesn't collect or use this information for any other purpose.

Customization

Customization¶

Text Elements ¶

wishlistButtonAdd - Label for the "Add to Wishlist" button

Icons ¶

wishlist24 - Icon for the wishlist button in normal state
wishlistFill24 - Icon for the wishlist button when product is in wishlist

Survey with quick feedback optionsOther (custom user comment)

Feedback¶

Feedback

Enables users to provide feedback on the try-on results quality.

Customization

Customization¶

Text Elements ¶

feedbackTitle - Title displayed in the feedback section
feedbackOptions - List of feedback options available to users
feedbackButtonSkip - Label for the "Skip" button
feedbackButtonSend - Label for the "Send" button
feedbackGratitudeText - Text displayed after feedback is sent

Icons ¶

like36 - Icon for the "Like" feedback option
dislike36 - Icon for the "Dislike" feedback option
gratitude40 - Icon displayed after feedback is sent

Shapes ¶

feedbackButton - Shape for feedback buttons

Other Feedback¶

Feedback

Enables users to provide custom comment on the try-on results quality.

Customization

Customization¶

Text Elements ¶

feedbackOptionOther - Label for the "Other" feedback option in the survey
otherFeedbackTitle - Title for the "Other" feedback
otherFeedbackButtonSend - Label for the "Send" button
otherFeedbackButtonCancel - Label for the "Cancel" button

Continue with Other Photo¶

Continue with Other Photo

Allows users to start a new try-on with a different photo.

Customization

Customization¶

Icons ¶

changePhoto24 - Icon for the "Change Photo" action

Generation History¶

Provides access to previously generated try-on results.

Customization

Customization¶

Text Elements ¶

generationsHistoryPageTitle - Title displayed on the generations history page

Icons ¶

history24 - Icon for the History button in the page bar

Data Management¶

Built-inData Provider

By default, the SDK uses platforms' local storage to store the history. This is the simplest approach and requires no additional configuration.

Anonymous data

Neither the SDK nor the Aiuta API have any information about your users; all generated images are completely anonymous and are not linked to any user. Data in the history is stored locally on the device and may be lost when the app is reinstalled.

If you need to link images to a user profile, use Data Provider instead.

You can implement your own custom data provider that:

Provides the generated list of images previously generated for the user
React to the add(generated:for:) callback to store new generated images
React to the delete(generated:) callback to remove images by the user choice

This allows you to

Integrate with your existing user management system
Sync the generations history across devices
Implement custom business logic for history management
Control how generated images are stored and accessed

Fit Disclaimer¶

Fit Disclaimer

Displays important information about the virtual try-on fit.

Customization

Customization¶

Text Elements ¶

fitDisclaimerTitle - Title displayed in the fit disclaimer
fitDisclaimerDescription - Description text in the fit disclaimer
fitDisclaimerCloseButton - Label for the close button

Typography ¶

disclaimer - Text style for the disclaimer

Icons ¶

info20 - Icon displayed in the fit disclaimer

Analytics ¶

The following analytics events may be tracked during results interaction:

Type	Event	Page Id	Description
`page`		`results`	Results screen opened
`results`	`resultShared`	`results`	Try-on result was shared
`results`	`productAddToWishlist`	`results`	Product was added to wishlist
`results`	`productAddToCart`	`results`	Product was added to cart
`results`	`pickOtherPhoto`	`results`	User requested to try with different photo
`feedback`	`positive`	`results`	User provided positive feedback
`feedback`	`negative`	`results`	User provided negative feedback
`exit`		`results`	SDK was closed on the results screen

How to implement¶

Android
iOS
Flutter