android-native-expert

Enforce Android 16 UX standards with Material 3 Expressive guidelines.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/armanisadeghi/real-singles --skill android-native-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-native-expert
Source: https://github.com/armanisadeghi/real-singles/tree/main/.cursor/skills/android-native-expert
Command: npx skills add https://github.com/armanisadeghi/real-singles --skill android-native-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Android implementations align with native feel by enforcing Android 16 constraints and Material 3 Expressive design patterns, preventing drift from web or iOS implementations.

Core Features & Use Cases

  • Enforces edge-to-edge rendering and adaptive layouts for 600dp+ screens.
  • Guides theming with dynamic colors and M3 Expressive components.
  • Provides compliance and review guidance for Android-specific features, components, and UX patterns.

Quick Start

Review the Android-native-expert guidelines and apply edge-to-edge, M3 Expressive patterns, and Android 16 requirements to your next Android screen.

Frequently Asked Questions about android-native-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement edge-to-edge rendering and adaptive layouts for Android 16?

Edge-to-edge rendering and adaptive layouts for Android 16 are implemented by enforcing native-Android UX standards that apply edge-to-edge rendering and adaptive layouts specifically designed for 600dp+ screens, preventing drift from web or iOS implementations.

What is Material 3 Expressive design and how does it apply to Android native development?

Material 3 Expressive design is a native-Android UX standard that guides theming with dynamic colors and M3 Expressive components. It applies to Android-specific feature development to ensure implementations align with native feel and prevent platform drift.

How do I add haptics and spring-based motion using Reanimated in an Android app?

Haptics and spring-based motion using Reanimated are implemented by following Android 16 constraints and Material 3 Expressive guidelines. This enforces native-Android UX standards for expressive feedback and motion in your app's components.

Does this Android native UX guidance work for code reviews and feature evaluations?

Android native UX guidance works for code reviews and feature evaluations by providing compliance and review guidance for Android-specific features, components, and UX patterns. It checks implementations against native feel and Material Design requirements.

Why does my Android app feel like a web or iOS port instead of a native application?

An Android app feels like a web or iOS port when it drifts from native-Android UX standards. Enforcing Android 16 constraints and Material 3 Expressive design patterns for edge-to-edge rendering, theming, and haptics prevents this platform drift.