Note that the inbox UI requires a FragmentActivity host

IterableInboxFragment needs a FragmentManager, so Compose-first apps
(whose host defaults to ComponentActivity) crash at attach when adding
it. The SDK has no Compose-native inbox, so the host activity's base
class must be switched first. Short note added after the slug routing
table, where inbox work is picked up.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: franco-zalamena-iterable

iterable-android/SKILL.md

@@ -330,6 +330,13 @@ mismatch.
 | `updateUser`, profile data fields, JSON merging | `updating-user-profiles` |
 | Unknown User Activation (anonymous → identified upgrade) | `setting-up-unknown-user-activation` |
 
+> **Inbox UI is fragment-based.** `IterableInboxFragment` needs a
+> `FragmentManager`, so its host must be a `FragmentActivity` /
+> `AppCompatActivity`. Compose-first apps default their host to
+> `ComponentActivity`, which has none — hosting the fragment there crashes
+> at attach (`… is not within a subclass of FragmentActivity`). The SDK ships
+> no Compose-native inbox; switch the host activity's base class before adding it.
+
 For tasks that span multiple areas (e.g. "wire up the whole SDK end to end"),
 fetch `android-sdk` first — it tells you which others to load and in what
 order.