Helena Fernández
Miralpeix
Projects
About
Product Design
UX/UI
Information Architecture
Wireflows
Interface System
Speculative Product Strategy
Speculative voice-first product concept · 2025
Helena Fernández
Miralpeix
Product Designer
UX/UI Designer
Brand Strategy
Hexacore is a speculative voice-first product concept for hands-free robotic support in extreme environments.
The case explores how users could request help, confirm urgency and receive Hexabot support when gloves, low visibility and limited attention make traditional interfaces harder to use.
Overview
What the product is about
Hexacore is a speculative voice-first assistant for requesting, confirming and coordinating robotic support.
The product focuses on operational UX: short requests, clear confirmations, task status and context-aware support.
The goal was a credible interaction model where users can ask for help by voice and receive the right robotic support for their context.
A voice-first assistant for requesting robotic support, confirming urgency and activating Hexabots hands-free.
I led interaction design, voice UI, UX strategy, system logic and visual direction.
Context definition:
Defined the colony setting, users, tasks and environmental constraints.
Product logic:
Structured use cases around spoken needs, context interpretation, confirmation and Hexabot activation.
UX/UI system:
Designed modular flows and hierarchy for critical information.
Visual direction:
Built a lunar, precise and usable interface language.
A speculative voice-first product concept focused on hands-free robotic support, mission tasks and adaptive assistance.
Context-aware assistance, task logic, confirmation flows and interface hierarchy.
I led concept, product strategy, UX/UI and visual direction.
Context
Phase 1.1 · A product system for pioneers on the Moon
Hexacore supports lunar pioneers coordinating maintenance, exploration, logistics and safety tasks through a fleet of Hexabots.
The interface had to prioritise fast reading, quick action and clear task understanding under pressure.
The product turns extreme-context constraints into voice-first interaction, confirmation flows and operational status feedback.
Design problem
Phase 1.2 · Making critical operations readable under pressure
The design problem was supporting robotic operations when users cannot rely on precise touch, full visibility or sustained attention.
Critical support needed to be requested and confirmed quickly, especially when a user is moving, wearing gloves or facing risk.
Lunar dust, helmet glass, darkness and external glare require strong contrast, large modules and instant hierarchy.
Touch targets need to be generous, simple and forgiving because precision interaction is harder in protective equipment.
Users need to understand robot status, task urgency, risk level and progress without reading dense information.
The interface must reduce cognitive load when users are making decisions in constrained and potentially dangerous conditions.
Key product decisions
Designing for extreme-context UX
Hexacore translates an extreme-context scenario into a practical assistant experience built around clarity, confirmation and low-friction task support.
The project focuses on operational UX for environments where touch, visibility and attention may be limited.
The case turns a speculative context into an operational UX problem: reducing interaction cost, clarifying critical decisions and designing feedback loops that can support users under pressure.
Product objective
Phase 2.1 · Request, recommend and react with clarity
The objective was to help pioneers request support, receive the right Hexabot recommendation, confirm action and follow progress.
Hexacore connects voice interaction, context awareness, UX and visual direction into one operational product language.
Users and needs
Phase 2.2 · Designing for mission-focused operators
The main users are lunar pioneers working across exploration, engineering, maintenance and logistics.
Their needs shaped short decision loops: express a need, understand urgency, confirm support and stay updated.
Two profiles guided the application: technical lunar operators and colony administrators.
Engineers, explorers and maintenance operators making decisions under pressure while moving through low-visibility, equipment-heavy environments.
They need Hexacore to reduce friction during urgent tasks: identifying the problem, requesting the right Hexabot, confirming the action and following status without interrupting fieldwork.
For this group, the interface had to prioritise speed, hierarchy and operational confidence over exploration or decorative interaction.
Colony users assigning support tasks, checking routines and coordinating Hexabots from shared spaces, agricultural areas and domestic maintenance contexts.
Their interaction is less technical, but still time-sensitive: the system has to make robotic support understandable, accessible and easy to confirm without forcing users into complex controls.
For this group, Hexacore needed clearer language, guided actions and smart alerts that surface only the information required for the next decision.
Engineer & lunar explorer
Needs a responsive interface for mission-critical decisions, task assignment and fast Hexabot status checks.
Must access robot availability, risk level and progress quickly, even with low visibility or limited dexterity.
Voice command compatibility supports control when gloves, suits or equipment make touch interaction slower.
Instant alerts and progress changes keep him informed without constant manual checks across the colony.
Greenhouse administrator
Needs to manage Hexabot routines efficiently while moving between greenhouse systems and colony duties.
Requires structured information that stays readable in harsh environments, glare and emergency conditions.
Can operate robots, confirm tasks and trigger support actions without removing gloves or leaving the work area.
Smart alerts surface essential updates only, avoiding unnecessary notifications during critical routines.
MVP Experience
Phase 3.1 · A hands-free intelligent assistant for every context
The MVP turns spoken needs into Hexabot actions, status updates and clear operational feedback.
The validation focus is a short task loop: identify intent, recommend the right action, confirm and keep users updated without adding cognitive load.
Users trigger support without stopping their task, removing gloves or navigating a dense control panel.
I designed the first interaction as a short spoken request, so the system can capture intent while the user stays focused on the physical task.
The voice layer works as an operational shortcut: ask for help, clarify urgency, receive a recommendation and confirm the next action.
Screens adapt by task type, risk level, available Hexabots and required confirmation.
I structured the MVP around decision paths for repair, transport, greenhouse support, exploration and emergency response.
The interface reveals only the information required at each step: status, location, urgency and progress.
User flow map connecting the core service paths: home, tasks, project files, planner, assistant, messages and Hexabot management. The system shows how a request moves from voice input to task coordination and fleet control.
MVP flows
Phase 3.2 · From voice request to Hexabot action
I defined the MVP flows around a short digital service path: request, interpretation, recommendation, confirmation and status feedback.
Each flow reveals only the controls needed for the current need, while voice keeps the interaction usable with gloves and low visibility.
The sequence: express need, receive recommendation, confirm action and track progress.
Early wireframes mapping Hexacore's operational logic: from spoken request and context reading to Hexabot recommendation, confirmation and progress feedback.
UX/UI decisions
Phase 4.1 · Designing for extreme use conditions
The UX/UI direction is based on legibility, modular composition, status hierarchy and large interaction targets.
Voice prompts, task cards, status chips, alert levels and progress feedback create a scalable assistant system.
Alerts, task status and robot condition appear before secondary descriptive information.
Big touch areas and clear spacing support use with gloves and reduce interaction errors.
Strong contrast, short labels and visual grouping help users understand the system quickly.
The interface avoids visual noise so urgent states can stand out without overwhelming the operator.
Operational interface system
Phase 4.2 · Turning interface elements into task support
The interface system connects voice prompts, task cards, Hexabot status, alerts and progress feedback into one operational layer.
I used modular components and high-contrast hierarchy to make the assistant readable in low-light conditions, without making the product feel like a decorative sci-fi dashboard.
The product needed a system that could scale across requests, recommendations, project files, messages and Hexabot management while keeping every screen focused on the next action.
I designed the interface around a shared logic for requests, tasks, Hexabots and updates, so every screen feels part of the same operational system.
The model helps users understand what is happening, what needs attention and which action should come next without reading every detail.
Cards, status chips, alerts and progress states can expand across new Hexabot types, task categories and colony routines.
The system keeps technical information visible, but organizes it into clear layers so the assistant feels usable under pressure.
Final result
A scalable assistant system for lunar operations
The result is a structured, readable and believable assistant for coordinating Hexabot support in extreme conditions.
The case translates a science-fiction universe into practical UX decisions and a coherent interface system.
Highlights
What this project shows
Hexacore shows how an extreme-context scenario can become a practical assistant experience built around clarity, confirmation and low-friction task support.
The project focuses on operational UX for environments where touch, visibility and attention may be limited, connecting voice-first logic, confirmation flows and readable status feedback.
"Hexacore shows how complex robotic support can become clearer through voice-first UX, confirmation flows and operational interface logic."