Mobile App Feature Planner

Plan mobile app features with platform-specific considerations for iOS and Android.

**App Type:** [E-COMMERCE / SOCIAL / PRODUCTIVITY / HEALTH & FITNESS / FINANCE / EDUCATION / TRAVEL]
**Target Platforms:** [iOS ONLY / ANDROID ONLY / BOTH (SWIFTUI + JETPACK COMPOSE)]
**Monetization Model:** [FREE WITH ADS / FREEMIUM / PAID DOWNLOAD / SUBSCRIPTION]

**Feature Planning Framework:**

**Core Features (MVP):**
- User onboarding flow: splash screen → welcome carousel → sign up/login → permission requests → empty state or dashboard
- Authentication: email/password, biometric login (Face ID / fingerprint), social auth integration
- Navigation structure: tab bar vs. drawer, deep linking strategy, back stack management
- Core content display: list/grid views with pull-to-refresh, infinite scroll, skeleton loading states
- Search functionality: local search with fuzzy matching, filter/sort controls, recent searches

**Platform-Specific Considerations:**
- iOS (SwiftUI):
  * Human Interface Guidelines compliance
  * Dynamic Type for accessibility (font scaling)
  * Haptic feedback integration (UIImpactFeedbackGenerator)
  * WidgetKit home screen widgets
  * App Clip support for lightweight experiences
  * Privacy manifest requirements
- Android (Jetpack Compose):
  * Material Design 3 compliance with dynamic color theming
  * Adaptive layouts (phone, tablet, foldable)
  * WorkManager for background tasks
  * App Bundles for optimized APK delivery
  * Android Auto/Wear OS extension potential

**Offline-First Architecture:**
- Local database strategy (Core Data / Room) with conflict resolution rules
- Sync strategy: pull on app launch, push on user actions, background sync intervals
- Offline indicator UI and graceful degradation of features
- Queue system for actions performed while offline

**Push Notification Strategy:**
- Notification types: transactional, engagement, marketing, system alerts
- Deep link mapping (which notification opens which screen)
- Notification grouping and cancellation rules
- User preference center for notification categories
- FCM (Firebase Cloud Messaging) + APNs setup architecture

**App Store Optimization Checklist:**
- Keyword research strategy for app store search
- Screenshot design guidelines (feature callouts, benefit-focused copy)
- App description with keyword optimization
- Review request timing (after positive user action, not at install)
- Rating prompt integration (SKStorefront / In-App Review API)

**Performance Budgets:**
- Initial load time target: <3 seconds on 4G
- Memory usage limit per screen (<150MB)
- Image optimization strategy (WebP/AVIF, lazy loading, responsive sizing)
- Network request batching and caching headers

How to Customize It

Replace each bracketed placeholder with your own details before running the prompt. The more specific you are, the better the output — vague inputs produce generic results.

• [E-COMMERCE / SOCIAL / PRODUCTIVITY / HEALTH & FITNESS / FINANCE / EDUCATION / TRAVEL]Swap in your e-commerce or social or productivity or health & fitness or finance or education or travel.
• [FREE WITH ADS / FREEMIUM / PAID DOWNLOAD / SUBSCRIPTION]Swap in your free with ads or freemium or paid download or subscription.

When to Use It

• Scoping an MVP feature set with platform-specific effort visible before committing to "both platforms at launch."
• Planning permission-heavy features (location, notifications, camera) where the request flow determines the grant rate.
• Choosing a monetization model with the feature implications (paywalls, restore purchases, trial logic) mapped out.

Tips for Better Results

• 1Decide native vs. cross-platform first and tell the prompt — feature plans differ meaningfully between SwiftUI/Compose and React Native/Flutter.
• 2Ask for the notification permission strategy specifically; asking at first launch is the default and it's the worst option.
• 3Have it flag which features App Store review commonly rejects — finding out at submission costs you weeks.