# Virtual Wardrobe App Design: Capture and Save Outfits Source: https://www.jvds.cn/en/share/ui-design/closetly-wardrobe-capture-filter-outfit-u140 Language: en Published: 2026-10-22 Author: JVDS Design Studio Closetly uses white-gray, soft shadows, and large garment images for a light interface, showing capture, wardrobe browsing, and outfit building in sequence. More interesting than the model alone is the distinction between item and combination. Confirm a garment first, then identify the members of an outfit, giving saving a definite object. ## Key takeaways - Capture locates the garment before result confirmation and retry, keeping entry objects visible. - Clothes organizes by garment type and Collections by occasion, with distinct purposes. - Outfits show model, included items, and candidates; saving should retain traceable members. ## Capture gives results a checking opportunity The first phone shows a brown down jacket on a sofa, with Point the camera at the item near capture. The second outlines it in white; the third enlarges it against a softened background with Try again and Done. Guidance, identification area, and result each have a step before retention. Black Done and pale Try again form primary and secondary actions within a translucent bottom area, without covering the main garment. Edges, color, and completeness still need checking. Cut-off cuffs or background residue should allow returning to an appropriate step without exiting the entire process. The result page does not show name or category entry. A subsequent step could add type, color, or notes for searchable properties. Capture records a reusable object; an attractive cutout is only part of that task. ![Jacket capture, white outline identification, and result confirmation](https://www.jvds.cn/upload/2026/1008/d187-tp/u140-i1.webp) Entry makes the object visible before retry or confirmation determines retention. ## Items and outfits use different categories Closet retains search and Upload above Clothes/Collections. Clothes uses All, Tops, Bottoms, and Shoes for individual images; Collections uses Casual, Work, and Sport for model outfits. Similar grids hold categories already distinguishing two [organizational tasks](https://www.jvds.cn/en/share/website-design/website-taxonomy-categories-tags). Items suit lookup by type, outfits by occasion. JVDS prefers distinct names and explicit return relationships: a combination reveals its members and an item reveals related outfits. The wardrobe then supports movement between owned objects and planned dressing beyond two image walls. Red hearts indicate favorites, with Favorite offering a shared view. Red stands out on gray-white for personal preference. Translucent bottom navigation overlaps lower cards, so scroll endings need enough space to see and select the final row fully. ![Clothes item-type grid and Collections occasion-based outfit grid](https://www.jvds.cn/upload/2026/1008/d187-tp/u140-i2.webp) Changing objects also changes category meaning, forming item and outfit organization layers. ## Specific garments remain beside the model Model centers a full figure with small garment thumbnails near top, trousers, and shoes, each with a red cross. Shoes and candidate cards sit below, with a green check on the third and black Save collection at the bottom. The figure conveys the whole while thumbnails and candidates identify its members. Red crosses suggest removal and green checks selection, which need [separate feedback](https://www.jvds.cn/en/share/ui-design/ui-component-states-design-system). Another shoe should update both the small model-side image and candidate state. This is easier to check than changing only the model, especially with similar choices. Saving should create a combination, not overwrite one garment or the whole wardrobe. Name, occasion, and members can receive short checks around saving, then appear consistently in Collections. The model previews the whole and lists confirm members; synchronization supports later reorganization. ![Outfit model with removable garment thumbnails and a selected shoe candidate](https://www.jvds.cn/upload/2026/1008/d187-tp/u140-i3.webp) Whole preview and member selection stay together, giving saving a definite object. ## Frequently asked questions ### Are favoriting clothes and saving outfits the same? They can be separate. Hearts express preference for an item or combination; saving an outfit records specific members. Names and feedback should identify the level affected. ## Design review checklist - Add garment properties after confirmation and retain an appropriate retry path. - Distinguish item types and outfit occasions with cross-checkable relationships. - Synchronize candidates, members, and model previews; check saving and removal states. ## Connect garment entry with everyday outfit organization If a virtual wardrobe handles capture, categories, and saved combinations, JVDS Design Studio can help with UI/UX design, website design, and development, clarifying items and outfits. Trace one capture and outfit-change process to discuss confirmation, properties, and collection management. [Contact JVDS to discuss your project](https://www.jvds.cn/contact)