Would be nice if when using RateFindr and you switch between terms/mileage your prior inputs remain.
Ex: Looking at say a BMW X3 on RateFindr and wanting to compare 36/10k with 36/12k. You input 36/10k, check all your applicable incentives, etc., and see the price on the calc. Then you go to 12k and do the same thing. But for some reason you just can’t remember exactly what the 10k was. So when you go back to 10k, you have to re-input all of your incentives again. Would be nice if it “memorized” your prior inputs and just reverted to them, if that makes sense
4 Likes
It makes sense. Right now I would have to copy the calculator link, paste it onto another window (so my current search saved, with the make and model noted in Note), before I search for another mileage/term. I assume most people would like to compare the the payments, not just RV/MF, so a “Leave v Finance” payment comparison layout would help (except the user would be comparing two leases).
Not sure what would be the most elegant way to lay out the comparison if we were to build it given how crowded the calculator already is.
Another idea is to create a button that auto open the current numbers in a new tab, but with the Rate Findr selections saved.
Welcome suggestions!
Maybe some logic in the code where if the only thing changed post-load in this section is the mileage and you hit search again:
It just loads in the new RV to the calc and leaves everything else alone?
From a technical standpoint, off the top of my head, the simplest approach might be adding a new button at the end to allow a user to adjust term and/or mileage to some preset numbers.
This way the dev can take all existing values that are filled in and re-make the calls. I think adjusting the existing search button makes refactoring the current logic a nightmare given the waterfall effect of higher level choices.
Ultimately someone can probably do all the suggestions above, but there’s also probably a reason most automotive site filters behave the same way.
IMO
1 Like
