Egery Mobile· Section 02 — Exigences métier
Exigences métier
Egery Mobile · 43 BRs validées avec Nelson.
Indispensable 37 exigences
BR-3DSVVA Approuvé
Multi-account types: user, brand, influencer
The platform must support three distinct account types — consumer user, brand, and influencer — each with its own profile model (User core; BrandProfile: companyName, siret, vat, industry, logo; InfluencerProfile: instagramUsername, niche, bio, followerCount), its own onboarding parcours, and conditional navigation and UI per type. A single human may hold multiple linked accounts and switch between them at runtime without re-login.
Objectif Enable the V1 Collaborations marketplace by modelling the three sides of the marketplace (user, brand, influencer) and allowing one person to play multiple roles, supporting Egery's revenue model (15-25% commission on brand-influencer deals).
BR-CATALOG-READ Approuvé
Read-only catalog: search, barcode scan, photo recognition
Search the 2,200+ product catalog by text, scan barcodes via camera, or recognize products from a photo (Google Vision). Read-only — users do not author catalog entries in v1.
Objectif Eliminate manual data entry — the largest abandonment risk for wardrobe apps.
#v1#production#catalog
BR-CT-01 Brouillon
Product reference database
Seeded catalog of fashion products (brand, model, SKU, category, market price) usable for wardrobe entry and value estimation. v1 seed target: 2,200+ items.
Objectif Enable accurate wardrobe valuation and fast scan-to-add via reference data.
#catalog#v1#cdc-3.2.2
BR-CT-02 Brouillon
Product search
User can search the catalog by text (brand, model, keyword) and filter by category/brand.
Objectif Provide a manual-but-fast path to add items when scan/recognition is not available.
#catalog#v1#cdc-3.2.2
BR-CT-03 Brouillon
Photo recognition (Google Vision)
User takes/uploads a photo of a clothing item; system suggests matching catalog references via Google Cloud Vision.
Objectif Eliminate typing friction — the biggest cause of wardrobe-app abandonment.
#catalog#v1#cdc-3.2.2
BR-CT-04 Brouillon
Barcode / EAN scan
Camera barcode scanning resolves to catalog references by EAN/UPC.
Objectif Fastest-possible add-item path for items with scannable tags.
#catalog#v1#cdc-3.2.2
BR-CT-05 Brouillon
Manual product contribution
When an item has no catalog match, user can manually enter brand, model, category, price so it can still be tracked as a wardrobe item.
Objectif Ensure 100% wardrobe coverage regardless of catalog completeness.
#catalog#v1#cdc-3.2.2
BR-CT-06 Brouillon
Current second-hand price per reference
Each catalog reference carries a current market (second-hand) price used as the base for wardrobe-item valuation.
Objectif Base for credible wardrobe valuation (BR-WD-02 depends on this).
#catalog#v1#cdc-3.2.2
BR-DM Approuvé
Direct messaging between any two users
Any authenticated user can DM another user via /dm/. Conversations use a deterministic id so both sides see the same thread. Distinct from collaboration messaging — DM works without an accepted application and is the channel used by marketplace buyers, profile visitors, and follower interactions.
Objectif Allow direct contact between users (buyer↔seller, follower↔influencer) without forcing a collaboration application as a prerequisite.
#v1#shipped#messaging
BR-FRENCH-LOCALE Approuvé
French-language UI throughout
All user-facing strings, product data, and notifications in French. Locale flag = fr.
Objectif Serve French-speaking consumers natively — non-negotiable for the target segment.
#v1#production#locale
BR-ID-01 Brouillon
Social login (Google, Apple)
Users authenticate via Google or Apple OAuth through Firebase Auth. No email/password for v1.
Objectif Reduce onboarding friction to maximize activation rate for fashion-conscious consumers.
#identity#v1#cdc-3.2.1
BR-ID-02 Brouillon
Biometric authentication (Face ID / Touch ID)
Returning users can unlock the app with device biometrics instead of re-authenticating via OAuth.
Objectif Improve daily re-engagement by removing re-login friction.
#identity#v1#cdc-3.2.1
BR-ID-03 Approuvé
Profile management (pseudo, avatar, bio)
User can set and edit a pseudonym, avatar photo, and bio describing their style.
Objectif Give users an identity in the app to support later social/collaboration features.
#identity#v1#cdc-3.2.1
BR-ID-04 Approuvé
Account settings
User can view/edit account settings: language, notification preferences, logout, delete account.
Objectif Meet baseline user-control expectations and GDPR obligations.
#identity#v1#cdc-3.2.1
BR-IDENTITY Approuvé
Social authentication + biometric unlock
Users authenticate via Google or Apple OAuth and unlock the app with Face ID / Touch ID / fingerprint. User profile (username, avatar, bio) editable in-app.
Objectif Frictionless onboarding so consumers reach value (their first wardrobe item) within 60 seconds of install.
#v1#production#identity
BR-INFLUENCER-DISCOVERY Approuvé
Brand-facing influencer directory
Brands access /influencers from the collaborations tab via a “Découvrir des influenceurs” entry point. The directory ranks creators by follower count and supports a free-text query (name, bio, Instagram handle), niche chips, and audience-size buckets (1K+, 10K+, 100K+). Tapping a card opens the public influencer profile.
Objectif Unlock the inverse of the offer→application flow: brands proactively find creators that match their niche and audience size instead of waiting for inbound applications.
#v1#shipped#marketplace#discovery
BR-MARKETPLACE Approuvé
User-to-user resale marketplace
Wardrobe items can be flagged forSale with an asking price. Listings are surfaced on a dedicated /marketplace feed enriched with the seller’s display name and avatar; tapping an item opens its detail view where another user can contact the seller via DM.
Objectif Close the wardrobe lifecycle (acquire → wear → resell) and enable a secondary stream of activity inside the app.
#v1#shipped#marketplace
BR-NOTIFICATIONS Approuvé
Push notifications + in-app notification center
Users receive push notifications (collaboration invites, messages) and review them in an in-app notification center with read/unread state.
Objectif Drive re-engagement and surface time-sensitive collaboration events.
#v1#production#engagement
BR-OF-01 Brouillon
Outfit requires minimum 2 items
An outfit must contain at least 2 wardrobe items.
Objectif Ensure outfits are meaningful compositions, not single-item entries.
#outfit#v1#cdc-3.4
BR-OF-02 Brouillon
Outfits only from user's own wardrobe
Outfits can only include items from the authenticated user’s wardrobe.
Objectif Keep outfit composition tied to real owned items (MVP scope).
#outfit#v1#cdc-3.4
BR-OF-03 Brouillon
Outfit attributes
Outfit carries: title, items, optional photo, computed total value, occasion tag, season, favorite flag.
Objectif Give outfits enough structure to support discovery, recall, and future sharing.
#outfit#v1#cdc-3.2.4
BR-OF-04 Brouillon
Favorites and sharing
User can mark outfits as favorites and share them (link/image export).
Objectif Enable organic growth and daily re-engagement via social sharing.
#outfit#v1#cdc-3.2.4
BR-OUTFITS Approuvé
Outfit composition from owned wardrobe
Users compose outfits combining at least 2 wardrobe items (BR-OF-01). Only the user’s own wardrobe is selectable (BR-OF-02). Optional outfit photo and occasion tag. Total outfit value calculated.
Objectif Deliver the "what to wear" value prop and drive daily app return.
#v1#production#outfits
BR-PUBLIC-PROFILE Approuvé
Public user profile pages
/users/ renders a stable public profile for any user. The payload adapts to accountType: brands expose companyName, industry, website and open-offer count; influencers expose niches (multi-select), Instagram handle and follower count. Every profile carries a 12-outfit portfolio grid linking to outfit detail. The “Gérer les collaborations” CTA is exclusive to the user’s own private profile and never appears on the public view.
Objectif Give every account type a credible public face — brands a portfolio of open offers, influencers a niche/audience showcase, users a wardrobe portfolio — so the marketplace can be vetted before contact.
#v1#shipped#social#public-profile
BR-SOCIAL Approuvé
Likes, saves and follows on the community feed
Authenticated users can like, save and follow on the community feed. State is persisted server-side (Like, Save, Follow collections keyed on userId) and reflected back in the outfit payloads (likeCount, isLikedByViewer, isSavedByViewer) so every screen renders the right state immediately. Self-actions are not allowed (a user cannot follow themselves).
Objectif Turn the outfit feed into a two-way social surface so users return for engagement, not just composition.
#v1#shipped#social
BR-STORE-RELEASE Approuvé
App Store + Play Store production release
App is built, signed, submitted, and approved for both Apple App Store and Google Play Store. Includes screenshots, privacy policy, store listing in French, and crash-free release readiness.
Objectif Without store availability there is no production. Distribution gate.
#v1#production#release
BR-WARDROBE Approuvé
Wardrobe CRUD with photos and condition-based valuation
Users add, view, edit, and delete wardrobe items with at least one photo (BR-WD-04). Estimated value = market price × condition multiplier (BR-WD-02). Sold items excluded from totals (BR-WD-05). Filters by category, brand, season.
Objectif Deliver the core consumer value prop: "know what you own and what it's worth".
#v1#production#wardrobe
BR-WD-01 Brouillon
Wardrobe item linked to catalog reference or manual entry
Every wardrobe item is either linked to a catalog reference or carries user-supplied manual data.
Objectif Guarantee every item can be valued and filtered consistently.
#wardrobe#v1#cdc-3.2.3#cdc-3.4
BR-WD-02 Brouillon
Estimated value from market price × condition multiplier
Estimated value = reference market price × condition multiplier (new_tags 90%, new_no_tags 80%, very_good 60%, good 40%, satisfactory 25%).
Objectif Deliver credible wardrobe valuation that users trust.
#wardrobe#v1#cdc-3.4
BR-WD-03 Brouillon
Accepted condition states
Allowed condition values: new_tags, new_no_tags, very_good, good, satisfactory. No other values permitted.
Objectif Enforce the valuation-multiplier contract (BR-WD-02) across the product.
#wardrobe#v1#cdc-3.4
BR-WD-04 Brouillon
At least one photo required when adding an item
User must attach ≥1 photo when creating a wardrobe item.
Objectif Ensure visual recall for outfit composition and future image-based features.
#wardrobe#v1#cdc-3.4
BR-WD-05 Brouillon
Total wardrobe value excludes sold items
Sold wardrobe items are excluded from total-value calculation but retained for history.
Objectif Report a meaningful current-value figure without losing historical context.
#wardrobe#v1#cdc-3.4
BR-WD-06 Brouillon
Three methods to add a wardrobe item
User can add an item via catalog search, photo/barcode scan, or manual entry.
Objectif Meet users where they are — support the fastest path for each item type.
#wardrobe#v1#cdc-3.2.3
BR-WD-07 Brouillon
Thematic collections
User can group wardrobe items into named thematic collections (e.g. “Summer”, “Work”, “Formal”).
Objectif Help users organize growing wardrobes beyond flat lists.
#wardrobe#v1#cdc-3.2.3
BR-WD-08 Brouillon
Wardrobe filters (category, brand, season)
User can filter their wardrobe by category, brand, and season.
Objectif Make the wardrobe usable at 100+ items without friction.
#wardrobe#v1#cdc-3.2.3
BR-WD-09 Brouillon
Receipt upload
User can attach a purchase receipt (image/PDF) to a wardrobe item for record-keeping.
Objectif Support future insurance/resale use cases and user trust in valuation.
#wardrobe#v1#cdc-3.2.3
BR-WISHLIST Approuvé
Wishlist of catalog products
Users mark catalog products as wished-for from product search or detail screens. Items appear in a dedicated /wishlist page and a heart toggle keeps state in sync across catalog and wishlist views without a refetch.
Objectif Surface intent before purchase so users can return to items they aspire to own and brands can read demand signals.
#v1#shipped#wishlist
Souhaitable 2 exigences
BR-COLLAB-OFFERS Approuvé
Brand/influencer collaboration offers + messaging
Brands publish offers, influencers apply, both parties exchange in-app messages tied to the application. No pricing or commission in v1.1 — just discovery and conversation.
Objectif Establish the two-sided base before introducing money.
#v1.1#next#collaboration
BR-SOCIAL-NOTIFICATIONS Approuvé
Social interaction notifications
Notifications are created server-side on toggleLike, toggleSave and toggleFollow with self-actions excluded. Three new types extend the existing notification enum: outfit_liked, outfit_saved, new_follower. The mobile notification center surfaces them with dedicated icons (Heart, Bookmark, UserPlus) and deep-links each one to the relevant target — outfit detail for likes/saves, public profile for follows. Direct-message notifications also route correctly to /dm/.
Objectif Close the social loop — when a user is liked, saved or followed, they hear about it and come back to the app to see who interacted with their content.
#v1#shipped#notifications#social
Optionnelle 4 exigences
BR-COLLECTION-EDITING Approuvé
Collection image editing surface
Reorder, crop, set primary, delete images within a collection. Journey scan shows this is ~30% of session time — needs deliberate design.
Objectif Highest-time creator activity must feel polished or creators churn.
#v2#later#ux#creator
BR-COMMISSIONED-COLLAB Approuvé
Commissioned collaboration: fixed price + commission %
Brand-influencer collaborations include a fixed fee plus commission split, with date range and confirmation. Foundation for the v2 brokerage revenue stream.
Objectif Activate the brand-side revenue stream and the brokerage-fee revenue stream.
#v2#later#creator#monetization
BR-CREATOR-PRODUCTS Approuvé
Creators author products and collections
Brands and creators publish their own products (title, description, sizes, IG/TikTok import) into collections — extending the currently read-only catalog with creator-authored entries.
Objectif Open the supply side of the marketplace; foundation for monetized collaborations.
#v2#later#creator
BR-MULTI-IMAGE-UPLOAD Approuvé
In-app multi-image upload
Multi-select image picker inside the app — eliminates the 3 macOS Finder context switches observed in the journey scan. Critical UX fix before creator workflow ships.
Objectif Remove the largest UX friction in the creator publishing flow.
#v2#later#ux