android / android/architecture-samples

[todo-mvp] Why use fragment?

Open
#859 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
45.8k
Forks
11.9k
PR merge metrics
No merged PRs in 30d

Description

I found that an activity in the project will create a fragment correspondingly. What are the benefits of this? I don't think fragments are necessary.
image
image

Contributor guide

Open the contributing guide

Research direction

Start by tracing the activity and its corresponding fragment shown in the issue, then compare their responsibilities and lifecycle roles in the sample. Document the architectural rationale for keeping both, or identify the specific simplification needed; done means the relationship and benefits are clearly explained.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.