mobile-games

Address mobile platform constraints for touch input, battery, and app store compliance.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Sanali209/pla_teplate --skill mobile-games-sanali209
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-games
Source: https://github.com/Sanali209/pla_teplate/tree/main/_blueprint/skills/game-development/mobile-games
Command: npx skills add https://github.com/Sanali209/pla_teplate --skill mobile-games-sanali209

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile game development faces unique platform-specific challenges including imprecise touch input, strict battery and thermal limits, and rigid app store submission requirements that can lead to poor user retention or rejected releases if unaddressed. This skill provides clear, actionable guidance to navigate these constraints effectively.

Core Features & Use Cases

  • Platform Constraint Best Practices: Covers touch input design, battery and thermal optimization, screen responsiveness, and interruption handling for mobile devices.
  • App Store Compliance: Outlines mandatory requirements for iOS App Store and Google Play to avoid submission rejection.
  • Monetization Guidance: Compares common mobile game monetization models (premium, free + IAP, ads, subscription) and their ideal use cases. Use case: If you are developing a casual mobile puzzle game, use this skill to ensure your touch targets meet accessibility guidelines, optimize performance to minimize battery drain, and fulfill App Store privacy label requirements before launch.

Quick Start

Use the mobile-games skill to review your new mobile game's design for touch usability, battery efficiency, and app store compliance before you submit it for review.

Frequently Asked Questions about mobile-games

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

FAQPage Schema
What are the app store compliance requirements for mobile games to avoid submission rejection?

App store compliance for mobile games requires fulfilling mandatory iOS App Store and Google Play privacy label requirements and submission guidelines. Meeting these specific platform requirements prevents poor user retention and avoids rejected releases during the app review process.

How do I optimize mobile game performance to minimize battery drain?

Optimize mobile game performance to minimize battery drain by implementing FPS throttling, thermal management, and screen responsiveness optimizations. Addressing these strict battery and thermal limits effectively prevents poor user experience caused by device overheating or rapid power depletion.

How do I design touch input for mobile games to meet accessibility guidelines?

Design touch input for mobile games by applying actionable platform-specific best practices for touch target sizing. Ensuring touch targets meet accessibility guidelines prevents imprecise touch input issues and improves overall user retention for casual mobile puzzle games.

What is the best way to choose a monetization model for a mobile game?

Choosing a monetization model for a mobile game involves comparing common approaches like premium, free with in-app purchases, ads, and subscriptions. Evaluating these models against your ideal use cases ensures you select the most appropriate revenue generation strategy.

Can I use this mobile game development guidance for both iOS and Google Play platforms?

Yes, you can use this mobile game development guidance for both iOS and Google Play platforms. It provides actionable platform-specific best practices addressing unique constraints like touch input design, battery optimization, and privacy label implementation for both major app stores.

Why does my mobile game keep getting rejected during app store submission?

Your mobile game may be getting rejected during app store submission due to unfulfilled iOS App Store or Google Play compliance requirements. Addressing strict platform constraints like privacy label implementation and mandatory submission guidelines before launch prevents release rejection.