- 84 months ago
This is a useful idea in a couple of different ways I think - basically the price of parts when a build is marked as "completed" is saved in the database with each component of that build.
Naturally this would suggest the ability to switch between "current prices" and "build prices", of which I assume "build prices" would be the default layout. So to be clear:
- "build prices" shows all the prices of the components at the time the user marked it as completed, regardless of whether that was yesterday or a year ago.
- "current prices" allows you to look at the best price for that component on the current market (current default view)
Why is this good? These are the reasons I can think of - and I think it helps in multiple ways:
- We can judge a build better based on what the person paid for the parts, not what they would pay now, which seems kind of clunky once you start thinking about it!
- Users would be allowed to edit the saved "build prices" - I would say at the moment about 1 in 3 builds have prices in their description, "this is what I actually paid for the parts at the time". Editing the prices directly would cut out the need for this, as well as making this kind of information so much more presentable
- Availability - current prices are based on current retailers. We all know how quickly technology advances. A year down the line all the current builds we celebrate might not even have half of their prices listed because the components are no longer being sold by the major retailers! Build prices will ALWAYS be relevant.
So there we have it. I think this is a really good idea and kills several birds with one stone. Hope you like it! (Sorry Philip, another set of data to store in the database with each build!)