Maya

A futuristic voice assistant that feels native on Android.

Maya is a dark, cyberpunk-style Android assistant app built around voice-first interaction, Gemini-powered responses, and persistent system-level access. It is designed for users who want a highly personalized assistant experience with onboarding for API setup, permissions, background access, and a polished home dashboard.

Business Goals

  • Reach 25% onboarding completion from install within 60 days of launch.
  • Convert 15% of free users to activated or licensed users within 90 days.
  • Maintain a 4.5+ average app store rating after the first 1,000 reviews.
  • Keep 30-day retention above 20% for users who complete onboarding.
  • Reduce onboarding drop-off between step 1 and step 3 to below 35%.

User Goals

  • Set up Gemini API access in under 2 minutes.
  • Grant the permissions needed for voice, background, and assistant features in a guided flow.
  • Use one-tap quick actions like Music, Study, and Journal from the home screen.
  • See status, reminders, and assistant context at a glance in a single dashboard.
  • Access settings, memory, and profile controls without hunting through menus.

Non-Goals

  • Building the actual AI model or training custom LLMs inside the app.
  • Supporting iOS system-level permissions or iPhone-specific assistant behaviors.
  • Implementing full call interception, SMS automation, or hidden system actions beyond standard Android APIs and user-granted permissions.
  • Creating backend account management, billing, or multi-device sync in the first release.

Power User Arjun, 29 - Arjun uses Android as his main work device and wants a voice assistant that can help him stay organized, launch tasks quickly, and reduce app switching. He is comfortable granting permissions if the value is clear and the UI feels polished.

Power User Arjun, 29

  • As a power user, I want to paste my Gemini API key during onboarding, so that I can activate the assistant immediately.
  • As a power user, I want quick action pills for Music, Study, and Journal, so that I can start common workflows with one tap.
  • As a power user, I want background and overlay setup instructions, so that Maya can stay available when I need it.

Busy Professional Sana, 36 - Sana wants a fast assistant experience for reminders, notes, and routine daily coordination, but she does not want a confusing setup process. She needs clear permission explanations and a trustworthy settings area.

Busy Professional Sana, 36

  • As a busy professional, I want the app to explain why each permission is needed, so that I feel confident granting access.
  • As a busy professional, I want a simple greeting and input bar on the home screen, so that I can ask questions without navigating menus.
  • As a busy professional, I want profile fields for name and preferences, so that responses feel personalized.

Tech Enthusiast Dev, 24 - Dev likes testing assistant apps, exploring experimental settings, and tweaking system-level integrations. He expects a futuristic UI, strong responsiveness, and clearly labeled advanced options.

Tech Enthusiast Dev, 24

  • As a tech enthusiast, I want access to advanced permissions and system settings, so that I can enable full assistant functionality.
  • As a tech enthusiast, I want a settings screen with grouped controls, so that I can tune memory, connectivity, and assistant behavior.
  • As a tech enthusiast, I want visible status indicators and license state, so that I know what features are currently active.

Onboarding and Activation · High priority

  • The app must guide users through API setup, permissions, and background configuration before entering the main dashboard.
  • Screen 1 must include a secure API key field with masked input and a save action.
  • Screen 2 must show a clear permissions checklist and trigger Android permission dialogs in sequence.
  • Screen 3 must open battery optimization, accessibility, and overlay settings pages using system intents.
  • Progress through onboarding must persist locally so users can resume after app restart.
  • If a permission is denied, the app must explain the impact and provide a retry path.

Home Dashboard UI · High priority

  • The main screen must present the assistant experience in a visually rich, voice-first layout optimized for daily use.
  • Top app bar must include menu, title, notifications, and avatar actions.
  • The central orb must animate subtly and remain the visual focal point.
  • Quick action pills, weather/date/mood cards, and the message composer must be visible without excessive scrolling on common Android screen sizes.
  • Bottom navigation must include Home, Scan, central mic action, Memories, and Chat.
  • The license banner must display free-mode status and an activation CTA.

Navigation and Drawer · Medium priority

  • The app must provide a clear side drawer for fast access to productivity and system areas.
  • Drawer sections must match Productivity and System groupings.
  • Items must be tappable navigation targets with consistent icons and labels.
  • Drawer header must brand the product clearly as Maya by The Hunter AI.
  • Footer must show version information sourced from app config.
  • Navigation state must remain synchronized with the current screen.

Settings and Profile Management · Medium priority

  • The app must allow users to manage assistant behavior, personal details, and connectivity from dedicated screens.
  • Settings must use grouped categories for account, assistant, work and messages, connected accounts, memory and data, and system.
  • Profile form must include name, gender, phone, music preferences, and API key management.
  • Toggles must persist locally and reflect current state on re-entry.
  • Advanced items such as secret settings and battery saver must be clearly separated from primary controls.
  • Fields must validate empty and malformed input with inline feedback.

Design System and Accessibility · Low priority

  • The UI must follow the intended dark futuristic visual language while staying readable and performant.
  • Use a deep navy background with dark slate cards and neon blue-purple accents.
  • Use rounded corners around 16px for cards, inputs, and buttons.
  • Support readable contrast, scalable text, and touch targets suitable for Android accessibility standards.
  • Animated glow effects must remain subtle and not harm frame rate.
  • The layout must degrade gracefully on smaller screens and support safe areas.

First-Time User Experience

  • Install and open Maya on Android.
  • Review the welcome and API key setup screen, paste the Gemini API key, and save it.
  • Grant required microphone access and review optional permissions in a guided sequence.
  • Enable background features such as battery optimization exceptions, accessibility, and overlay access.
  • Arrive at the home dashboard with the orb, quick actions, and message composer visible.
  • Target time to value: under 3 minutes from first launch to first dashboard interaction.

1. Onboarding setup

  • The user enters the API key and saves it before any assistant actions are available.
  • Mask the key input while allowing paste from clipboard.
  • Show inline success or failure states if the key format is invalid or missing.
  • Persist the key securely on-device and avoid showing it in plain text after save.

2. Permission guidance

  • The user grants the permissions required for voice and assistant features.
  • Explain why each permission is requested before system dialogs appear.
  • Only request permissions after the user taps Allow all.
  • If a permission is permanently denied, offer a settings shortcut instead of looping the dialog.

3. Background configuration

  • The user is guided to system settings for battery optimization and special access.
  • Launch the correct Android settings intents for battery optimization, accessibility, and overlay.
  • Show clear completion state for each setting after returning to the app.
  • Handle cases where a device does not support a specific settings panel.

4. Home interaction

  • The user lands on the dashboard and can start interacting immediately through voice or text.
  • Make the mic and bottom composer the main call to action.
  • Display greeting, energy, license, and quick action context on the first view.
  • Keep navigation consistent so users can switch to scan, memories, or chat without losing state.

5. Settings and profile

  • The user tunes assistant behavior and personal preferences from grouped screens.
  • Use section headers and clear dividers to prevent overwhelming the user.
  • Validate profile inputs and show save confirmation.
  • Treat advanced and risky settings as secondary actions with explicit labels.

Advanced Features and Edge Cases

  • Resume onboarding after app restart or app kill without losing progress.
  • Support device rotation and different Android screen sizes without layout breakage.
  • Show fallback states when notifications, camera, or location permissions are not available.
  • Surface a restricted mode if the API key is missing, revoked, or invalid.
  • Offer a safe path to re-open system settings when users revoke permissions later.

UI and Interaction Principles

  • Use neon glow accents sparingly around the orb and active buttons to preserve legibility.
  • Keep the background dark with layered cards and soft shadows for depth.
  • Use large tap targets, high contrast text, and simple labels for accessibility.
  • Ensure animations are lightweight and smooth at 60 fps on mid-range Android devices.
  • Preserve a premium cyberpunk look without sacrificing clarity or usability.

Sana installs Maya because she wants a voice assistant that feels modern, not cluttered. During onboarding, she pastes her Gemini API key, grants the required microphone and background permissions, and reaches the dashboard in just a few minutes.

Once inside, she sees the glowing orb, quick action pills, and a single input bar that makes the app feel instantly usable. When she wants to personalize the assistant, she opens Settings and Profile to update her name, music preferences, and system controls without needing a tutorial.

The result is a product that feels premium and responsive while reducing setup friction. For the business, that means more users completing activation, using the app daily, and converting to a paid or licensed experience because they understand the value quickly.

User-Centric Metrics

  • 80% of onboarding users complete API setup successfully.
  • 70% of users grant microphone permission on first request.
  • 50% of activated users send at least one prompt within 5 minutes of reaching Home.
  • Average time from first launch to first successful assistant interaction under 3 minutes.
  • Less than 10% of users abandon onboarding after step 2.

Business Metrics

  • 25% install-to-activation conversion within 60 days.
  • 15% free-to-paid or free-to-licensed conversion within 90 days.
  • 30-day retention above 20% among activated users.
  • Average app rating at or above 4.5 stars after launch stabilization.

Technical Metrics

  • 99.5% monthly app availability for any backend-dependent screens.
  • Under 300 ms UI response time for local navigation and taps.
  • Under 2 seconds to render the Home screen after onboarding completion on mid-range devices.
  • Zero critical permission or API-key handling security incidents in the first release cycle.

Tracking Plan

  • Track onboarding_started when the user enters the flow.
  • Track api_key_saved when the user saves a Gemini key.
  • Track permission_dialog_shown and permission_granted for each requested permission.
  • Track background_setup_opened and background_setup_completed for special Android settings.
  • Track home_viewed when the dashboard loads successfully.
  • Track quick_action_tapped for Music, Study, and Journal.
  • Track settings_saved and profile_updated when users persist preferences.

Technical Needs

  • Build with React Native using Expo for rapid Android iteration, or Flutter if the team prefers a single-codebase rendering model.
  • Use a state management solution such as Zustand, Redux Toolkit, or Riverpod to persist onboarding and settings state.
  • Store secrets with secure local storage such as react-native-keychain or flutter_secure_storage.
  • Use Reanimated or Flutter animations for the orb glow and subtle motion.
  • Implement Android native bridges or Expo config plugins for permissions, settings intents, and special access screens.
  • Structure the app with reusable cards, pills, drawers, form controls, and bottom navigation components.
  • Add analytics instrumentation with a lightweight event pipeline such as Firebase Analytics or PostHog.

Integration Points

  • Google Gemini API for AI responses and assistant behavior.
  • Android runtime permissions and special settings intents for microphone, notifications, camera, location, accessibility, and overlay.
  • Firebase Analytics or PostHog for event tracking.
  • Secure local storage for API key persistence and user profile data.
  • Optional push notifications through Firebase Cloud Messaging if reminders are added later.

Data Storage & Privacy

  • Store the API key only in encrypted local storage and never in logs.
  • Keep profile data minimal and allow users to edit or clear it from settings.
  • Request only the permissions needed for the feature the user is enabling at that moment.
  • Provide a privacy note explaining what data stays on-device versus what is sent to Gemini.
  • Prepare consent and deletion flows aligned with GDPR and CCPA expectations if accounts or cloud sync are introduced later.

Scalability & Performance

  • Keep the initial render light by loading only the Home screen bundle after onboarding.
  • Cache static configuration and theme tokens locally to avoid repeated fetches.
  • Use lazy loading for secondary screens such as settings and drawer destinations.
  • Limit animation complexity so the orb remains smooth on lower-end Android phones.

Potential Challenges

  • Android permission friction may reduce completion; mitigate by explaining value before requesting dialogs and allowing resume later.
  • Special access settings vary by device brand; mitigate by checking device capability and showing device-specific guidance when needed.
  • Securely storing API keys can be error-prone; mitigate with encrypted storage and strict log redaction.
  • A visually rich UI can hurt performance; mitigate with memoized components, lightweight animations, and careful image use.
  • Users may be confused by advanced or risky settings; mitigate with clear labels, grouped sections, and explicit confirmations for sensitive actions.

Team & resourcing - Small team - 2 mobile engineers, 1 product designer, part-time PM, and optional QA support.

Phase 1: MVP Onboarding and Shell · Weeks 1–3

  • App scaffold with navigation, theme tokens, and reusable UI components.
  • Three onboarding screens with API key input, permissions checklist, and background setup actions.
  • Encrypted local storage for API key and onboarding completion state.
  • Basic analytics events for onboarding progression.

Phase 2: Home Dashboard and Navigation · Weeks 4–6

  • Main dashboard with top app bar, license banner, greeting, orb, quick actions, widgets, and composer.
  • Bottom navigation with Home, Scan, center mic, Memories, and Chat.
  • Side drawer with productivity and system sections.
  • Polished dark cyberpunk styling and animated orb effects.

Phase 3: Settings and Profile · Weeks 7–8

  • Grouped Settings screen with toggles and advanced items.
  • Personal Profile screen with name, gender, phone, music preferences, and API key management.
  • Persistence for settings and profile fields.
  • Validation, empty states, and save confirmation flows.

Phase 4: Hardening and Release Prep · Weeks 9–10

  • Permission edge-case handling and device compatibility checks.
  • Performance tuning for animations and navigation.
  • Accessibility pass for contrast, tap targets, and readable labels.
  • Release candidate build, QA checklist, and analytics verification.

Paste this into Cursor, Bolt, Lovable, or v0 to start building.

Build a React Native Android app called Maya using Expo and TypeScript. Create a dark, futuristic AI assistant UI with neon blue and purple accents, rounded 16px cards, soft glow effects, and Inter or Roboto typography.

Core screens and flows:
1. Onboarding flow with 3 screens:
   Screen 1: API Key Setup with secure masked text input, helper text, and Save and continue button.
   Screen 2: App Permissions showing a checklist for Microphone required, Notifications, Camera, Phone Calls, Contacts, SMS, Location, Gallery, Call Management, Bluetooth, plus an Allow all button that requests Android permissions sequentially.
   Screen 3: Background Setup explaining battery optimization, accessibility, and overlay permissions, with an Allow button that opens system settings intents.
2. Home dashboard:
   Top app bar with hamburger menu, title Maya, notification bell, and avatar.
   License banner reading Free mode - 10:00 min left today with Activate button.
   Greeting section, energy counter, animated glowing central orb with M.A.Y.A and AI ASSISTANT text.
   Quick action pills for Music, Study, Journal.
   Three cards for Weather, Date, Mood.
   Bottom text composer with placeholder Ask Maya anything... and send icon.
   Bottom tab navigation with Home, Scan, center mic action, Memories, Chat.
3. Side drawer:
   Header Maya by The Hunter AI.
   Sections for Productivity and System with the listed items.
   Footer version label.
4. Settings screen:
   Grouped sections for Account, Assistant, Work and Messages, Connected Accounts, Memory and Data, System, including toggles and list items such as Secret settings Girlfriend mode 18 plus, Battery saver, and Advanced Permissions.
5. Personal Profile screen:
   Form fields for Your name, Gender selection Male Female Prefer not to say with note about Hindi grammar, Phone number, Music preferences with Default app and Favorite song, and API key storage management.

Technical requirements:
Use React Navigation or Expo Router for navigation. Use a component-based architecture with reusable cards, buttons, pills, inputs, section headers, drawer items, and bottom nav. Use local state management with Zustand or Redux Toolkit. Persist onboarding progress, settings, and profile data in secure storage for the API key and AsyncStorage for non-sensitive preferences. Add basic mock data for weather, date, mood, and license banner. Include placeholder event tracking functions for onboarding, permission, and settings events. Make the app responsive for common Android screen sizes and support safe areas. Include stubbed hooks and service files for Gemini API integration, permission handling, and settings deep links.

Data model:
User profile with name, gender, phone, music preferences, API key metadata, onboarding completion flags, permissions state, and settings toggles.

Deliver a clean folder structure, reusable UI components, theme tokens, navigation setup, sample screen implementations, and mocked logic where native functionality is not available in Expo.

Business Idea

Act as an Expert Mobile App Developer (React Native / Flutter). I want to build an AI Voice Assistant Android App named "Maya". Based on my UI designs, generate the complete frontend code structure and logic. App Core Features: Maya is a voice-first AI assistant powered by the Google Gemini API. The app requires heavy background permissions to act as a system assistant. Here is the exact structure you need to code: 1. ONBOARDING FLOW (3 Screens): - Screen 1: API Key Setup. Instructs user to get a Gemini API key. Includes a text field to paste the key and a "Save & continue" button. The text field should be secure (password type). - Screen 2: App Permissions. A list of permissions (Microphone [Required], Notifications, Camera, Phone Calls, Contacts, SMS, Location, Gallery, Call Management, Bluetooth). It features an "Allow all" button that triggers the Android OS permission dialogs sequentially. - Screen 3: Background Setup. Instructs user to disable battery optimization and enable accessibility/overlay permissions. Features an "Allow" button that opens the system settings for these specific features. 2. MAIN DASHBOARD (Home): - Top App Bar: Hamburger menu (opens side drawer), Title "Maya", Notification Bell, User Avatar. - A License Banner showing "Free mode - 10:00 min left today" with an "Activate" button. - Greeting section: "Good morning, there" with an energy counter (⚡ 1). - A large, glowing, animated central Orb with the text "M.A.Y.A" and "AI ASSISTANT". - Three quick action pills above the orb: "Music", "Study", "Journal". - Three grid widgets below: Weather Card (Temp, condition), Date Card, Mood Card. - Bottom Input area: "Ask Maya anything..." text box with a send icon. - Bottom Navigation Bar: Home, Scan, Big Mic Button (Center), Memories, Chat. 3. SIDE DRAWER (Navigation Menu): - Header: Maya by The Hunter AI. - "PRODUCTIVITY" Section: Markets, Marketing, Documents, Website/Coding, Study/Whiteboard. - "SYSTEM" Section: Settings, Maya Rules, PC <-> Phone. - Footer: Version number. 4. SETTINGS & PROFILE SCREENS: - Settings Screen: Grouped in categories (Account, Assistant, Work & Messages, Connected Accounts, Memory & Data, System). Include toggles and list items like "Secret settings (Girlfriend mode 18+)", "Battery saver", and "Advanced Permissions". - Personal Profile Screen: Form fields for "Your name", Gender selection (Male/Female/Prefer not to say with a note about Hindi grammar), Phone number, Music preferences (Default app, Favorite song), and API key storage/management. Design System & UI Style: - Theme: Dark mode, futuristic, sleek, cyberpunk/AI aesthetic. - Colors: Deep Navy Blue background (#090b14 approx), Dark Slate Gray for cards (#1a1e2d), Primary Accent Color: Neon Blue/Purple (#4b68ff and #a64dff for the M.A.Y.A text). - Typography: Clean Sans-serif (Inter or Roboto). - Rounded corners for all cards, buttons, and input fields (approximate border-radius: 16px). - Use subtle glowing effects for the AI orb and active buttons. Please write the boilerplate code for this application, focusing on the UI components (React Native using Expo / or Flutter). Provide the layout structure for the Onboarding Flow, Home Screen, and Settings Screen.

Make My PRD

Design by The Resonance | Powered by GPC – The AI Transformation Company