Originally Posted by
michab
Yeah, just that you have to enter one thing to see the earnings but then something else to show the right lounges as opposed to getting them in one row. Might be worth detecting the unsupported fare classes and throwing an explicit error rather than just ignoring it.
Also, I wonder if some people might have an easier time with a bunch of labelled fields rather than having to figure out how to tweak the syntax?
I agree, it would be better to show all of the information together. Stay tuned.
A flight builder with dropdowns is on my radar, but I did the text input first for two reasons: (1) it’s faster for me to use since I know the syntax and (2) adding all of the possible options makes the UI quite crowded; text solves the simplest input case and the rest of the information is discoverable / referenceable.
I used a similar syntax to skymilescalculator.com, which I enjoyed prior to writing this but I thought I could have a different take on it.