android-platform
Android core components lifecycle, Activities, Fragments, Services, Intent system. Use when working with Android components or handling lifecycle.
When & Why to Use This Skill
This Claude skill provides expert-level guidance on the Android platform's core components and lifecycle management. It assists developers in mastering Activities, Fragments, Services, and the Intent system, offering best practices for resource management, state persistence, and robust application architecture to ensure high-performance mobile development.
Use Cases
- Implementing lifecycle-aware components to prevent memory leaks and optimize app performance during state transitions.
- Configuring Services and the Intent system for efficient background processing and seamless inter-component communication.
- Designing Fragments and Activities that gracefully handle configuration changes, such as screen rotations, using modern Android architectural patterns.
| name | platform |
|---|---|
| description | Android core components lifecycle, Activities, Fragments, Services, Intent system. |
| version | "2.0.0" |
| sasmp_version | "1.3.0" |
| bonded_agent | 02-platform |
| bond_type | PRIMARY_BOND |
| atomic | true |
| single_responsibility | Android platform components & lifecycle |
| type | string |
| enum | [activity, fragment, service, intent, permission] |
| required | false |
| max_attempts | 2 |
| backoff | exponential |
| on_failure | return_lifecycle_diagram |
| level | info |
| include | [query, component_type, response_time] |
Android Platform Skill
Quick Start
Activity Lifecycle
class MainActivity : AppCompatActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_main)
}
override fun onDestroy() {
super.onDestroy()
// Cleanup
}
}
Fragment Usage
class UserFragment : Fragment() {
private val viewModel: UserViewModel by viewModels()
override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
super.onViewCreated(view, savedInstanceState)
viewModel.user.observe(viewLifecycleOwner) { user ->
updateUI(user)
}
}
}
Key Concepts
Lifecycle Callbacks
onCreate(): Initial setuponStart(): Become visibleonResume(): Gain focusonPause(): Lose focusonStop(): HiddenonDestroy(): Final cleanup
Fragment Lifecycle
Similar to Activity but with:
onAttach(): Attached to activityonDetach(): Detached- Fragment manager for transactions
Intent System
// Explicit
startActivity(Intent(this, DetailActivity::class.java))
// Implicit
startActivity(Intent(Intent.ACTION_VIEW, Uri.parse("https://example.com")))
Services
- Started:
startService() - Bound:
bindService() - Foreground: Visible notification
Best Practices
✅ Handle lifecycle properly ✅ Use ViewModel for state ✅ Unregister listeners ✅ Test configuration changes ✅ Respect process lifecycle