Unique car site idea - need feedback
Discussion
Most people who modify end up changing their car's specs and the overall plan and purpose. For example, I've seen owners of cars go from a supercharger setup to turbocharger or an extreme NA setup to a turbo setup.
As I'm an IT Developer who has just graduated with a good result, and I work in all IT disciplines, and I'm an avid car nut like all on here, I came up with a web application which would allow users to plan the modifications they would make to their car. I always wanted to do something with the 2 things I love. BTW I typed the below in a rush so please excuse any grammar and punctuation errors.
Such a website would allow users to make a wishlist of how they want to mod their car. For example, you choose your car and its options, and then add various aftermarket parts that would mimic how you want to modify your car. The system would be database-driven and store all the mods available for the Z06 (exhausts, headers, cams, etc). This would help anyone who took a bespoks route in modding his or her car. It would be possible to work out the total cost and time required to complete the modifications, by implementing critical path analysis into the system. Furthermore, it wouldn't be hard to work out the results of a modification path and the system can provide details on this, with the use of SQL/programming. This would allow users to experiment with the results before they committed to a plan.
The system would also allow users to manage their money and work out the most ideal modification path based on personal finances and preferences. All this is possible via SQL and some creative ASP/VB.NET programming. For example, if a member says he has kids various mortgages etc than the best way to modify his car would be to spend 10% of his disposable income. The system should only deal with effect demand. It would be good to also store wishlists and trade them with other users and see what the trends are, and the results (dyno charts etc - only facts).
The only problems I see is:
-Keeping up with the rate of change. New products are being added all the time, so the workload of managing the app will be high. Of course, it is possible to let users add products to the database, effecitvely turning the site into a web 2.0 application, but then this will raise the problem of falsifying information. This will mean that the site has to have moderators.
-Product prices constantly change. Different retailers sell products at different prices. There's no web service to allow the prices in the system to automatically change. To tackle this, the system should provide a minimum and maximum estimated price for a part (e.g. exhaust $400-500 or a set deviance) and when a user finally produces his own wishlist, the price of all the parts is added up - both the minimum and maximum estimated price, and the range calculated.
Let me know what you guys think of this idea. Would be a fun project for me to make (only if there is demand for it though!). The constant experience and exposure to the skills involved in such a large project would also always be beneficial to me.
As I'm an IT Developer who has just graduated with a good result, and I work in all IT disciplines, and I'm an avid car nut like all on here, I came up with a web application which would allow users to plan the modifications they would make to their car. I always wanted to do something with the 2 things I love. BTW I typed the below in a rush so please excuse any grammar and punctuation errors.
Such a website would allow users to make a wishlist of how they want to mod their car. For example, you choose your car and its options, and then add various aftermarket parts that would mimic how you want to modify your car. The system would be database-driven and store all the mods available for the Z06 (exhausts, headers, cams, etc). This would help anyone who took a bespoks route in modding his or her car. It would be possible to work out the total cost and time required to complete the modifications, by implementing critical path analysis into the system. Furthermore, it wouldn't be hard to work out the results of a modification path and the system can provide details on this, with the use of SQL/programming. This would allow users to experiment with the results before they committed to a plan.
The system would also allow users to manage their money and work out the most ideal modification path based on personal finances and preferences. All this is possible via SQL and some creative ASP/VB.NET programming. For example, if a member says he has kids various mortgages etc than the best way to modify his car would be to spend 10% of his disposable income. The system should only deal with effect demand. It would be good to also store wishlists and trade them with other users and see what the trends are, and the results (dyno charts etc - only facts).
The only problems I see is:
-Keeping up with the rate of change. New products are being added all the time, so the workload of managing the app will be high. Of course, it is possible to let users add products to the database, effecitvely turning the site into a web 2.0 application, but then this will raise the problem of falsifying information. This will mean that the site has to have moderators.
-Product prices constantly change. Different retailers sell products at different prices. There's no web service to allow the prices in the system to automatically change. To tackle this, the system should provide a minimum and maximum estimated price for a part (e.g. exhaust $400-500 or a set deviance) and when a user finally produces his own wishlist, the price of all the parts is added up - both the minimum and maximum estimated price, and the range calculated.
Let me know what you guys think of this idea. Would be a fun project for me to make (only if there is demand for it though!). The constant experience and exposure to the skills involved in such a large project would also always be beneficial to me.
How would you cater for the difference in labour costs between incremental and big bang work?
How would you ensure that the power increase claims for a particular product were pukka?
How would you cater for longevity/mechanical sympathy of modifications?
Yes the database would be easy to write and it would be simple to achieve in a Assembly/Bill Of Materials type pattern/abstract but there are so many variables that would effect the outcome of the actual work as to render the model of limited viability I'd have thought.
How would you ensure that the power increase claims for a particular product were pukka?
How would you cater for longevity/mechanical sympathy of modifications?
Yes the database would be easy to write and it would be simple to achieve in a Assembly/Bill Of Materials type pattern/abstract but there are so many variables that would effect the outcome of the actual work as to render the model of limited viability I'd have thought.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff


