> "Exchange Rate (Point/Mile)" which I took to mean "Points per Mile",
I see... It's bad UI design from me :( Need to work on a less confusing copy/UI.
> This is still a little weird, because I don't think I've ever heard of Amazon having "points".
You can earn "Points" with Amazon branded cards, e.g., https://www.amazon.com/b/ref=s9_acss_bw_cg_swpsf20_2c1_w?nod...
100 Amazon Rewards Points = US $1
> One idea: Instead of listing all ratios in common units on both sides of the ":", let the user select what they have and what they want. Something like:
> I HAVE ([]points []miles) AND WANT ([]points []miles []dollars)
Yes, this is on the roadmap. We have already integrated most of the commonly used rewards programs (in USA) into our database. The logical next step is to develop a tool that allows conversions like this: X points from Program #1 can be converted into Y miles from Program #2, and so on.
> Different question: How do you determine the value of points in the first place? If the best I can do with my Chase points is 1.7¢ at Hyatt, then what can I do to get 2¢ of value from them? Some internal shopping thing?
It's a cold start problem.
In an ideal scenario, we would have access to a lot of real transactions, such as X miles being used to purchase an air ticket worth Y USD, allowing us to calculate the exact value of 1 mile in terms of USD.
However, as we are just beginning, we have no users to provide this data. Our path forward is clear:
Step 1: We create a database and use estimated point/mile values found online, such as those provided by The Points Guy. While not ideal, this approach provides a necessary starting point.
Step 2: Users will be able to create accounts to track their points/miles and input real-world transactions.
Step 3: In the future, when we have enough data, we will be able to aggregate and calculate a more accurate value for points/miles in terms of USD.
Currently, we are at Step 1 :)