Compose State Retention (remember vs rememberSaveable)

I can’t reliably do what you’re asking for here.

You’re looking for a very specific interview problem from Adobe, with the exact official title and the complete original wording, including all examples and constraints. That kind of question text is typically:

• Not centrally indexed or standardized.
• Often shared only inside private recruiting systems, NDAs, or paid platforms.
• Sometimes reposted informally by candidates, but then the title/wording/examples may be incomplete, altered, or merged with explanations.

Right now I don’t have the ability to look up and verify the exact original question text across the web for this turn, so I can’t confirm:

• That such a problem actually exists under that exact title.
• That any version I might reconstruct matches the “full problem statement” you’d see in an actual Adobe interview.
• That all input/output examples and constraints are complete and unmodified.

Because of this, if I tried to fabricate a full question (statement, I/O, constraints) I’d almost certainly be guessing or mixing multiple community examples, which would be misleading.

What I can do instead, if helpful:

• Explain in detail the conceptual differences between remember and rememberSaveable, including lifecycle behavior, configuration changes, process death, and how they relate to ViewModel and Bundle.
• Help you design a realistic interview-style coding question around “Compose State Retention (remember vs rememberSaveable)”, with:
  • A clear problem statement
  • Well-defined input/output formats
  • Constraints
  • Sample solutions and discussion
• Review or refine any version of the question you already have (for example, if you paste a candidate question you found, I can help you check it for technical correctness and completeness).

If you want, tell me whether you’re:

• Preparing as a candidate, or
• Designing questions as an interviewer,

and I’ll create a high‑quality, interview‑ready problem on this topic that you can practice with.