Wardrobe Manager
May 25, 2013

The base idea of this application is to give the end-user an application where they can create a wardrobe outfit based on one of more items and then the application can show them items that match via color, style, tag, etc.

This would need to be a phone based application, although there could be a value for tablet, laptop and desktop could be of value as well.

Voice recognition will be important to make the process of accessing the data. Allowing the user to speak the name, style, etc of an item could make data entry easy enough. Image recognition will also be helpful for determine color and texture. A combination of these features could get an acceptable result until RFID gets into the mainstream.

A big concern would be ability to add your wardrobe into your local database. Users would not want to type anything into their phone or other device. The preferred method would be to have RFID tags implemented into clothes by the manufacturer and of course phones would then have to RFID readers. This technology is coming along and details of one example can be found here: http://www.electronics-eetimes.com

Another option, using the current technology within most cells phones would be to scan standard bar codes or QR codes. Again this would mean that data would have to be shared from the manufacturer.

Many apps charge, of course, and then there are many applications that are free and have found other forms to make money, often with advertising. One of the benefits, for the end user, would be that this application would pay the user for using it. The more frequently the user enters their daily wardrobe the more "points" the user would earn that would then give them discounts to attire from various participating vendors/manufacturers.

The usual connections to Facebook, Twitter, etc could be included; "Look what I am wearing today" and these sort of social connections could be used to earn additional "points"

To attempt to alleviate fears of Big Brother during the installation all options should be "Opt In". The user should see a dialog that informs them of their options and the benefits. These options should be able to be changed at a later date. One option would be to show the user their ID so that they can see exactly what data is being transmitted and that data should move from device to device in an encrypted form so only those who pay for the data can have access to it.

Application funding.
The application will be paid for by manufacturer and retail establishment purchasing users detail data. A standard GUID will identity the user so the user's personal information is not identify them directly. This info would include, but not limited to; age, (range?) height, weight, favorite outfits, tags, frequency, brands owned, worn, location where the outfit is purchased and worn (City and State via the phone's GPS. The exact address would not be shared to vendors)

Benefits for the user

Benefits for the manufacturer

This application would require a very large buy-in from clothing manufacturers and retails, who user their own metrics and have systems that they may be reluctant to allow access. (in the case of getting new data) This becomes a realm of sales and marketing. I only state this here to show that I am fully aware of the details necessary for this project to succeed.

The point of this entry is to show that I can take an idea, in this case presented to me by my wife, and carry it forward to include additional details that can benefit the user as well as the host company. I worked briefly at Coach and saw how much they used their own internal data based only on sales.