โ Back to Linestyle
Linestyle โ Product Concept
Name: Linestyle (earlier candidate: Clothinglinestylist) Author: Josh Zimmerman Date: September 1, 2026 Status: Draft v0.1
1. Concept
An app that lets you photograph yourself and the clothes you own, cataloging every item by type, size, color, manufacturer, and more. From that catalog you can mix and match pieces and virtually try on outfits before you get dressed. The app suggests outfits based on what you already own and the style you're going for. When you're tired of an item, have outgrown it, or simply want to sell it, you can list it for sale directly in the app. Your personal style can be shared on a public profile page.
The app is organized into three sections:
| Section | Visibility | Purpose |
|---|
| Private Wardrobe | Only you | Catalog, try on, plan outfits, get suggestions |
| Public Page | Everyone | Share your style, post looks, build a following |
| Public Store | Everyone | Sell items straight out of your wardrobe |
The key idea: an item is cataloged once and flows through all three sections. The same photo and attributes you capture for try-on are the ones that appear in a posted look and, later, in a for-sale listing. No re-photographing, no re-typing.
2. Problem & Opportunity
The problems
- "I have nothing to wear" โ people forget what they own and rotate through the same 20% of their closet.
- Getting dressed is a daily, repeated decision with no memory of what worked before.
- Closets fill up with items that no longer fit, no longer suit the person, or were never worn.
- Selling clothes today means re-photographing, re-describing, and re-listing on a separate platform โ enough friction that most items just sit.
The opportunity
Existing apps each solve one piece: wardrobe cataloging, resale, or style sharing. None connect them. Cataloging is the expensive part (the user's time), and today that effort is thrown away at resale time. Owning the whole loop โ catalog โ wear โ share โ sell โ buyer's catalog โ is the differentiator.
3. The Three Sections
3.1 Private Wardrobe
Your closet, digitized. Everything here is private by default.
- Body profile โ guided full-body photos (front/side) and optional measurements. Used for try-on and fit suggestions. Never shown publicly. Users who skip photos get a generic mannequin (pick a body type) so try-on works from day one without a personal photo.
- Item catalog โ every garment, shoe, and accessory you own, with photos and attributes.
- Outfit builder โ drag pieces into slots (top, bottom, layer, shoes, accessories) and see them on your body.
- Saved outfits โ favorites, plus a "worn on" log so the app knows what you actually wear.
- Suggestions โ outfits generated from your own items for a chosen style or occasion.
- Closet insights โ most/least worn, cost-per-wear, items you haven't touched in six months (natural candidates for the Store).
3.2 Public Page
Your style, shared.
- Profile: display name, bio, style tags (e.g., minimalist, streetwear, business casual, vintage).
- Looks โ outfits you choose to post, rendered on you or as a flat-lay collage. Each look links to its items; items can be marked "for sale" or "not for sale."
- Followers / following, likes, comments, saves.
- Visitors can save a look for inspiration or jump to the Store if an item in it is listed.
3.3 Public Store
Your resale shop, fed directly from your wardrobe.
- One-tap listing from any wardrobe item โ photos, brand, size, color, and condition are already there. You add a price and a reason (tired of it, outgrown, upgrading, etc.).
- Pricing guidance based on purchase price, condition, age, and comparable sold items.
- Offers, buyer messaging, in-app payments, shipping labels.
- When an item sells it leaves your wardrobe automatically. The buyer can import it into their wardrobe with one tap, attributes intact.
4. Feature Detail
4.1 Capture & Catalog
Cataloging friction is the number-one reason wardrobe apps get abandoned. Target: under 30 seconds per item.
- Capture modes: on-hanger, flat-lay, or on-body.
- Automatic background removal so items look clean and can be layered.
- Auto-suggested attributes from the photo (type, primary color, pattern); user confirms or corrects.
- Barcode / care-tag scan where available to pull brand and size.
- Batch mode: photograph ten items in a row, tag afterward.
Item attributes
| Attribute | Examples |
|---|
| Category / type | Top โ T-shirt, button-down, sweater; Bottom โ jeans, chinos; Outerwear; Shoes; Accessories |
| Size | Numeric, letter, or brand-specific; fit notes (runs small / runs large) |
| Color(s) | Primary and secondary; pattern (solid, stripe, plaid, print) |
| Material | Cotton, wool, denim, leather, synthetic blends |
| Brand / manufacturer | Free text with autocomplete |
| Season | Spring, summer, fall, winter, all-season |
| Formality | Casual, smart casual, business, formal |
| Condition | New with tags, like new, good, worn |
| Purchase info | Date, price, where bought (feeds cost-per-wear and pricing guidance) |
| Care | Machine wash, dry clean, etc. |
| Tags | Free-form (vacation, gym, interview) |
4.2 Try-On & Mix-and-Match
Two rendering tiers, so the app is useful on day one and gets better over time:
- Layered composite (v1) โ cut-out item images layered over your body photo at fixed anchor points. Fast, cheap, works offline, and good enough to judge color and combination.
- AI try-on (later) โ generative try-on that drapes the garment on your body photo realistically. Higher quality, higher cost; offered as a premium feature.
Builder features: slot-based outfit assembly, swap any piece with a swipe, save/favorite, compare two outfits side by side, "wear today" to log it.
4.3 Suggestion Engine
Inputs
- What you own (only items in your wardrobe โ never things you'd have to buy)
- Target style or occasion (chosen per request or set as a default)
- Weather / season
- What you've worn recently (avoid repeats) and what's marked "in the laundry"
- Your own history: outfits you saved, wore, or dismissed
Outputs
- Ranked outfits assembled from your items, with a one-line rationale ("navy + camel for smart casual; you haven't worn these boots in three weeks").
- Gap detection โ "a white sneaker would unlock 14 more outfits from what you own." This is also the natural hook for retail integration later (see ยง8).
Start with rules (color harmony, formality matching, season, silhouette balance). Layer learning on top once there is wear/save/dismiss data.
4.4 Public Page
- Post a look from any saved outfit (renders your try-on image or a flat-lay collage โ your choice).
- Optional face blur / crop for people who want to share style but not identity.
- Style tags make pages discoverable ("browse minimalist," "browse workwear").
- Engagement basics: follow, like, comment, save, report.
4.5 Public Store
- Listing = wardrobe item + price + reason + shipping option.
- Buyer sees the same clean photos and attributes the seller cataloged, which is a better listing than most resale platforms get.
- Offers and counteroffers; seller can auto-accept above a floor price.
- Payments held in escrow until delivery confirmed.
- Prepaid shipping label generated in-app; seller prints or shows a QR code.
- Ratings for buyers and sellers.
- Optional cross-posting to external marketplaces in a later phase.
5. Core User Flows
Onboarding Create account โ take body photos (guided, with skip option) โ add first 5 items (guided batch capture) โ see first generated outfit. Goal: a "wow" moment within five minutes.
Add an item Camera โ auto background removal โ confirm auto-tagged type and color โ add size, brand, condition โ save. Batch mode defers tagging until after all photos are taken.
Get dressed (daily flow) Open app โ pick occasion or accept default โ see 3โ5 suggested outfits on your body โ swap pieces if desired โ tap "wear today." The app logs it and adjusts future suggestions.
Post a look Saved outfit โ "Post" โ choose render style and caption โ tag items as for-sale / not-for-sale โ publish to Public Page.
Sell an item Wardrobe item (or Store nudge: "not worn in 6 months") โ "List for sale" โ set price (with guidance) โ pick reason โ publish. On sale: payment, label, ship, item removed from wardrobe, buyer offered one-tap import.
6. Data Model (high level)
| Entity | Key fields |
|---|
| User | id, handle, display name, bio, style tags, settings |
| BodyProfile | user id, photos (front/side), measurements, anchor points for layering |
| Item | id, owner id, photos (original + cutout), category, subtype, size, colors, pattern, material, brand, season, formality, condition, purchase date/price, care, tags, status (active / listed / sold / archived) |
| Outfit | id, owner id, name, item slots, render image, favorite flag |
| WearLog | outfit id, date, occasion, weather |
| Look | id, owner id, outfit id, caption, render, visibility, engagement counts |
| Listing | id, item id, price, reason, condition, shipping option, status |
| Order | listing id, buyer id, payment status, shipping status, tracking |
| Follow | follower id, followee id |
Item status is what ties the three sections together: active lives in the wardrobe, listed appears in the Store while staying in the wardrobe, sold transfers to the buyer.
7. Technical Approach
- Platform: iOS first, Android second. Camera-centric. A lightweight web view for public pages and store listings so links can be shared outside the app.
- Image pipeline: capture โ background removal โ normalization โ thumbnail + full-res storage. Background removal can run on-device (Apple's Vision framework supports subject lifting: https://developer.apple.com/documentation/vision) or server-side with an open-source model such as rembg (https://github.com/danielgadd/rembg).
- Try-on: tier 1 is pure layering on the client. Tier 2 uses a generative try-on model โ open-source options such as IDM-VTON (https://github.com/yisol/IDM-VTON) exist, and hosted try-on APIs are emerging; evaluate current options at build time since this space moves quickly.
- Auto-tagging: a vision model classifies category, color, and pattern from the cutout image; user confirmation feeds back as training data.
- Suggestions: rules engine first, ranking model later, driven by wear/save/dismiss signals.
- Payments: Stripe Connect (https://stripe.com/connect) for marketplace payouts and escrow-style holds.
- Shipping: label generation via Shippo (https://goshippo.com) or EasyPost (https://www.easypost.com).
- Privacy & safety: body photos are the most sensitive asset in the app. Encrypt at rest, never use them for anything public without an explicit post action, process on-device where feasible, and make deletion complete and immediate. Public content needs reporting and moderation tooling from day one.
8. Monetization
| Stream | Notes |
|---|
| Free tier | Wardrobe up to N items, layered try-on, basic suggestions, public page |
| Premium subscription | Unlimited items, AI try-on, advanced suggestions and insights, closet analytics |
| Marketplace fee | Percentage of each sale, plus payment processing |
| Retail integration (later) | Gap detection can surface items from partner retailers โ e.g., connecting to stores such as Anthropologie (https://www.anthropologie.com) or Free People (https://www.freepeople.com) so a user can try a suggested piece on their own body photo before buying. Affiliate or partner revenue. |
9. MVP Scope & Phasing
Phase 1 โ Private Wardrobe (MVP) Body profile, item capture with background removal and auto-tagging, full attribute set, layered outfit builder, rule-based suggestions, wear log. Success metric: users add 20+ items and return three or more mornings a week.
Phase 2 โ Public Page Profiles, posting looks, follow/like/save, style-tag discovery, moderation basics.
Phase 3 โ Public Store One-tap listings, pricing guidance, payments, shipping, ratings, buyer import.
Phase 4 โ Intelligence & Retail AI try-on, learned suggestions, gap detection with retail partners, cross-posting to external marketplaces.
10. Comparable Apps
Each covers one piece of the loop; none covers all three sections. (Feature sets change โ verify before using this externally.)
Positioning: the only app where cataloging your closet once gives you a stylist, a style page, and a storefront.
11. Risks & Open Questions
- Cataloging friction โ if adding items feels like a chore, nothing else matters. Batch capture and auto-tagging are not optional.
- Try-on expectations โ users may expect photorealism from day one. Set expectations clearly for tier 1; ship tier 2 only when quality is convincing.
- Marketplace trust โ decided: funds are held in escrow until delivery is confirmed; all disputes must be opened within that hold window. Counterfeit and return policy still to be written.
- Body image sensitivity โ decided: body photos are optional; a generic mannequin is the fallback. Tone and privacy defaults still need care.
- Cold start on the social side โ public pages are only interesting with content. Consider seeding with curated looks or launching Phase 2 to an invite group.
12. Decisions Log
| Date | Decision |
|---|
| 2026-09-02 | Name: Linestyle |
| 2026-09-04 | Platform: iOS first, then Android |
| 2026-09-04 | Marketplace: build in-house (payments + shipping), not cross-post to other platforms |
| 2026-09-04 | Trust: escrow hold until delivery confirmed; disputes must be raised inside the hold window |
| 2026-09-04 | Try-on: body photos optional; generic mannequin as fallback |
โ Back to Linestyle