wearwise

Inspiration

I wanted a better way to understand my wardrobe: what I own, how I can wear it, and whether a new purchase would work with the clothes I already have. I also wanted to keep practical details, such as my usual size in a brand, alongside visual inspiration.

Wearwise brings those needs together. It connects a visual wardrobe, outfit collages, daily wearing records, and cost-per-wear estimates so that buying decisions can start with what is already in the closet.

How I built it

I built Wearwise as a native iOS app using SwiftUI for the interface and SwiftData for local storage. Apple’s Vision framework removes garment backgrounds, and users can review the results, adjust suggested colors, and enter item details before saving.

The app has four main destinations: Wardrobe, Shopping, Journal, and Brands. Users can arrange clothes into outfit collages, add a customizable character, and record what they wore in Journal. Shopping keeps potential purchases and website prices separate from owned clothes, while Brands stores sizing notes, material preferences, and inspiration photos.

I separated calculations and composition data into a Swift package so that they could be tested independently of the interface. Saved journal entries retain their own snapshots, allowing users to change an outfit later without changing an earlier record.

I used Codex to help implement and refine the project, while I defined the requirements, reviewed the designs, tested the app, and directed revisions.

What I learned

I learned how much work sits between a feature idea and a usable interaction. Supporting sticker resizing, for example, requires clear selection behavior, reliable gesture recognition, sensible touch targets, and undo support.

I also learned to distinguish what a calculation test, a simulator test, and a physical-device test can establish. Image processing and system photo permissions needed particular attention on the iPhone.

Working through scope, product requirements, implementation, and repeated reviews helped me understand how decisions in one part of an app affect the rest.

Challenges I faced

The collage editor was one of the hardest parts. Moving, pinching, rotating, and resizing had to affect only the selected layer, while artwork stayed within the canvas and each completed action remained undoable.

The character system presented a different challenge. Hairstyles needed to fit different face shapes without shrinking the face or exposing gaps. I refined the artwork, separated front and rear hair layers, and adjusted how the parts connect.

Performance and data preservation also mattered. I moved expensive character preview work away from the main interface and added bounded caches. For saved outfits and journals, I preserved image versions and snapshots so that later edits would not unexpectedly change earlier records.