Case Study · Human-Centered Product Design
How Do You Make an Intimate Product Feel as Casual as Earbuds?
Turning an intimate human need into a considered physical-product experience through industrial design, human factors and engineering.
Every fact in this case study is drawn from the project team's own documentation and the official Gizmospring project record — nothing is inferred from the imagery alone.
Fig. 01 · MYPOD · authentic project photographyProject record
- Year
- 2019
- Designed by
- Gizmospring — ODM design
- Client
- CalExotics · Ontario, California
- Team
- Kenny Tai · Anson Lee · Esme Lo · Ben Yang
- Services
- Industrial Design · Engineering Design · Mass Production · Logistics
- Documentation
- Behance study library · published July 2021
This case study is reconstructed from two verified sources: the project team's own Behance documentation — including their written explanations of the idea, shape, function and prototyping phases — and the official Gizmospring project record. No functionality, mechanism or result is inferred from imagery alone.
Fig. 02 · original 2019 project plate01 / User insight
The Product's Real Context Wasn't the Moment of Use. It Was Every Moment Around It.
The team's insight, in their own words: if the object borrows the size and feel of gear people already carry without thinking, the stigma never enters the room.
"MYPOD is the same size as a portable charger case. It has the same feel. It is small, portable, and easy to keep away from people. This makes it a great choice for a discreet lifestyle. It doesn't look like a toy, but it is a fun product to own."
01
Easy to carry
The same size and the same feel as a portable charger case — an object that already belongs in a pocket.
02
Discreet
It doesn't look like a toy. It reads as an everyday consumer electronic, so it never has to be explained.
03
Safe & clean
Hygiene is designed into the case — sanitization happens where the product is stored, not as a separate chore.
Principles as written by the project team · verified
02 / The design question
Can an Intimate Product Borrow the Language of Everyday Electronics — and Still Take Its Own Ritual Seriously?
The documented brief asked for a product that is discreet, portable and intuitive, integrating into daily routines — with hygiene via UV sanitization, elegant simplicity and effortless usability as the focus. Translated into a design question, that becomes a single tension: make the object disappear into daily life, while giving it a hygiene and charging ritual ordinary accessories don't have.
The requirements the answer had to satisfy
The form had to be borrowed from products nobody questions — the behavior had to be entirely its own.
03 / Development needs
Intimate Products Still Have to Solve Ordinary Product Problems.
The needs below are the ones the team actually identified and worked against — each traceable to their own documentation. An intimate product doesn't get an exemption from any of them; it just gets discussed less openly.
01
Ergonomics
Does it work naturally with the human body?
The team's documented answer was control simplicity: one button cycling multiple modes, with no learning curve between picking it up and using it. The carry form was matched to a hand and pocket that already hold a portable charger case.
Documented · IDEA · FUNCTION panels
02
Discretion
Does the product feel appropriate to own, store and live with?
Confirmed as the project's organizing need: it "doesn't look like a toy, but it is a fun product to own," reads as an everyday consumer electronic, and is "easy to keep away from people" — designed for what the team called a discreet lifestyle.
Documented · IDEA panel · project record
03
Cleaning
What happens after use?
Hygiene was engineered into the storage behavior itself: the team decided to build UVC light into the case "for a better user experience," and validated it with mock-ups carrying live electronics to test the sanitizer's efficiency.
Documented · IDEA · MOCK-UP panels
04
Storage
How does the product exist when it isn't being used?
The case is where the product lives: stored, charged and protected inside one pocket-scale object that reads as an accessory. Magnetic attachment keeps the device seated so storage, charging and sanitization are a single action.
Documented · FUNCTION panel · engineering annotations
05
Mechanical performance
How does the mechanism deliver the intended experience?
Documented end to end: a single button cycling multiple modes; USB charging with a breathing battery-status light; the metal band doubling as a charging electrode; magnetic retention in the case. Each behavior was specified in the team's function documentation.
Documented · FUNCTION panel · team annotations
Materials — how the product feels against the body — withheld: no material decision is documented in the surviving record
Good product design doesn't treat intimate products as exceptions. It applies the same rigor to experiences people simply discuss less openly.
04 / Exploration
The Form Was Solved by Products Nobody Second-Guesses.
In the team's words: "We take some simple consuming electronic device for reference to develop shape and details." The exploration wasn't a search for a striking silhouette — it was a search for the everyday silhouette.
Fig. 03 · Shape + function documentation · team studyReference, not imagination
The team took simple consumer electronic devices — earbud cases, capsules, everyday shells — as the reference for shape and details, so the form would feel familiar rather than novel.
Sketch the interactions
Form studies ran alongside interaction studies: how the lid opens, how the device seats magnetically, and where the internal light lives.
Decide function early
The defining exploration decision was functional: build UVC light inside the case to sanitize the device — hygiene as part of the object, not an accessory to it.
05 / Concept directions
Every Shape Was Testing a Different Answer.
The team's study plate is not a moodboard. Each direction on it was a test with a question attached — and the project moved forward on what each test taught, not on which sketch looked best.
Fig. 03 · revisited · concept studies, annotated belowThe familiar-object direction
What was this trying to solve?
What silhouette gets carried in public without a second glance?
What did we learn?
The team studied the language of everyday personal electronics — objects nobody looks at twice — as the reference grid for the entire form.
What moved forward?
The everyday-object scale carried into the final: a charger-case silhouette meant to be carried, not displayed.
What was rejected?
Pending team account — the record does not document which reference languages were set aside.
The docking direction
What was this trying to solve?
How does the device seat itself — every single time?
What did we learn?
The interaction studies converged on magnetic attachment: the dock guides itself, so storage happens without guidance.
What moved forward?
Magnetic retention moved into the final architecture — seating the device is the same act as storing and charging it.
What was rejected?
Pending team account — alternative retention concepts are not documented.
The built-in hygiene direction
What was this trying to solve?
Where does sanitization live so it happens without being asked?
What did we learn?
UVC belongs inside the case: closing the lid is the cleaning act — hygiene became part of putting the product away, not a separate chore.
What moved forward?
The in-case UVC chamber moved into the final architecture, active behind the closed lid.
What was rejected?
Pending team account — external cleaning concepts are not documented.
The dimension-and-shape loop
What was this trying to solve?
What dimensions will a hand and a pocket actually accept?
What did we learn?
“We made mock-up to find a better dimension and shape” — physical mock-ups, not sketches, settled the proportions the body has to accept.
What moved forward?
The mock-up-proven dimension and shape moved into the final product.
What was rejected?
Pending team account — the specific proportions set aside are not documented.
How the field narrowed — documented moves only
Four study directions
Familiar object · Docking · Built-in hygiene · Dimension & shape
Verified moves
Everyday scale · Magnetic seat · In-case UVC · Mock-up proportions
Final architecture
Device + case — the band is the electrode, the case is the sanitizer (Fig. 04)
Ideation creates value when every concept teaches you something.
06 / Product architecture
Two Parts, One System — and a Detail That Does Two Jobs.
MYPOD resolves into a device and a case. The device carries the interaction; the case carries storage, sanitization and charging in one closed pill the size of a portable charger case.
The device
A single-button, pocket-scale device. Its defining detail is the metal band at its middle — in the team's annotation, it is "used as decoration as well as charging electrode": the visible styling line is the charging contact. Nothing on the product does only one job.
The case
The case is the product's second half of behavior: it stores the device in a form that reads as an everyday accessory, sanitizes it with built-in UVC light, and charges it over USB — all with the lid closed.
Fig. 04 · Device anatomy · team annotationGood architecture hides its complexity in details that look like styling.
07 / Human factors
The Whole Interface Is One Button.
Human factors for a discreet product means removing every moment of visible operation: one control, a familiar carry scale, and a hygiene ritual folded into storage.
Fig. 05 · In the hand · authentic project photographyOne button, no learning
A single press cycles through the device's modes. No display, no menus, no manual — the entire interface is one control the thumb finds without looking.
Carry scale, by reference
Sized to the portable charger case — an object hands already know how to pocket, hold and pass across a table without a second thought.
A ritual, not a chore
Cleaning lives inside the storage behavior: close the lid and the case sanitizes the device where it is kept. Hygiene happens by putting the product away.
08 / Form & the body
Start With the Body, Not the Object.
MYPOD's geometry wasn't drawn and then checked against people. The documented studies start from the hand, the pocket and the docking moment — and the form is what those requirements left behind.
01
Body interaction
Carried at the scale of a charger case a hand already knows, operated by one button the thumb finds without looking, and cleaned by the act of putting it away.
Verified
02
Contact geometry
The documented contact surfaces are device-to-case: the metal band meeting the case's charging contact, and magnetic retention seating the device. The device's contact geometry against the body in use is not documented.
Partial · body contact pending
03
Product form
"We made mock-up to find a better dimension and shape" — the silhouette was solved against hand and pocket, borrowed from everyday electronics so it would be carried, not displayed.
Verified
04
Mechanical architecture
The geometry carries the function: the visible metal band is the charging electrode, the UVC source lives inside the case, and the lid-closed pill charges over USB with a breathing status light.
Verified
Fig. 03 · revisited · interaction studiesFig. 05 · revisited · in the handThe lid study
What should the opening gesture be?
The team sketched how the case opens — the entry moment had to behave like an everyday object, because the product's first impression is where discretion is won or lost.
The seating study
How does the device dock — every time?
Interaction studies worked out magnetic attachment: the device must seat itself in the case without guidance, so storage, charging and sanitization happen as one closing action.
The light study
Where does the sanitizing source live?
The team placed the internal UVC light during the form studies — hygiene had to be built into the case's geometry, not added to it as an accessory.
The dimension study
What size does a pocket actually accept?
Mock-ups were built to find a better dimension and shape — the form was measured against the hand and the pocket, not against a sketchbook aesthetic.
Studies as documented in the team's SHAPE panel · shown for the problems they solved, not as aesthetic exploration
When a product interacts directly with the body, form isn't styling. It's function.
09 / Experience architecture
The Experience Had to Become an Architecture.
Every intended experience in this study resolves into a physical system: a need became a requirement, the requirement met a constraint, and the constraint was answered by a documented mechanism — never by a feature list.
Fig. 04 · revisited · device anatomy, team annotation01Hygiene without a chore
User need
Cleaning it should happen by itself — not as a second ritual after the ritual.
Physical requirement
Sanitization had to live inside the product and be triggered by the act of putting it away.
Engineering constraint
The sanitizing source had to be built into the case, working behind the closed lid where the user never handles it.
Product solution
A UVC source inside the case, active when the lid closes — documented in the team's chamber photography (Fig. 06).
02Docking is the whole job
User need
Putting it away should be the only action — storage, seating and charging as one gesture.
Physical requirement
The device had to seat itself and carry current every time, without guidance.
Engineering constraint
Seating and current had to be solved by the same geometry — no separate charging step, no precise alignment ritual.
Product solution
Magnetic retention seats the device; the visible metal band doubles as the charging electrode (Fig. 04, Fig. 08).
03State at a glance
User need
Is it charging — without opening the case?
Physical requirement
The case had to report its own state from the outside.
Engineering constraint
Signaling had to read at a distance and in passing, not demand inspection.
Product solution
A breathing status light during USB charging — documented by the team (Fig. 07).
04Eyes-free control
User need
Operate it without looking at it.
Physical requirement
The entire behavior of the product behind a single control.
Engineering constraint
Every function — none documented beyond the essentials — had to be reachable without a screen, a menu or a manual.
Product solution
The one-button interface: the whole control surface is one control the thumb finds on its own (Fig. 05).
Mechanisms and components as confirmed by the project team's own documentation · nothing reverse-engineered from the imagery
A product concept becomes real when an experience can be translated into mechanisms, materials and manufacturable parts.
10 / Engineering
Three Engineering Decisions, Each Explained by the Team.
Sanitization, charging and retention — the three behaviors that make the case more than a box. Each is documented in the team's own words, with their own engineering studies.
Fig. 06 · UVC sanitizing chamber · project documentationDecision 01
Sanitization, built in
"And for a better user experience, we decided to build UVC light inside the case to sanitize the vibrator."
Hygiene was engineered into the storage behavior itself — the case is the sanitizer, so cleaning happens by putting the product away.
Verified · team documentation
Fig. 07 · USB charging + battery status · project documentationDecision 02
Charging, made visible
"When the charger is connected by USB, the breathing light on the outside of case flashes and show the status of battery."
A breathing light reports battery status from the outside of the closed case — the product keeps its state legible without ever being opened in public.
Verified · team documentation
Fig. 08 · Magnetic retention · project documentationDecision 03
Retention, without latching
"For vibrator to better fix case inside and prevent from dropping out, the vibrator is attached by magnet."
Magnetic attachment seats the device in the case with no latch to operate and no mechanism to wear out — it holds by default.
Verified · team documentation
Every mechanism serves the same brief: nothing about the product should ask to be noticed.
11 / Prototyping
The Prototype Had to Prove the Sanitizer, Not Just the Shape.
MYPOD's mock-ups carried real electronic components — the form was validated by hand, and the sanitizing function was validated live.
The team's account
"To make the concept more realizable and best for use, not only did we make mock-up to find a better dimension and shape, we also put electronic components inside it to test the efficiency of sanitizer."
Two validations in one prototype loop: the dimension and shape were tested as physical form, and the sanitizer's efficiency was tested with its electronics running inside the mock-up — the claim was measured before the product existed.
Verified · team documentation
Fig. 09 · Mock-up studies · team documentationA prototype that only looks right proves the wrong thing.
12 / Material & touch
When Touch Is Part of the Function, Material Becomes Engineering.
MYPOD is touched, docked, carried and sanitized — so its materials are not finishes, they are working parts of the experience. The public record documents one material decision in full; the rest of this chapter is held open for the team's account rather than inferred.
The documented decision · the band
The surface that carries the brand also carries current.
The one material choice the record documents in full is also the product's central engineering act: the metallic band that defines MYPOD's look is the charging electrode. The trade-off was resolved in the material itself — an appearance detail was made into an electrical path, so styling and function could not drift apart.
The CMF range the team documented — light, black and wine colorways, each carrying the metallic band (Figs. 10–12) — shows the finish palette. The material reasoning beneath it is not documented.
Fig. 04 · revisited · the band, team annotationFig. 09 · revisited · mock-up studiesWhat the prototypes settled — and what they don't record
The mock-ups settled geometry. The material story stayed in the studio.
"We made mock-up to find a better dimension and shape" — the physical loop the team documents answers size and proportion. It does not record what the mock-ups were made of, how they felt, or which material candidates were ruled out in hand. Those decisions belong to the project team's account, not to this page.
Open material questions — pending team account
Silicone
Did a soft polymer carry any of the contact surfaces?
Pending team account
Softness
How much give did the touched surfaces have?
Pending team account
Hardness
Where was rigidity required against yielding contact?
Pending team account
Flexibility
Which parts were allowed to move, and how far?
Pending team account
Friction
How did the product stay planted in hand and pocket?
Pending team account
Texture
What did the surfaces communicate at first touch?
Pending team account
Cleanability
The case sanitizes the device — but what keeps the touched surfaces themselves clean?
Pending team account
Overmolding
Was a soft layer molded over a rigid core?
Pending team account
Structural materials
What material carries the docking and closing loads?
Pending team account
Surface finishes
How was each finish chosen against touch and cleaning?
Pending team account
The right material isn't the one that feels best in isolation. It's the one that makes the entire product experience work.
13 / Outcome
What the Record Documents, the Record Publishes.
The outcome is stated only as far as the documentation goes: the finished two-part system, three studied colorways, and an end-to-end delivery for CalExotics — industrial design through logistics. No market results are claimed beyond the record.
Discreet form factor — pocket-sized, blending into daily carry
UVC sanitizing case — hygiene built in after each use
Single-button interface — seamless cycling through modes
Everyday normalization — as casual as tech accessories
Verified · official Gizmospring project record
Documented colorway studies
Fig. 10 · Light colorway
Fig. 11 · Black colorway
Fig. 12 · Wine colorwayDelivered end-to-end for CalExotics
"It doesn't look like a toy, but it is a fun product to own."
14 / What this project demonstrates
MYPOD turned an intimate and highly personal user need into a thoughtful physical-product experience — designed, engineered, validated and delivered end-to-end by one team.
Verified against the project's own documentation
Have a product whose real problem is bigger than its feature list? That's where we start.
Start a conversation