Step-by-Step Experiments with AI Tools
1. Writing the Most Effective Prompt
ChatGPT
ChatGPT helped me craft a rich and structured prompt that included:
- Context, user pain points, design goals, and constraints
- Clear instructions (3 UI ideas + wireframes + pros/cons)
- References to apps like Spotify or Apple Podcasts
It responded like a smart design partner: structured, clear, and fast.
📎 Prompt title:
“Redesign in-app audio playback experience for HUXE app to improve control, discoverability, and multitasking”
📌
**Prompt Title:**
"Redesign in-app audio playback experience for HUXE app to improve control, discoverability, and multitasking"
**Context:**
HUXE is an iOS app for discovering and listening to podcasts and audio content. While exploring the app, I noticed issues with the current in-app audio playback experience:
- Sometimes two podcasts play at once.
- It’s hard to locate the pause button and know which content is playing.
- When I want to listen and explore simultaneously, I must exit the exploration view to stop audio.
- If I switch to another piece of content, the previous audio stops and cannot resume from where I left off.
**Goal:**
Redesign the in-app audio playback control system to:
1. Allow users to easily identify and control currently playing content without losing context.
2. Support smooth multitasking between listening and exploring without losing playback position.
3. Provide a persistent visual/audio indicator visible across all in-app pages.
4. Keep the current HUXE design language but be open to wireframes for testing.
**Must-Have Requirements:**
- **Persistent Audio Player Indicator**:
- Always visible in the app (floating bar or docked at the bottom).
- Shows content title, thumbnail, elapsed time, and progress bar.
- Provides play/pause and skip controls without leaving the current screen.
- **Playback Status Clarity**:
- Clear visual cue for which content is playing.
- Indication if multiple audio sources are active, with quick stop controls.
- **Multitasking Support**:
- Continue playing audio while browsing/exploring other content.
- Resume from where playback left off after switching content.
**Constraints:**
- Maintain HUXE’s existing visual style and branding.
- Prioritize simplicity and clarity for casual listeners.
- Wireframes are acceptable for first-stage concepts.
**What I want from you (AI):**
- Generate at least **3 design concepts** for the in-app persistent audio player and playback controls.
- Include **annotated wireframes** showing layout, hierarchy, and interaction points.
- Suggest **interaction patterns** from top podcast/music apps (e.g., Spotify, Pocket Casts, Apple Podcasts) that could be adapted to HUXE.
- Highlight **pros and cons** of each approach.
Gemini
Gemini’s prompt resembled a formal product requirement doc. It had good structure but lacked creativity. It didn’t explore multiple directions or reference industry standards for UI.
📎 Prompt title:
Persistent Audio Player Indicator
📌
**Feature:** Persistent Audio Player Indicator
**User Story:** As a Huxe user, I want a persistent audio player at the bottom of the screen that shows what is currently playing, its progress, and key controls. This will allow me to easily manage my listening experience without interrupting my exploration of new content.
**Requirements:**
- **Persistent Indicator:** A small, floating player indicator should be visible at all times, regardless of which screen or content I am viewing within the app.
- **Playback Status:** The indicator must clearly show whether audio is currently playing, paused, or stopped.
- **Content Identification:** The indicator should display the name of the content currently being played (e.g., the title of the podcast).
- **Progress Bar:** A progress bar should visually represent how far along the audio has played and how much is remaining.
- **Key Controls:** The indicator should include controls to pause/play the audio.
- **Screen Lock Functionality:** The player controls should also be accessible from the device's lock screen.
- **Interaction:** Tapping the indicator should take the user to a full-screen player view with more detailed information and controls.
Stitch
Stitch performed best in logic flows but didn’t offer prompt-writing support.