Begin with the selected character, not the gallery
A visual catalogue can create the impression that character selection is the whole product. The useful review begins after a card is chosen. Record which details appear on the card, what the primary action promises and whether the next screen keeps the same character unmistakable. If the transition changes names, images or context, pause and confirm what was actually selected.
For a trans persona, examine whether the entry route offers relevant presentation choices or an open-text route to describe the character. Do not label Candy supportive based only on a portrait. The evidence you need is a visible field, a saved summary and a later conversation that can be checked against the setup.
Map the first conversation screen
On entry to chat, identify the character header, conversation controls, route back to the profile and any nearby media action. A buyer deciding between chat and photos needs to know whether those activities share one context or live in separate areas. Record the navigation, not a prediction about output quality.
Send only enough ordinary text to learn the screen structure. Notice whether the interface explains when the conversation is saved and whether another thread can be started without overwriting the first. Leave through normal navigation and return once. That establishes the route you would use later, even though deeper continuity requires a longer account test.
Open Candy AI and compare this step →Follow one photo-related action end to end
Locate the visual action from the active character. Before confirming anything, record the selected character, the wording of the action, any scene or style inputs and any notice about access or credits. If the action moves to another page, check whether the original conversation remains easy to recover.
The result screen should be evaluated as organization: where completed media appears, how it links back to the character and whether another request starts from the same context. Do not infer consistency from one preview or from editorial imagery on this site. A repeated controlled test in your account would be needed for that conclusion.
Treat every commercial prompt as part of the flow
A plan prompt may appear before chat, before saving, during a media action or after a limited interaction. Those placements create different friction. Write down the trigger and whether your character or draft remains intact when you close the prompt. The recoverability of work is a practical buying factor.
Read the final screen for billing interval, renewal wording and any distinction between plan access and consumable actions. This page publishes no amount because the current account screen is the authority for your purchase. If a label is ambiguous, stop rather than assuming that a plan includes every visual action.
Find account controls before building deeply
Open the profile or settings route while the test character is still simple. Locate current billing navigation, support information and any controls related to conversation or character management. A visible menu item is not proof of a particular cancellation or deletion result, so read the current confirmation text before using it.
Also look for the later edit path. The relevant question is whether the details used to establish the persona can be revisited after the character is saved. If only some fields are editable, record exactly which ones. That boundary may matter more than the speed of the initial setup.
Candy compared with a scene-first route
Candy is useful as the character-to-visual side of the Candy versus OurDream comparison. The test asks how quickly a selected profile becomes an active conversation and how clearly a visual request remains tied to it. OurDream is examined from the opposite direction: scene or world context first, then continuing exchange.
Choose between those routes based on your preferred setup labor. If you want to recognize a character and begin immediately, fewer pre-chat decisions may feel clearer. If you want the setting established before dialogue, a scene-oriented path may justify additional steps. Verify both routes rather than treating either design as a quality guarantee.
Open Candy AI and compare this step →How to use this documentation-led review
Treat the page as a route map, not as a promise that every visitor sees the same account state. Product interfaces, regional availability, plan names, included actions and account menus can change. Open the product in your own browser, write down the labels you actually see and compare the complete path from entry screen to account controls. A useful decision comes from the sequence of screens, not from one attractive character card.
Keep the comparison fair by using the same short brief in each product. Choose a visual direction, define a character detail that matters to you, begin a conversation, leave and return, inspect any media request screen, then open the plan and account areas. This method separates a visible control from an assumption about what the control will deliver. It also prevents a promotional landing page from standing in for the signed-in experience.
Why current plan screens must be checked directly
This guide does not publish a fixed price, allowance or promotional reduction because those details can depend on time, location, account state and the screen through which you enter. Compare the billing interval, renewal language, taxes or fees shown before confirmation, and whether a separate credit balance applies to photos or other actions. Capture the final summary for your own records before agreeing to a charge.
A low-friction trial is not merely a small number on an upgrade card. The practical question is how much of the workflow can be inspected before payment and how clearly the interface explains the next paid action. Note where the first paywall appears, what triggered it, whether the back button preserves your work and where the account area explains recurring billing. Those observations remain useful even when the amounts later change.
Claims this comparison deliberately does not make
We do not infer test results, audience size, message quality, image accuracy, data encryption, long-term memory performance or deletion outcomes from marketing copy. We also do not assign numerical scores. A feature label proves only that a label was presented; it does not establish reliability, speed or suitability for every persona. Where an outcome depends on an account, this page tells you what to verify rather than presenting an unobserved result as fact.
The products discussed are fictional companion services intended for adults. A trans persona should be handled as a character choice rather than a spectacle: check whether the builder supports the presentation and relationship context you want, whether edits remain available later, and whether the conversation respects the details you entered. Do not use a fictional system to impersonate or exploit a real person.
