android-platform-patterns

What problem does it solve?

It prevents duplicated or inconsistent Android helper logic by guiding contributors to reuse existing platform-layer APIs across the AniTrend app.

Core Features & Use Cases

• Platform-first helper reuse: Directs you to inspect :android:core, :android:navigation, :android:deeplink, and :app:core before creating new utilities.
• Clear ownership boundaries: Defines what belongs in platform :android:* modules versus feature-specific modules to avoid tangled abstractions.
• Decision rules for common touchpoints: Helps you choose the right existing controllers, notification flows, theme/config wiring, router usage, and context/fragment utilities.
• Real code anchors: Provides canonical files and paths to copy and adapt when a concrete implementation is needed.

Quick Start

Before adding any new Android helper, open the relevant platform module list and confirm whether an existing implementation already covers your configuration, theme, navigation, deeplink, notification, router, or context/fragment use case.