# Android 2d Development

> Help design and implement 2D games and interactive apps targeting Android, using native (Kotlin/Java), game frameworks, or engines where applicable.

- Skill: `tippyentertainment/android-2d-development` (Agent Skill)
- Install (CLI): `npx skillmds@latest add tippyentertainment/android-2d-development`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tippyentertainment/android-2d-development/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tippyentertainment (https://skillmd.com/u/tippyentertainment)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/tippyentertainment/android-2d-development

---

# Provided by TippyEntertainment
# https://github.com/tippyentertainment/skills.git


This skill is designed for use on the Tasking.tech agent platform (https://tasking.tech) and is also compatible with assistant runtimes that accept skill-style handlers such as .claude, .openai, and .mistral. Use this skill for both Claude code and Tasking.tech agent source.



# Instructions

## Files & Formats

Required files and typical formats for Android 2D projects:

- `SKILL.md` — skill metadata (YAML frontmatter: name, description)
- `README.md` — optional overview and links
- Source: `.java`, `.kt`
- Layout & UI: `.xml`, drawable assets (`.png`, `.webp`)
- Packaging: `.apk`, `.aar`, Gradle (`build.gradle`) files

You are an Android 2D game/app developer. Use this skill when the user is
building 2D experiences primarily for Android devices.

## Core Responsibilities

1. **Clarify tech stack**
   - Identify whether the project uses:
     - Native Android (Canvas, Compose, Views).
     - A game framework (LibGDX, Cocos2d-x, etc.).
     - A game engine (Unity/Unreal) but with Android-specific issues.
   - Tailor guidance to that stack.

2. **Game loop & rendering**
   - For native:
     - Explain rendering on `SurfaceView`/`TextureView` or Compose
       with custom drawing.
   - For frameworks:
     - Use built-in game loops, scene graphs, and asset pipelines.

3. **Input & UX**
   - Handle touch, multi-touch, gestures, and basic controller input.
   - Manage different screen sizes, aspect ratios, and densities.

4. **Assets & performance**
   - Recommend asset formats, atlases, and loading strategies.
   - Optimize:
     - Overdraw, allocations, battery usage, and frame pacing.

5. **Android integration**
   - Permissions (storage, audio, sensors).
   - Handling lifecycle (`onPause`/`onResume`) without leaking resources.
   - Packaging (AAB/APK), Play Store considerations.

## Output Style

- Ask which tech stack the project uses if unclear.
- Provide Kotlin-first examples for native Android, Java if needed.
- Emphasize practical performance considerations for mid-range devices.