feat: Add interview questions for Coroutines, Compose, and Launch Modes

[shreeharshshinde]

Hi there!

This PR contributes a set of new Android interview questions as part of the Hacktoberfest initiative.

Additions

• A question comparing StateFlow and SharedFlow.
• A question explaining the use cases for remember vs. rememberSaveable in Jetpack Compose.
• A question detailing the different Activity launch modes.

This helps expand the repository's question bank with topics relevant to modern Android development.

Closes #28

Summary by CodeRabbit

• Documentation
  • Added an advanced Android Q&A guide covering: Kotlin Flow (StateFlow vs SharedFlow), Jetpack Compose remember vs rememberSaveable, Activity launch modes, Compose stability annotations, coroutineScope vs supervisorScope exception handling, Dagger/Hilt scopes, and an offline-first data sync architecture (SSOT, Repository, Retrofit, WorkManager, conflict resolution, Paging 3). Provides concise explanations, practical notes, and structured sections for quick reference.

[coderabbitai]

Walkthrough

A new Markdown document, android_advanced_questions.md, was added containing Android interview-style questions with concise answers on topics like Kotlin Flow, Jetpack Compose state and stability, Activity launch modes, coroutine scopes, Dagger/Hilt scopes, and an outline of an offline-first sync architecture with Paging.

Changes

Cohort / File(s)	Summary
Docs: Android interview Q&A android_advanced_questions.md	Added a sectioned Q&A document covering Kotlin Flow (StateFlow/SharedFlow), Compose remember/rememberSaveable and stability annotations, Activity launch modes, coroutineScope vs supervisorScope, Dagger/Hilt scopes, and an offline-first architecture with SSOT, Repository, Retrofit, WorkManager, conflict resolution, and Paging 3 RemoteMediator.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

Thump-thump, I hop through bytes and lore,
New questions sprout—more carrots to store. 🥕
Compose and Flows in tidy rows,
Hilted burrows where DI grows.
Offline dreams sync moonlit light—
A rabbit’s notes for interview night.

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly summarizes the main addition of interview questions on Coroutines, Jetpack Compose, and Activity launch modes, matching the PR description and using a clear, concise convention.
Linked Issues Check	✅ Passed	The pull request adds a Markdown file with new Android interview questions and answers following the prescribed format, covering topics such as StateFlow vs SharedFlow, remember vs rememberSaveable, and Activity launch modes, thereby fulfilling the objectives of issue #28 to contribute community-driven interview content.
Out of Scope Changes Check	✅ Passed	All changes are confined to adding a single Markdown file with relevant interview questions as specified by the linked issue and do not introduce any unrelated code modifications or extraneous files.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d0a726a and 1c0a444.

📒 Files selected for processing (1)

• android_advanced_questions.md (1 hunks)

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Update scope target to SingletonComponent.

@Singleton has been scoped to SingletonComponent ever since Hilt dropped ApplicationComponent. Please update the wording so readers aren’t pointed to a component that no longer exists in current Hilt versions.

🤖 Prompt for AI Agents

In android_advanced_questions.md around lines 50 to 51, the text refers to the
deprecated ApplicationComponent for @Singleton; update the wording to reference
SingletonComponent instead: replace "scopes a dependency to the
ApplicationComponent" with "scopes a dependency to the SingletonComponent" and
adjust any nearby phrasing that implies ApplicationComponent so the description
correctly states that the instance is created once for the application's
lifecycle and is provided by Hilt's SingletonComponent.