Loading case study
Loading case study
Beta
Built an iOS wardrobe platform with authentication, social discovery, marketplace infrastructure, cloud persistence, and production backend services.
RoleFounder / Product Builder / Lead Developer
Woredrobe is an AI-assisted wardrobe and outfit planning application for iOS. The product covers what someone owns, how outfits come together, social discovery, and the structure for a marketplace. The build includes Apple Sign In, a REST API, PostgreSQL, Railway hosting, and a TestFlight build.
Outfit planning is usually split across a closet, a camera roll, and memory. A useful product has to remember what a person owns, help them put outfits together, and still be there the next time they open the app. That means an account, persistent cloud data, and a model that can grow into social discovery and exchange.
I took Woredrobe from concept through a TestFlight build. I owned the product decisions, the Swift iOS client, Apple Sign In, the REST API, PostgreSQL persistence, and deployment of the backend on Railway.
Swift app for wardrobe management, outfit planning, and the social surfaces.
Native sign-in on device, with identity carried through to the API.
Authenticated access to wardrobe records, social discovery, and marketplace data.
Cloud persistence for accounts and product data.
Hosted backend services for the API and database.
Beta distribution of the iOS build.
A wardrobe app that only stores data on the phone is a demo. People need to leave and come back, which means identity and records have to meet.
Discovery and exchange are easy to overbuild before the core loop — owning clothes and planning outfits — actually works.
A simulator walkthrough does not surface signing, backend availability, or real account flows.
I used Apple Sign In on the device and kept the source of truth in PostgreSQL behind the API, so the account and the wardrobe survive beyond one install.
I kept authentication and cloud persistence as the base, and modeled social and marketplace data so those surfaces could grow on the same account system.
I distributed the app through TestFlight and deployed the backend on Railway so the product could be opened as a beta, with a live API behind it.
Beta. The iOS app is distributed through TestFlight, with backend services deployed on Railway. This is not presented as a public App Store launch.